(WARNING: This is a long, boring mail :P) Well, maybe I am the only one who doesn't feel it like a totally postitive thing... First of all, aMSN is far from being stable on its own. Maybe it's better to polish what we currently have than coming up with a new core and adapting some pieces of our software to cooperate with it.
What would amsn gain from the porting to Telepathy? Lots of protocols. We already have MSN, the most complete out there I think (in terms of functionality, not code quality). We would be willing to implement Jabber... Well, i think it's A LOT easier to clean a little bit our current framework, and implement Jabber, we can even abstract Tkabber's code for our implementation, so we wouldn't even need to write Jabber code. Do you want to support AOL? Yahoo? Well I have never believed on clients full of protocols, and my experience with them tells me that i do prefer clients with less protocols, but more focused on what they do. To really cut out our GUI code and make a stand alone GUI and do the same with the protocol.... well, it's hard work. Probably harder than what I said for implementing Jabber . But it can be done. It wouldn't be aMSN, it would be a different thing, but we can do it if we feel like doing it. Also having to run to wish instances... uhm... Is it the right thing to do? Don't think so. We can be used to aMSN, but our code really needs some restructurations. We still have on protocol bits of MSNP7 and even some bits untouched from the ccmsn times. Think about it, only 2 people can actually work on our protocol code without having to study it in depth (Youness and Sander, maybe Burger from his times hacking on it a long ago). I think it would be great to see another project taking our protocol code and trying to make it operate with Telepathy, but moving aMSN's future in that direction.... I can't get the point... I think we could have more chances of success polishing our current product, reimplementing and cleaning the weakest points (each day less than the day before) and simply making it envolves. That 'transformation' of aMSN to use.... what? a core system based on DBUS messaging? Well, I think we can go on well with our rudimentary messaging system, and improve it a little, no need for DBUS, but it's fancy nowadays ;) I like the idea of having a protocol plugin based on our code (once it's clean and refactored) but I really don't see aMSN's future in that direction, I'm sorry to differ from the rest's point of view... Anyways, just my opinion, hope it helps :) Alberto P.D. I just looked at Telepathy quickly, I should have been practising maths :P so i may have missed a point. El Sunday, 11 de December de 2005 19:44, [EMAIL PROTECTED] escribió: > Hi guys, > > This will be a big email, and I hope it can generate a lot of talk. > This is a proposal for the future of aMSN that benefits several > parties : aMSN, Telepathy and Farsight. Now you all know Farsight, and > you all know aMSN. You might not have heard of Telepathy. It's a > project funded by Nokia to developped a CORE for all IM protocols. It's > basically a spec and a system that will be the brain of all IM > communications, including support for media (VOIP and video for > example). It is also based on D-BUS. How it works is that you have > connection managers for each protocol (basically a protocol plugin). > And it would have a GUI on top of it. > > The thing is, we don't want to use Gaim's MSN protocol as a connection > manager for telepathy. What we want is an aMSN based TCL connection > manager. That would basically mean all the protocol code, plugged into > telepathy through DBUS. Also, I would personally love a GUI on top of > telepathy that is based on aMSN's GUI (because I am so used to it). > > So what would the result be? > aMSN connection manager <-> Telepathy core <-> aMSN GUI > > Now, I know the GUI is being rewritten, would be very interesting to > write it cleanly on top of the Telepathy core. It would also be very > interesting to be able to separate completly the PROTOCOL code from the > rest of aMSNs organs. > > Whats in it for aMSN? Well, aMSN would then have support for any > protocol that is supported by Telepathy. Very soon, the Jabber > connexion manager for telepathy will be complete. Therefore at first it > would give aMSN Jabber support. Basically, aMSN would become a > multi-protocol IM with an MSN GUI :) I know we talked about this alot, > and I think telepathy is the solution. Also, aMSN would immediatly > benifit from Farsight since the Telepathy core will have full support > for Farsight. Obviously some of the current aMSN work would be lost > (all the core stuff) but on the long term, it means that all the > protocol work that has gone into aMSN will be used by any Telepathy > application, and it will give it more exposure. > > Problems to solve : a TCL extension to give it DBUS support. Finally a > good separation of Protocol/Core/GUI needs to be finished. Telepathy > needs to work on support for Win32 (macosx already supported). I would > like to note that the Adium people are already migrating to > Telepathy and dumping libgaim. > > Please ask me any questions you guys have, and give me your feedback. I > would love for this vision to go forward but it will never be done if > we don't have everyones approval of it. Also, I need to be alerted of > anything important I missed. > > Links : > Telepathy : http://telepathy.freedesktop.org/wiki/ #telepathy on > Freenode > Farsight : http://farsight.sf.net #farsight on Freenode > > Waiting for your replies, > Laterz, > Burger > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
