Aurélien Gâteau a écrit :
Aurélien Gâteau a écrit :
Hello,
I have been working on improving cobranding support for the
WengoPhone. I wrote an OpenWengo Enhancement Proposal (OWEP) about it.
You can find it here:
http://dev.openwengo.org/trac/openwengo/trac.cgi/wiki/OWEP_11388_Cobranding
Maxime Alexandre a écrit :
Nice :)
About the file format, why don't you use a standard format to store the
data ?
The thing is: we try to make the WengoPhone 2.1 easier to cobrand
without making too many invasive changes. If it was up to me, I wouldn't
be using XML to store config, or I
Aurélien Gâteau a écrit :
Hello,
I have been working on improving cobranding support for the WengoPhone.
I wrote an OpenWengo Enhancement Proposal (OWEP) about it. You can find
it here:
http://dev.openwengo.org/trac/openwengo/trac.cgi/wiki/OWEP_11388_Cobranding
The document talks about a
Le 4 juin 07 à 13:07, Aurélien Gâteau a écrit :
As you can see, the idea is still the same: store a relative path
if the resource path is inside resourcesDir, store a full path
otherwise.
This approach should be more lightweight than the previous because
it does not require any
Nice :)
About the file format, why don't you use a standard format to store the data ?
DTD files are maybe more suitable :
!ENTITY mywengo.ringing.file /home/user/boom.wav
Is there a data type specification, or all the settings are strings ?
Because you could have to store some booleans or
Maxime Alexandre wrote:
Another way to do it is to define CustomParams struct
and to use boost::serialization to serialize it to XML
boost::serialization does support structure versioning so back/forward
compatiblity
would be strightforward
Vadim
Hello,
I have been working on improving cobranding support for the WengoPhone.
I wrote an OpenWengo Enhancement Proposal (OWEP) about it. You can find
it here:
http://dev.openwengo.org/trac/openwengo/trac.cgi/wiki/OWEP_11388_Cobranding
As it's stated in the document, all work is going on in
