From: Jon Cruz <jon@...18...> Subject: Re: [Inkscape-devel] Embed Python script engine Date: Tue, 14 Dec 2010 19:35:00 -0800
doubt that value of XUL or XForms in the inkscape. It's a good concept, but it might not worth the effort in pratice. No matter XUL or XForms, we need to build a set of widgets to use them. Unless inkscape want to embedded gecko or webkit inside it in the long run. Use propriatary XML format to change the UI is more practical.
XUL is very very different from XForms. The latter presents some abstract data models and allows the hosting presentation to render them however it wants.
If you means data-model of XForms, I must to say that XUL also provides equivalent facility.
Oh, and we already are using it for our extension .inx support. Parameters are implemented via declarative functional UI, and and provide rendering 'hints' to allow inkscape to provide the more appropriate GTK widgets as needed.
The typical example of Firefox to use data-model is for UI of preference. I think it is what you said difference.
The data-model of XUL can comes from RSS/XML/or database. Since Inkscape have used XForms, just forget XUL. I just clear the misunderstanding for XUL.