On 3/1/06, Patrick Aljord <[EMAIL PROTECTED]> wrote:
It's a simple (well, not quite actually) application based on the NG engine. From this diagram: http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/WengoPhoneNgOverview#OverviewDiagram
we can see that WengoPhone Firefox extension uses an API that is a level higher than PhApi.
The level of abstraction to choose depends on which features must be integrated into your application. If you just need to place calls, you'd better use PhApi. If you need advanced functionnalities like external IM protocols support, contact list or history of calls, then you'd better use the same API as WengoPhone Firefox extension (that is the code written in wengophone/src/presentation/xpcom for now. Please keep in mind that this code is not tied to XPCOM in any way).
Looking at minua (located in wifo/miniua) may be a good start. It's really a bar bone application, and it has educational virtues. The best way to start, IMHO, is to write code in your favorite editor and ask questions on #openwengo :-).
That would be nice, indeed. In the above mentioned diagram, it corresponds to the console screen on the right-hand top.
Well, actually, it was the more pragmatic choice we could do by that time: it supports a lot of protocols in their latest version, it has a compatible license and it is actively maintained. There are drawbacks and pitfalls, for sure, like code that could be more componentized, and such, but we can avoid them by paying attention.
As usual, any input on available solutions that could better suit our needs is more than welcome.
On 3/1/06, gregor herrmann
> > If there is a need for a bare-bone phone application, it may be interesting
> > to build a light, robust and simple application based on PhApi (or even
> > SipWrapper).
jgi what about the API that you used for the firefox extension? isn't
that some kind of "simple application based on PhApi"? I thought so.
It's a simple (well, not quite actually) application based on the NG engine. From this diagram: http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/WengoPhoneNgOverview#OverviewDiagram
we can see that WengoPhone Firefox extension uses an API that is a level higher than PhApi.
The level of abstraction to choose depends on which features must be integrated into your application. If you just need to place calls, you'd better use PhApi. If you need advanced functionnalities like external IM protocols support, contact list or history of calls, then you'd better use the same API as WengoPhone Firefox extension (that is the code written in wengophone/src/presentation/xpcom for now. Please keep in mind that this code is not tied to XPCOM in any way).
> > We would love to help you if you wish to initiate such a
> > project.
I would be interested in building a light Qt4 (even Qtopia :))
softphone that would use the PhApi or SIP Wrapper but I'm not sure I
would have the knowledge to help you refactor the code to build a
bare-bone app though, I would need your help for that.
Looking at minua (located in wifo/miniua) may be a good start. It's really a bar bone application, and it has educational virtues. The best way to start, IMHO, is to write code in your favorite editor and ask questions on #openwengo :-).
(by the way I
think it would be nice to have basic text mesaging even on a bare-bone
refactored app like the ff extension)
That would be nice, indeed. In the above mentioned diagram, it corresponds to the console screen on the right-hand top.
I suppose that if they chose to integrate libgaim it's because they have the man power to do so
Well, actually, it was the more pragmatic choice we could do by that time: it supports a lot of protocols in their latest version, it has a compatible license and it is actively maintained. There are drawbacks and pitfalls, for sure, like code that could be more componentized, and such, but we can avoid them by paying attention.
As usual, any input on available solutions that could better suit our needs is more than welcome.
and
I'm sure that in a couple of month we'll get something usable :)
I would say that we'll have something usable sooner.
Thank you very much for your feedback.
Regards,
--
Julien Gilli
_______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
