Klaus Darilion wrote:
- being buildable on Windows with free software. That means free qt4 +
mingw. I've tried several times but never suceeded. Open source software
which can't be built without commercial products are useless for most
developers.
The only part that does not compile using MinGW is phApi, the rest of NG
does. Only few changes will allow to compile phApi with MinGW.
By the way there is a patch for Qt4 free edition to make it work with
Visual C++, Vadim sent the URL yesterday.
NG compiles under Linux and MacOSX aswell.
- being independent of wengo. Probably this is against your/wengo's
business case, but a configuration option (not a compile option) which
tells openwengo the http URL to download the provisiong data, or an
option to allow direct configuration of the SIP configuration is necessary.
We are working on it. If you check NG source code you will see that the
specific Wengo login procedure is well separated.
- calling outside the home domain. I do not know if this is doable with
ng, but I tried classic and it did not worked to dial any SIP URI
outside the local domain just by entering the SIP URI, eg.
sip:[EMAIL PROTECTED]
It should work already with classic.
For NG is just a problem of parsing. When you enter a standard phone
number like 01701878123 NG will create a SIP address of the shape
sip:[EMAIL PROTECTED] If the user enters a SIP address directly it
should not do any parsing and this is not the case for the moment (just
a 5 lines patch).
Also the buddy list and presence should be open
to all SIP domains.
The buddy list is local to the computer at least for the moment since
only XMLDataLayer is implemented not RPCDataLayer. I hope to integrate a
system where you the user will be able to specify its own URL for saving
the contact list and configuration files.
The configuration/settings system has not been implemented yet.
We use the standard protocol SIP simple for the presence, we are already
working on libgaim in order to integrate more chat and presence
protocols. Stay tuned ;)
We learned a lot with classic, we (specially me in fact) made many
mistakes with classic. If we develop NG from zero it's because we
believe NG will be 10 times better than classic and from a developer
point of vue it's already 10 times better.
The NG architecture has been already tested with softphone-csharp cf
http://dev.openwengo.com/trac/openwengo/trac.cgi/browser/old/softphone-csharp
The problem is simple C++ is not as complete as C# so we have to
re-invent/re-use/re-learn a lot (thread, mutex, stringlist, delegates,
xml parsing, http, serialization ect...) and it takes time.
--
Tanguy Krotoff <[EMAIL PROTECTED]>
http://dev.openwengo.com
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
