[hafqa] [hafqa] [Bug 2168] API needs destroy functions for user data
From: bugzilla-daemon at lists.maemo.org bugzilla-daemon at lists.maemo.orgDate: Thu Nov 8 10:18:20 EET 2007
- Previous message: [hafqa] [Bug 2221] Device name changes not reflected in the background image chooser
- Next message: [hafqa] [Bug 2168] API needs destroy functions for user data
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=2168 ------- Comment #4 from kimmo.hamalainen at nokia.com 2007-11-08 10:18 GMT+3 ------- I think we should not do this by modifying the existing API -- it will require changes in all API users. We should add new functions instead so the users can move to the new API when they wish to do so. I think the original Libosso API is ugly, so I started to write a new one, the 'muali API', but it seems there is not much interest for a libdbus wrapper. Also, it would be cleaner to remove the muali API as its own library. The muali API is not frozen in any way, so it still can be changed freely. Maybe you could modify the muali API to fit your needs and then we could split it from Libosso to begin its own life as a libdbus wrapper library. My design principle has been that it has 'API for dummies' that is very simple to use for applications that just want to send a simple message or receive a simple signal, and then it has API that allows to harness the full power of libdbus. It also should be independent from libdbus, in case a different D-Bus client library is used in the future (or no library at all). -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
- Previous message: [hafqa] [Bug 2221] Device name changes not reflected in the background image chooser
- Next message: [hafqa] [Bug 2168] API needs destroy functions for user data
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]