@David:<br><br>David, i was thinking already to remove the wrapping around libhal and libhal-storage and basically reimplement its/their functionality using DBus directly (basically what you said). I'm looking atm (well not _right now_ heh, but generally currently) at the libhal code, and I think this is how hal++ is going to end up in the end.
<br><br>It was a first shoot-off to replace the usage of the C API of libhal in BMP, but i realized now too that it'd be better if i'd instead just make hal++ talk directly to hald-* through DBus instead (i guess that's what you meant by stubs (?))
<br><br>@Murray (+ David heh)<br><br>Yeah well we talked recently about dbus-cpp in #c++ and thing is i see the whole introspectability, or rather non-introspectability, problem, as the biggest problem, with a lot of metacode generation.
<br><br>In the case of C++/gtkmm/sigc++ signaling it would be far more intrusive and heavyweight than the C variant, as a first estimate, as e.g. signals are hooked on to on a GSignal basis by-name: g_signal_connect (obj, "signalname", callback, data)
<br><br>With sigc++, you have to specify the signal name as a class member, etc. I think that this is the reason no one has started real work on a dbusmm (or continued it..) for now.<br><br>There was someone in #c++ recently (on GIMPnet) who said something about a dbusmm/dbus-cpp/dbus-c++ but i forgot who it was sorry.
<br><br>In any case the bottom line is: I'll start rewriting hal++ as something that directly talks to hald through dbus rather than wrapping the hal libs, and i'll just start out with the DBus C bindings, and as soon as someone comes up with a dbusmm (or maybe i'll start on it as well or code on it with the guy whose name i forgot :P), i can replace it internally then.
<br><br>Milosz<br><br><div><span class="gmail_quote">On 11/27/06, <b class="gmail_sendername">Murray Cumming</b> <<a href="mailto:murrayc@murrayc.com">murrayc@murrayc.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 2006-11-27 at 12:42 -0500, David Zeuthen wrote:<br>> Did you check out dbus-cpp that Murray Cumming wrote 1-2 years ago?<br>><br>> <a href="http://webcvs.freedesktop.org/dbus/dbus-cpp/">http://webcvs.freedesktop.org/dbus/dbus-cpp/
</a><br>><br>> Perhaps it would be useful if dbus-cpp included a binding tool that<br>> took<br>> D-Bus introspection XML and generated stubs. Unless this is the case<br>> already? Thanks.<br><br>I've never done more than the very initial work on dbus C++ APIs, partly
<br>because I never could find a simple DBUS C API example. It should be<br>better now. Basically, don't depend on me much for this.<br><br>--<br>Murray Cumming<br><a href="mailto:murrayc@murrayc.com">murrayc@murrayc.com</a>
<br><a href="http://www.murrayc.com">www.murrayc.com</a><br><a href="http://www.openismus.com">www.openismus.com</a><br><br></blockquote></div><br>