dbus/doc TODO,1.60,1.61
Havoc Pennington
hp at freedesktop.org
Sun Jan 30 15:06:34 PST 2005
- Previous message: dbus/dbus dbus-glib-lowlevel.h, 1.3, 1.4 dbus-glib.h, 1.5,
1.6 dbus-pending-call.c, 1.9, 1.10
- Next message: dbus/glib dbus-glib.c, 1.3, 1.4 dbus-gmain.c, 1.36,
1.37 dbus-gproxy.c, 1.15, 1.16
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /cvs/dbus/dbus/doc
In directory gabe:/tmp/cvs-serv17174/doc
Modified Files:
TODO
Log Message:
2005-01-30 Havoc Pennington <hp at redhat.com>
* glib/dbus-glib.c (dbus_g_pending_call_set_notify): new function
(dbus_g_pending_call_cancel): new function
* dbus/dbus-glib.h: move GType decls for connection/message here;
* dbus/dbus-glib.c: move all the g_type and ref/unref stuff in
here, just kind of rationalizing how we handle all that
* tools/dbus-names-model.c: new file for a tree model listing the
services on a bus
* tools/dbus-tree-view.c (model_new): use proper typing on the
model rows
Index: TODO
===================================================================
RCS file: /cvs/dbus/dbus/doc/TODO,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -d -r1.60 -r1.61
--- TODO 29 Jan 2005 19:52:19 -0000 1.60
+++ TODO 30 Jan 2005 23:06:32 -0000 1.61
@@ -51,16 +51,9 @@
- finish dbus-glib-tool support for adding introspection
data to GObject and autoexporting GObject using same
- - the GLib bindings varargs take DBUS_TYPE_WHATEVER and
- return stuff allocated with dbus_malloc(); should this
- be made more "G" at some expense in code duplication?
- You also still have to use some D-BUS functions such as
- dbus_message_get_args() which takes a DBusError.
- Probably we need to either fully encapsulate and hide
- dbus/dbus.h, or encapsulate it slightly less e.g. no
- GError. Or maybe it's as simple as "never return dbus_malloc()
- memory" and just fully encapsulate the get_args() type of
- stuff.
+ - Need to make sure that dbus-glib.h never returns any
+ dbus_malloc() memory, only g_malloc().
+ dbus_g_proxy_end_call() is the major offender.
- dbus_gproxy_connect_signal() has to take a signature for the signal
so it can figure out how to invoke the callback, or we have to rely
- Previous message: dbus/dbus dbus-glib-lowlevel.h, 1.3, 1.4 dbus-glib.h, 1.5,
1.6 dbus-pending-call.c, 1.9, 1.10
- Next message: dbus/glib dbus-glib.c, 1.3, 1.4 dbus-gmain.c, 1.36,
1.37 dbus-gproxy.c, 1.15, 1.16
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the dbus-commit
mailing list