Hi, Please do a lot of thinking before actually working on this. I do not know the protocol code now, but I think the whole thing should be re-designed so it will only interfere with other code through firing events and handling events. (i.e. no calls from protocol code to gui code and vice versa)
To do this, some coöperation with the 'new GUI'-team is necessary to make sure both will be compatible. If we don't take this opportunity we will probably end up not doing the redesign at all. I have done quite some study about fully event-driven systems, and even coded some in both Java and Objective-C. The principles stay the same in whatever language you're using, only the best way to implement might be different. But these two languages are fully Object-Oriented (as well as a few others), which makes implementing event-driven systems really easy. So I could help to develop a real good schema of events and handlers, as well as document those for developers. Although I don't think I can do much on the actual coding. I would like to, but I don't think I will have the time to do so. Also I would have to learn what kind of constructs are available in Tcl/Tk (I really have no idea yet, only found the syntax of the language a real mess until now, by looking at the code), but I will find the docs about Tcl/Tk soon enough when I only start looking for them. If you decide to go ahead with this, after 0.95 is out, I'd like to receive some links to useful information on the protocol. Information about the current implementation and used events will be in the wiki I assume, so I'll start digging for such there. If I don't find what I need, I'll just ask about it then. Please let me know if you like the idea! Regards, Harry Op zondag 4 december 2005 13:19, schreef Sander Hoentjen: > On Sun, 2005-12-04 at 11:33 +0100, Le Philousophe - Phil wrote: > > Hi, > > maybe some readers will believe I want to speak about 0.95 but it's not > > the case... > > I want to inform you that a MSN Messenger 8/Windows Live Messenger will > > go out... And guess it... It uses a new protocol !!! We will have to redo > > what we did for MSNP11 !! So crap !! And they add VoIP but with which > > codecs ??? So baaaaaaaad... Will we manage to continue our work ???? aMSN > > is so bloated !! Anyway I think we won't publish the MSNP11 version ! We > > will go from MSNP9 to MSNP13 : a huge gap !! > > Phil > > Yes i saw it already, > SYN is dropped, instead it uses SOAP for the address list > and there is support for offline messages.. :) > I was going to work on it in a few weeks but if you start before that I > won't, just let me know > > > > ------------------------------------------------------- > 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 > [email protected] > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/amsn-devel
