hello everyone, I'm studying an adapter having vconf API and buxton backend.
I'm seeing a lot of problem using buxton. For example: - I've submitted a patch to make API exposing "const char*" arguments, not "char*" - The API allow to list the keynames but it is unusefull: the response can not be inspected - If the response could be inspected, some data are missing: the group, the type (and the layer but it is set by the request) It makes the returned data unuseful. - the get of a value of a key fails if the type is wrong I made a pull request for the 2 former points https://github.com/sofar/buxton/pull/109 I dont understand what are design strategies or immature implementation. Help wanted. Best regards José Bollo _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
