Tanguy Krotoff a écrit : > What's going on with WengoPhone development? > > > ** Build system > First as everybody have noticed the build system is too slow. > Yes WengoSCons can be improved but I don't think this is the way to go. > CMake seems to be the one: it is now used by KDE after trying to get > (...) Great. > ** CoIpManager > VoIP is nice, Instant Messaging is nice too but what about merging them > all together? This is CoIpManager's goal! > (...)
> If you think about it communication over IP is always the same: > you have a session and this session contains text/audio/video/whatever > Of course you need to connect to a server using an account, a contact > list ect... > > So CoIpManager is just a huge abstraction with high level objects: > - Account: user login/password > - Connect: uses an Account to connect to a server > - Contact: a peer > - ContactList: a list of peers > - Session: high level object that represents a session between 2 contacts > - ChatSession: text session > - AudioSession: audio session > - VideoSession: video session > - FileSession: file transfer session > - VNCSession: remote desktop session > ect... > (...) > protocols as plugins and you've got the perfect library. > > If you check IMWrapper you will see that it is a first attempt to reach > this 'perfect' library. CoIpManager simply is a better IMWrapper. > Philippe Bernery who is responsible for CoIpManager development has > learned a lot from IMWrapper so you can expect a LOT of goods things > from CoIpManager! > > SipWrapper will not disappear, it will be used for the SIP protocol > implementation. Gaim won't disappear aswell: it will be used for MSN, > AIM, Jabber... This is the problem, I have the impression that Wengophone is composed of too many software layers. If we think about SIP, basically, to place a call, we have to go through: Core Wengo phone -> CoIpManager -> SIP Wrapper -> phAPI -> exoSIp Will this address the Skype connectivity ? (I know, this is proprietary but many people use this) Regarding contact management I would ideally have my contact list linked with my Mac address book or my outlook contacts (on PC) so I do not need to get all the information enteref again. > ** MultiSIP > A lot of people would like to use WengoPhone with other SIP providers. > CoIpManager will provide this feature since everything (MSN, AIM, Yahoo, > Wengo, GoogleTalk, FreeWorlDialup...) will be the same for WengoPhone > GUI. This is CoIpManager main purpose anyway. > > > ** Qt 4.2 > http://blog.openwengo.org/index.php?/archives/66-Qt-4.2-gona-be-a-huge-step-forward!.html > > Qt 4.2 will bring a lot of new exciting features. > Of course don't expect this to happen before a good 8/10 months. > There are still some bugs inside Qt 4.1 and it will take time to have a > stable 4.2 + the time for us to integrate 4.2 > > > ** Refactoring > The code is improving a lot, all the developers learned a lot in 2 years. > We have already good libraries that enable us to develop faster than > before. Check libs/util, libs/webcam, libs/wenbox, libs/qtutil to see > good examples. > This is important. May I suggest to address also the issues: * In Wengphone, we have dependencies with glib, qt and boost. All theses three are overlapping. Would it be possible to plan a simplifcation of all this ? * Video codecs : I have read aboud some issue regarding the SDP used for H.263 that prevented interoperation with external devices. Also what about the H.264 + plugin effort developed by Mr. Schneider ? _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
