Le March 14, 2007 08:34, Fabiano Sant'Ana a écrit :
> I'm really interested in improving kopete MSN protocol support.
> How can I help you guys?
>
> Martijn Klingens escreveu:
> > On Wednesday 14 March 2007 01:12, Michaël Larouche wrote:
> >> Yes, I implied protocol support of course, which Kopete cannot live.
> >>
> >> If we decide to focus on protocol support when I should
> >> start to work harder on Messenger plugin to get it done for 4.0
> >
> > Can you give me a status update for libpapillon and MSN support in
> > Kopete/4?
> >
> > I've seen a bunch of commits lately, does basic messaging work now? How
> > much is still missing that was existing in the 3.5 MSN plugin?
>
> _______________________________________________
> kopete-devel mailing list
> kopete-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kopete-devel

Responding to both (and CC' to Gregg):

Yes I will need help in libpapillon to be ready for Kopete 1.0. the contact 
list stuff need a lot of work, like generating a binding to a web service.

For generating the web service, I first started with kwsdl but I needed to 
refactor the whole XML schema so I gave up. Then I started to add C++ 
generation to SOAP4R in Ruby and it can generate XML schema bindings but not 
full web services bindings and I haven't working on it since November or 
December I can't remember.

This is really a big chunk in MSNP13 and it is demotivating sometimes. Also, I 
want to be good and reliable. So no, it can't do basic messaging stuff 
because of contact list :\

I'm pasting the TODO from libpapillon so you will get a basic idea where I am

- : Item need to be started
# : Item is in progress
+ : Item is done
! : Item was postoned to another milestone

Milestone 1: Contact list and presence

- Create MimeHeader class
# Parse initial Hotmail message
+ Do Papillon::ChallengeTask
# Contact list
        # Retrieve contact list and address book using SOAP bindings
        - Manage contact list local cache (loading, saving, syncing)
        # Frontend/client API for Contact list
        - Add, remove, block contacts
        - Manage address book changes and update it on server
        - Add, remove groups
        - Move contacts between groups
# Presence
        # Set our own presence
        # Set our own information (nickname, personal message, etc.)
        # Get the initial presence of contacts
        # Get modification of presence from others
        # Get information change from contacts (nickname, personal message, 
etc..)
+ Papillon/Class include style
- Error framework that manage error code received from server

After this milestone, all(or mostly all) contactlist and presence manipulation 
will be in and we should be able to start the Kopete plugin.

Milestone 2: Switchboard

- Create the Switchboard connection manager for Papillon::Client
- Look for incoming switchboard session
- Create new Switchboard sessions
- Parse and create new messages
- Send typing information (Special type of message)
- Invite contacts
- Offline messages retrival using SOAP (yet another "fun" Web service)
- Sending of Offline messages
- Sending and received Nudges (Special type of message)

After this milestone, basic switchboard operations will be in (expect P2P part 
in fact), and Kopete plugin will be usuable. (Maybe a first standalone 
release of libpapillon)

Milestone 3: Peer to Peer

 - Design P2P framework
 - Design MSN object (and push it with presence)
 - Download and upload Display picture
 - Download and upload Custom emoticons
 - File transfer using Switchboard
 - Ability to register external P2P context using context GUID (suggestion by 
Diederick from KMess)

After this milestone, basic P2P framework will be complete. Futher P2P 
features will come after.

Milestone4: Webcam, Direct Transfers, HTTP and Proxy
 - Implement Webcam P2P context
 - Use reflection server for NAT
 - Implement direct transfers for all P2P context
 - Implement proxy support
 - Implement MSNP over HTTP

After this milestone, libpapillon will be equal to old Kopete MSN 
implementation(and more of course).

Features that maybe would be implemented

Shared folders
Voice clips (need documentation)
Voice conversation (need documentation)

Features that would be never implemented

Winks (annoying, use CAB and Flash)
Dynamic display pictures (use flash)
Background sharing
-- 
Michaël Larouche
KDE developer working on Kopete, Gamefu(KDE), Solid...on dial-up :P
--------------------------------------
Website: http://www.tehbisnatch.org/
MSN: [EMAIL PROTECTED]
IRC: irc.freenode.org/DarkShock
Jabber/email: [EMAIL PROTECTED]

Attachment: pgpQ6sidMD5PS.pgp
Description: PGP signature

_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel

Reply via email to