On Wed, Jul 19, 2006 at 09:44:17PM +0200, Philippe Valembois - Phil wrote: > Le Wednesday 19 July 2006 21:38, Harry Vennik a ?crit?: > > Op woensdag 19 juli 2006 21:14, schreef Philippe Valembois - Phil: > > > > 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. > > > > > > So there isn't any trouble if we do how we said some months ago : XML2GUI > > > (ours) to tie aMSN and the GUI engine... > > > > As the name suggests XML2GUI is a way to render a GUI as described in a XML > > file. So XULRunner is an example of an implementation of such a thing. > > 'Our' XML2GUI was an idea, not some part of code, even though there has > > been work (by me) on a piece of code to implement that idea, because I did > > not find a way to realize all of the XML2GUI idea with an existing > > solution. But while working on that I kept thinking about XULRunner (the > > best existing solution I had found), because it has a lot of very nice > > features (full CSS support for example) that would be very hard to do > > ourselves, and it already has backends for at least one good toolkit for > > each platform we want to support. So I retried to solve the issues that > > made me not choose XULRunner in the first place, and I finally found new > > information that proofed that such would be possible, so I decided to go > > with XULRunner, because it would fit our needs best. > Yeah if you like XULRunner why not... I don't try to force using of TkHtml > but > I think (as it was said some months ago) that a multi-GUI soft would be great > as you could use XULRunner and we could use TkHtml and with that we don't > force user to use GTK or things like that... They can use other things... > Phil
We never said the contrary.. you can create your own Tk+Tkhtml implementation of XULRunner.. or actually you can create your own XML2GUI that would be compatible with the XUL xml syntax... but since XUL does all we want (or so Harry says), we save ourselves the time needed to write such a XML2GUI project.. KKRT > > > > If we would allow different XML2GUI implementations to be used with aMSN, > > the problem would be that in most cases their XML would not be the same > > format, and thus we would need different XML files for each, and also they > > will all require their own bindings to bind to the rest of aMSN. I think > > that would be a huge problem, so that's why I say: just choose 1. > > > > ------------------------------------------------------------------------- > > 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
