Emmanuel BUU wrote:
Tanguy, we definitly need an abstraction. The CoIpManager is a brilliant
idea. But the logical next step would be then to
* Select ONE SIP stack, ONE RTP stack
There is 1 SIP stack and only 1 RTP stack and this job is achieved by phApi
and implement CoIpManager plugins using those APIs / stack natively.
This would mean to scrap PhAPI for instance (sorry Vadim) and IMWrapper
and SIP Wrapper.
SipWrapper will stay: it will be used to have a IAX implementation
aswell. CoIpManager replaces IMWrapper (in fact it extends it).
phApi works on embedded systems so don't worry for the memory foot print.
It will be
like layers of sand or mud in rivers and after a couple of million
years, people will dig into this to find dino bones :).
LOL
I guess code maintainability is not never issue until the maintenance
costs are too high.
A soft is 20% creation and 80% maintenance. Imagine if creation step is
not well done.
It should however be possible to compile separately the model of OW
without any QT dependency and then compile a Qt presentation WITHOUT
BOOST compilation dependency then link the whole thing together.
Agree but not simple as that. Model is Qt independant but presentation
is not Boost independant (at least it is dependant indirectly via
libutil and libqtutil).
I am aware that presentation / business logic are already separated but
this clearer seperation would make easier for service provider to embed
your product without having to use boost and be constrainted by your
choices. For instance, create a browser plugin and implement the whole
GUI as HTML and Javascript as I dream to do one day ...
Check the Firefox extension
It should be possible to also look toward code simplicity and use less
hundreds of classes and templates and ... Yes, regarding object oriented
programming, I am agnostic and I have seen to big projects die because
of design pattern overuse.
Don't worry for that. But yeah that's true I dislike .cpp that are 3000
lines long. I prefer the UNIX/KISS approach: small and simple tools
(=classes) that make one and only one thing.
For example I HATE to read Qt source code: 3000 lines .cpp files with
variables named like a, b, c... impossible to make a simple search
inside their source code!
--
Tanguy Krotoff <[EMAIL PROTECTED]>
http://openwengo.org
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
