Chris,
I'm wrong, sorry for the mistake ...
Keys :
config.xml : url.internaldirectory
config.cpp : URL_INTERNALDIRECTORY_KEY
Model layer :
accessors : WsUrl::getWengoDirectoryUrl()
Presentation layer :
WsUrl::showWengoSmartDirectory() (with open-sources Qt version)
QtWebDirectory (only Windows commercial Qt version)
(It will be interesting to rewrite QtWebDirectory with QtWebkit module ... )
Laurent
Chris Maciejewski a écrit :
> Hi Laurent,
>
> Thanks for you reply again.
>
> Unfortunately it seems to me xxx is not implemented anywhere in
> current code (apart from model/Config.h(cpp)). I tried to grep source
> code, but all I can find is:
>
> $ find . -name "*.cpp" -exec grep -Hn 'WENGO_DIRECTORY_PATH_KEY' {} \;
>
> ./model/config/Config.cpp:138:const string
> Config::WENGO_DIRECTORY_PATH_KEY = "wengo.directory.path";
> ./model/config/Config.cpp:482: return
> getStringKeyValue(WENGO_DIRECTORY_PATH_KEY);
>
>
> $ find . -name "*.cpp" -exec grep -Hn 'getWengoDirectoryPath' {} \;
>
> ./model/config/Config.cpp:481:string Config::getWengoDirectoryPath() const {
> ch...@chris:~/qutecom-2.2/wengophone/src$ find . -name "*.cpp" -exec
> grep -Hn 'getWengoDirectoryPath' {} \;
> ./model/config/Config.cpp:481:string Config::getWengoDirectoryPath() const {
>
>
> So looks like Config::getWengoDirectoryPath() is not used anywhere at all.
>
> Also when I checked web server logs, the only URLs requested when
> starting QuteCom are:
>
> wengo.sso.path
> wengo.softupdate.path
> wengo.info.path
>
> Would it be possible wengo.directory.path is currently not
> implemented? Or I am missing something?
>
> Best regards,
> Chris
>
>
>
> 2009/8/14 Laurent Tarrisse <[email protected]>:
>
>> Hello Chris,
>>
>> It is : WENGO_DIRECTORY_PATH_KEY = "wengo.directory.path";
>>
>> With it, you can add wengo contacts into your contact-list.
>>
>> This is not a remote contact-list manager .... like XCAP
>> (http://openxcap.org)
>>
>> Laurent
>>
>> Chris Maciejewski a écrit :
>>
>>> Hi Laurent,
>>>
>>> Thanks for you reply.
>>>
>>> I did enable CUSTOM_ACCOUNT in DefineWengoOptions.cmake file.
>>>
>>> However still can't figure out which "webservice" should push contacts
>>> to QuteCom.
>>>
>>> Likely candidates are:
>>>
>>> WENGO_SSO_PATH_KEY = "wengo.sso.path"; // I use that one already for
>>> SIP account details
>>>
>>> WENGO_INFO_PATH_KEY = "wengo.info.path";
>>> WENGO_SUBSCRIBE_PATH_KEY = "wengo.subscribe.path";
>>> WENGO_CIRPACK_PATH_KEY = "wengo.cirpack.path";
>>> WENGO_DIRECTORY_PATH_KEY = "wengo.directory.path";
>>>
>>> Could you please let me know which of the above is responsible for Contact
>>> list?
>>>
>>> Thanks and best regards,
>>> Chris
>>>
>>>
>>> 2009/8/6 Laurent Tarrisse <[email protected]>:
>>>
>>>
>>>> Yes, it is possible to fetch contacts from server
>>>>
>>>> You need to enable CUSTOM_ACCOUNT in DefineWengoOptions.cmake
>>>>
>>>> Laurent
>>>>
>>>> Chris Maciejewski a écrit :
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> Is it currently possible to fetch contacts from the server (in XML
>>>>> format)?
>>>>>
>>>>> I managed to implement
>>>>>
>>>>> <wengo.info.path><string>/oss/info</string></wengo.info.path>
>>>>>
>>>>> to update balance, line number etc.
>>>>>
>>>>> I can see the following in the config.xml:
>>>>>
>>>>> <wengo.directory.path><string>/oss/directory</string></wengo.directory.path>
>>>>>
>>>>> but there is nowhere in the code the above is used???
>>>>>
>>>>> The only "webservices" I can see in src/model/webservices are
>>>>> callforward, info, sms and softupdate.
>>>>>
>>>>> If it is not implemented at the moment, could please someone let me
>>>>> know, where is a best place to start to add this feature?
>>>>>
>>>>> Best regards,
>>>>> Chris
>>>>>
>
>
>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
