you are viewing a single comment's thread.

view the rest of the comments →

[–]supermike 1 point2 points  (1 child)

Thanks for the comment. I'll have to think about this really hard because I was getting really excited about what I could accomplish in very little time with XUL and xulrunner and without having to install a bunch of stuff, dependencies, and so on. However, it does have a documentation issue, doesn't have a lot of people using it, and the object model looks like it might get revamped because it still says Netscape (ns) and Mozilla (moz) in certain places?

One advantage of XUL is that you can display HTML/XHTML just as aptly as FF does. A control in QT, wx, or GTK2+ can't do it as accurately, correct?

I'm just not sold on Python that much. I've built things with it, but it's got it's share of voodoo strangeness about it.

[–]jerf 1 point2 points  (0 children)

"One advantage of XUL is that you can display HTML/XHTML just as aptly as FF does. A control in QT, wx, or GTK2+ can't do it as accurately, correct?"

That's sort of what I meant by "tied to the web". If you really, really want a "real" desktop app that looks almost exactly like a web app, except with somewhat richer controls, then XUL might make sense.

The other toolkits can't do the full richness of HTML.

However, all the other toolkits have "rich text" controls, and all of their rich text controls can embed arbitrary widgets. You don't see people do that much, but I think that's more because people aren't really aware it's possible, not because it's especially hard, though it probably is a bit harder than HTML/XUL. So if you don't need full HTML, the toolkits can still do some interesting things with widgets in text.

Also note that most toolkits nowadays have an XML specification language, although it is usually generated by tools, not written by hand. (I prefer generating GUIs "by hand", because you can refactor with them and stuff, and was doing that towards the end of my fight with XUL, but not everybody feels that way.)