Hi,
   Well after seeing that long thread about languages, it kinda feels
like there is no solution but to keep the GUI in tcl/tk. We will never
agree on a new language, we already know tcl/tk, and we have a whole
lot of GUI code already written in TCL/TK. The back-end (connection
manager) could be written in anything as it doesn't really matter or
doesn't even need to be an "amsn only" project. It can be started by
someone else, and contributed to by us, or vice versa. In any case
there are several outsiders to aMSN interested in such a project so
it's not an issue.

Regards,
Philippe

On Wed, 24 May 2006 20:32:10 -0400
Philippe Khalaf <[EMAIL PROTECTED]> wrote:

> Hi,
>    I have been reading the mailing list and I gather that people are
> getting rather bored. But the main problem is that everyone seems to be
> busy. In any case, I have sent a similar email before but I am doing it
> again. Now Telepathy is at a different stage of it's life. It's
> actually working now and a project like aMSN2 can be started. In case
> you guys don't know it, Telepathy is getting big and it will soon
> become an integral part of the Gnome desktop, and hopefully KDE. If
> aMSN2 was to be started, it would consist of 2 main projects :
> 
> - An MSN connection manager for Telepathy (a kind of protocol plugin) :
> This is where the aMSN people can be very helpful since you all have a
> rather good knowledge of the MSN protocol and can write this easily.
> This of course can be written in a different language than TCL. Any
> language that has DBUS bindings will do (C/GLib, C++, QT Objects,
> python, etc).
> 
> - An aMSN2 GUI. Brand new GUI. The cool thing about aMSN is it's
> feature list. The aMSN devels have come up with cool features that are
> actually useful and not just stupid little gadgets. This can be
> transported into a brand new UI that uses Telepathy, and it can be
> written with another toolkit like GTK or QT. A new UI can be started
> immediately using the Jabber connection manager (called gabble) while
> the MSN connection manager is being worked on.
> 
> In other words, aMSN2 would be a completely different project, but I
> believe aMSN is what it is not because of tcl/tk and not because of it's
> pretty code :P but because of the features and feel that it has, and
> that is a direct reflection of the community that works on it. If the
> feel of aMSN can be maintained, it doesn't matter what back-end it uses,
> or what toolkit it's written in. It can only look better anyways :)
> 
> There are a lot of positive things about moving on to Telepathy :
> - Put some life back into the project. 
> - New languages and new skills to learn. I'm talking C, C++, GLib, GTK,
> QT, D-BUS or anything else we want.
> - New toolkit, new look.
> - Solid and well designed framework.
> - Getting in sync with the future. Telepathy is big now. We have a
> GUADEC main talk, we got 2 summer of code entries and we financially
> support the project. Any UIs or projects associated with it
> will also be big (aMSN is already big and can take it's popularity with
> it).
> - Transparent support for other protocols (jabber, oscar, etc).
> - Full audio/video support with Farsight.
> 
> I will let you come up with any drawbacks or bad things about it.
> 
> If anyone is interested in taking this direction. Tell me right now! I
> can definitely help out with managing such a project and designing
> anything that needs to be designed. Obviously I am very close to
> Telepathy and can help with anything in that regards as well.
> 
> You guys want a spark here is your chance. Take it or leave it the
> Telepathy train is taking passengers but isn't slowing down!
> 
> Regards,
> Philippe
> 
> 
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel


_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to