Re: [dbus-cplusplus-devel] libhal++?

[Milosz D. <int...@gm...>]

Hey Andreas,

After a long time i'm reporting back in.

I've now started developing libhalmm, which is a reimplementation of
libhal and libhal-storage
using dbus-c++. I expect to publish the first version of the source
code with an estimated
completion of the code of 90% end of coming week (there are some
obscurities in libhal
about which i need to talk about with the hal developers).

I've mailed to the dbus-c++ mailing list with a few questions, but
Paolo was not very forthcoming
and finally outright ignored me; I don't know why he was being so
offensive after me just
having asked a few questions. Anyway, i'll quote the original questions here:

> Hello,
>
> I've got 2 questions and one announcement.
>
> First the announcement: I've finally started writing the libhalmm rewrite,
> as a reimplementation of libhal,
> instead of being a wrapper around the C libhal and libhal-storage.
>
> Since the basic work is straightforward I expect that I can make an
> announcement of the source code
> within 1-2 weeks; I'll post again then with the checkout URL, etc.
>
> Two questions:
>
> 1.) Is it OK to post git diffs for dbus-c++ here? (I assume yes, but just
> wanted to ask)
>
> 2.) Is the policy for inclusion of DBus C headers still "No DBus C headers
> in the public dbus-c++ headers"?
> I thought we could get rid of some (IMO) stupid things in the DBus C API,
> e.g. introduce an enum for the
> message type. However, to take the values from the C API, the C header
> dbus-protocol.h would need to
> be included? How is the stance on this policy by now?

Would be nice if you could tell me how the state of this is currently.

Regards,
M.

> On Sat, Nov 8, 2008 at 4:05 PM, Milosz Derezynski <int...@gm...> wrote:
> Hey Andreas,
>
> I will definitely look into the example, and into reimplementing libhal++
> instead of wrapping
> it in the next coming time.
>
> I've subscribed to dbus-cplusplus-devel now also.
>
> Thanks for the information!
>
> Cheers,
> M.
>
> On Sat, Nov 8, 2008 at 10:52 AM, Andreas Volz <and...@tu...>
> wrote:
>>
>> Am Sat, 8 Nov 2008 01:21:03 +0100 schrieb Milosz Derezynski:
>>
>> Hello Milosz,
>>
>> maybe you should correct the link on freshmeat.net. I didn't find that
>> site with google.
>>
>> In the past I did some changes in dbus-c++. Not sure if talk about the
>> same wrapper. But this on is the most mature C++ wrapper in my eyes.
>>
>> http://www.freedesktop.org/wiki/Software/dbus-c++
>> http://sourceforge.net/projects/dbus-cplusplus/
>>
>> There're currently two different repos that I try to sync from time to
>> time.
>>
>> There's the "hal-listen" example beside the source. I tried it and it
>> works nice, but no idea how complete the hal support is. Maybe you take
>> a look into it and tell us what's missing for the current libhal++
>> features. The example shows me a list of devices and when I add or
>> remove devices it prints that on the terminal. Sounds good for me.
>>
>> regards
>> Andreas
>>
>> BTW: dbus-c++ has a mailing list. I send this mail to the list too.
>> Maybe you join the list if you're interested.
>>
>> > Hey!
>> >
>> > Our website has moved, so the repositories and minisite moved too.
>> > All infos are available at:
>> > http://projects.backtrace.info/pmwiki.php?n=Main.Hal
>> >
>> > You probably know that this is a wrapping of the C API, and it's not
>> > done with gmmproc. (saying it just in case)
>> >
>> > There is a plan to reimplement libhal in C++ using dbusmm, but it has
>> > only recently become possible to
>> > do so because of the maturity of dbusmm; when i get the time i will
>> > attempt this as it's better than
>> > simply wrapping the C API.
>> >
>> > If you have any questions please let me know!
>> >
>> > Regards,
>> > M.
>> >
>> > On Sat, Nov 8, 2008 at 12:06 AM, Andreas Volz
>> > <and...@tu...>wrote:
>> >
>> > > Hello Milosz,
>> > >
>> > > any idea what's about libhal++? All links seems to be broken.
>> > >
>> > > Could you tell me about the current status? Do you still have the
>> > > source code and could send it to me?
>> > >
>> > > regards
>> > > Andreas
>> > >
>> > > --
>> > > Technical Blog <http://andreasvolz.wordpress.com/>
>> > >
>> >
>> >
>> >
>> > --
>> > Please note that according to the German law on data retention,
>> > information on every electronic information exchange with me is
>> > retained for a period of six months.
>> > [Bitte beachten Sie, dass dem Gesetz zur Vorratsdatenspeicherung
>> > zufolge jeder elektronische Kontakt mit mir sechs Monate lang
>> > gespeichert wird.]
>>
>>
>> --
>> Technical Blog <http://andreasvolz.wordpress.com/>
>
>
>
> --
> Please note that according to the German law on data retention,
> information on every electronic information exchange with me is
> retained for a period of six months.
> [Bitte beachten Sie, dass dem Gesetz zur Vorratsdatenspeicherung zufolge
> jeder elektronische Kontakt mit mir sechs Monate lang gespeichert wird.]
>



-- 
Please note that according to the German law on data retention,
information on every electronic information exchange with me is
retained for a period of six months.
[Bitte beachten Sie, dass dem Gesetz zur Vorratsdatenspeicherung zufolge
jeder elektronische Kontakt mit mir sechs Monate lang gespeichert wird.]