Hello,

 

As a side project that begun some weeks ago, I asked Minh to review phapi.h and see how we could leverage our 2 year anniversary of SIP problems and revamp it in order to make a more clear, more easy to understand and less prone to error interface.

 

Some of you may have followed this work in the wifo-refactoring branch.

 

Please look at some entry points and comment :

 

New Ones:

http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/wengophone-ng/branches/wifo-refactoring/phapi/phapi.h

http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/wengophone-ng/branches/wifo-refactoring/phapi/phevents.h

http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/wengophone-ng/branches/wifo-refactoring/phapi/phvline.h

 

Old One:

http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/wengophone-ng/trunk/wifo/phapi/phapi.h

 

Minh will try and summarize your comments to take into account your needs in this revamping process.

Thank you,

Jérôme

 

Ps1: Just to be more precise : this does not put on hold the necessity we have to clarify the repository layout and packaging of wengophone 2.0 on which we will have to work in the next days. It is a crucial refactoring that we need to do before it is too late and that will impact in the mid-term current phapi users so I want to give it sufficient publicity so that everyone can be involved.

 

Ps2: A porting guide will be written to help users understand the new API and help them upgrade their application.

_______________________________________________
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to