1) Does it support multi-platform applications well?
For example, OS X users complain about the poor Mozilla XUL UI.
2) How easy can you express/produce simple things?
3) What design quality can you achieve? Is the hard stuff possible?
4) Does it help you achieve a well-designed UI?
5) Can everybody in your team work with the solution?
6) What about the readability of the layout description?
Can you understand and edit what your collegue has designed?
7) What about compile-time safety?
8) What about tool support: e.g. editor support, code-completion?
Can you browse references?
9) Does your editor integrate with your refactoring tool?
10) How easy can you find and fix bugs? Can you debug
the build process and component configuration?
11) Does it support your favorite widget toolkit well?
For example, can you work with the GlassPane?
And does it integrate with Java2D?
12) Does it support multiple widget toolkits?
(Without ending up with the worst of all worlds).
13) Can you rely on the solution vendor?
14) How large is the extra download size?
15) How much does it cost?
16) Is support available?
17) Can you change the layout at runtime?
18) Can users change the layout at runtime?
MozillaじゃないXULたち (スコア:4, 興味深い)
XUL2GTK [phppatterns.com]: XULとPHPで書いたコードをPHP-GTKのコードに変換。
Jazilla [dhs.org]: Javaで書かれたXULエンジン(あまり進んでない?)
#どれも使ったことないので使ったことある人フォローよろ。
Re:MozillaじゃないXULたち (スコア:2, 参考になる)
Hans Muller's JavaOne session: Defining Swing GUIs Declaratively [swixml.org]に，SwingのGUIをXMLで書くフレームワークいろいろがレビューされています．死屍累々です．
Re:MozillaじゃないXULたち (スコア:2, 参考になる)
XUL and Java. It seems obvious to me. [javadesktop.org]という投稿には，こういうXULなどのフレームワークを評価するためのdiciplinesが列挙されていて，参考になります．以下引用します：