Op woensdag 19 juli 2006 20:58, schreef Philippe Valembois - Phil: > Well, some errors in the sum up : > For TkHtml : " - It's still TK, any form element for example is still an > ugly TK widget." > Wrong because it's you who handle these tags and you can create another > widget : why not a pixmap widget ? That is applying again a work-around for TK...
> For XML2GUI : Are you sure you understood XML2GUI ? For me, XML2GUI was a > system to create interfaces for several toolkits and not the link you > provided : XML2GUI was to be designed by us... This is just a name collision. The XML2GUI that was to be designed by us is not the same as the one in the sum up. > > >From events and logic it generates a XML which is used by a specific > > engine to > > render the widgets described in the XML.... > For XUL : and for Youness it's decided on the compil time : can you switch > from GTK2 to QT in Firefox ? No. (By the way is there a QT engine for XUL > ?) Phil I don't know yet if there is a XUL rendere for Qt at the moment. I still have to check. Indeed the toolkit option is compile time. > > > > TkHTML: > > > --------- > > > Pro: > > > - Seems to render HTML real good > > > - Supports CSS1 (TkHtml version 3) > > > > > > Con: > > > - It's still TK, any form element for example is still an ugly TK > > > widget. - It only renders HTML, which is perfectly fit for the contents > > > of our main window (except the menu bar), but not for anything else > > > (e.g. dialog windows). > > > - Depends on a single toolkit: TK > > > > > > Doubtful: > > > - Seems to be very permissive for bad HTML code. This may be easy when > > > creating the code, but also may cause non-wellformed code to go > > > unnoticed, which then may break in another TkHtml version. (On bad > > > markup, behavior is undefined, and thus may not always be the same.) > > > > > > > > > xml2gui (http://wiki.tcl.tk/8908) > > > ----------- > > > Pro: > > > - Very familiar: 1-to-1 mapping of TK commands to XML > > > - Everything possible with pure TK is also possible with this xml2gui > > > > > > Con: > > > - It's still TK, so it's still ugly. > > > - Depends on a single toolkit: TK > > > - Nothing like CSS supported > > > > > > > > > GladeXML > > > ----------- > > > Pro: > > > - Can handle any type of GTK widget > > > - If you got Glade, you can just draw your GUI > > > - In use by many projects, seems to work great. > > > > > > Con: > > > - Hard to hand-code XML > > > - Depends on a single toolkit: GTK > > > - Nothing like CSS supported > > > - Will not blend with HTML (but Pango markup is supported) > > > > > > > > > > > > XUL > > > ---- > > > Pro: > > > - Straight-forward and easy to use XML tag set > > > - Can be mixed with other XML-based languages (e.g. XHMTL) using XML > > > namespaces > > > - Supports CSS2, as well as some extensions to that. > > > - Localization support (by means of XML entities). [To be 100% honest: > > > this might work with some other XML, but here it is in the specs, so > > > it's sure to be supported.] > > > - Can support a native toolkit on every platform. (on Linux: GTK2) > > > - We all know the proof that it works: Firefox > > > - XULRunner can run embedded in another app (not yet complete in > > > current version) [Probably not needed, but you never know...] > > > > > > Con: > > > - You'll need to use XPCOM to bind code to the GUI. [XPCOM is Mozilla's > > > component system. It is best described as a cross-platform subset of > > > Microsoft's COM. Using this may require C++, I'm not yet sure of that.] > > > > > > Doubtful: > > > - Will enforce a package structure. For aMSN2 this will probably be a > > > per plugin package structure, but that is not 100% sure yet. Anyway, > > > one can regard this either as a pro or a con. Personally I'd like it > > > per-plugin, otherwise not. > > > > > > ----------------------------------------------------------------------- > > >-- Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > > your opinions on IT & business topics through brief surveys -- and earn > > > cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD > > >EV _______________________________________________ > > > Amsn-devel mailing list > > > Amsn-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your opinions on IT & business topics through brief surveys -- and earn > > cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Amsn-devel mailing list > > Amsn-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
