Hi, even if you yield at us I am happy ;) I am sure now that all will be in Tcl except protocol and bindings for D-Bus... Now, to sum up a little we will have : Protocol and Thelepathy <-> Some IPC service (DBus on *Nix, maybe DCom on Win ?, MacOs maybe DBus) <-> Bindings for IPC written in C (no need of C++ neither GLib for that) <-> aMSN logic with XML2GUI (written in Tcl) <-> GUI plugins (like XUL created by Harry, TkHtml created by Tom, Boris and me, and maybe others) I like that :d So there will be many Tcl and people will have the ability to develop something in Tcl Now there is a little problem (no don't worry I am not whining it's only to have a good design) : plugins... Because there are some plugins that interact at protocol level and some other that interact at GUI level and maybe some that interact in the two levels... But I think that doing plugins for only one GUI is a silly thing... aMSN is aMSN and plugins should be for aMSN and not for a whateverGUIpluginforaMSN... So we should think too about a way to make plugins compatible with all GUIs... Phil P.S. I hope I well understood your mail Youness. PPS Windows has already its IPC techniques so we should use them to port DBus to Windows but it's not our job (at least not the job of aMSN team)....
------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/amsn-devel
