Emmanuel BUU wrote:
This is the problem, I have the impression that Wengophone is composed
of too many software layers.

And? do you really think this is a problem?

If we think about SIP, basically, to place
a call, we have to go through:

Core Wengo phone -> CoIpManager -> SIP Wrapper ->  phAPI ->  exoSIp

On the other hand the code inside WengoPhone' model and presentation (GUI) is way easier! CoIpManager will simplify a lot the code -> less bugs, easier to read, easier to port, easier to optimize, more consistent... I believe in high level components: this is history: look at Java, C#, Qt... compare to C, Pascal, MFC... It's like travelling. You wanna buy a baguette for your breakfast, you go get your bicycle on the other hand if you wanna go from Madrid to Paris, you use the train or your car.

How can you be compatible with MSN, AIM, Jabber, SIP, IAX... without an abstraction? If Gaim is not good enough for Jabber for example, how can you replace the Jabber implementation for something else (Jiggle for instance) without changing the MSN, AIM... implementations that are using Gaim?

Will this address the Skype connectivity ? (I know, this is proprietary
but many people use this)

Theorically yes, just think about the matrix I wrote:

Protocol || Chat (Text) | Audio | Video | FileTransfer | ContactList...
---------||---------------------------------------------------------
Yahoo    || Yes         | No    | No    | Yes          | Yes
---------||---------------------------------------------------------
MSN      ||
---------||---------------------------------------------------------
SIP      || Yes         | Yes   | Yes   | Yes          | No
---------||---------------------------------------------------------
AIM      ||
---------||---------------------------------------------------------
Jabber   ||
.
.
.

Add the line:

Protocol || Chat (Text) | Audio | Video | FileTransfer | ContactList...
---------||---------------------------------------------------------
Skype    || Yes         | No    | No    | Yes          | Yes


'Yes' and 'No' of course depends on the library that is used to be compatible with Skype.


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.

At least an import contact list module with plugins for Outlook, Thunderbird and Mac Address Book can be implemented, synchronization is harder to achieve. It will take time but there is nothing really complex about it ;)

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 ?

glib because of Gaim
Qt for the GUI
Boost for the model so we are independant from Qt for this part
Boost has been already discussed here:
http://article.gmane.org/gmane.comp.voip.wengophone.devel/516/

glib issue can be solved: one can take Gaim modules (MSN, AIM, Jabber...) without the abstraction model that LibGaim offers since Gaim modules are developed without the glib dependency. But I don't really think this is priority. For Boost and Qt this won't be solved: this is done on purpose and developers are pretty happy with it. Yes we know that for external developers installing/compiling Boost + Qt4.1 is a pain in the ass.

    * 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 ?

Jerome Wagner is in holidays that's why ;)

Anyway all these compatibility issues will be solved since we want to be compatible with other SIP providers, at least:
Free World Dialup
ekiga.net
Voip Buster
Vonage
SIPphone (Gizmo project)

--
Tanguy Krotoff <[EMAIL PROTECTED]>
http://openwengo.org
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to