Exposing the mouse battery status through HAL

Sergey Udaltsov sergey.udaltsov at gmail.com
Tue Nov 30 15:01:01 PST 2004


> looking for to show up on the list was that the fdi file merge
> info saying that "run com.logitech.mouse..." daemon, and hald
> finds the callout and run it, or otherwise asks somebody to tell
> the user that she needs to install this and that package (or
> automatically dl/install?) when she plugs in stuff.
Well, since I am not sure what would be the best way to do it - could
you please give me a hint how to call something depending on
properties? All I see now from hald documentation is /etc/hal/device.d
subdirectory - where I could put the script analizing HAL_* variables
and starting/stopping my daemon.

> About the battery stuff, perhaps Hal spec can recommend what keys
> should/may daemons set under *.battery.  For example, milliWatt
> remaining, time remaining, time to charge, charge percent, ...
> This way for example the battstat applet can simply query Hal
> tree for *.battery and show a list to the user...
Actually, current HAL has nothing about batteries. So I just hacked my
own lwm.fdi with some properties which make sense to me... The "unit"
properties is void for logitech (well, I am not sure, but for a
moment...) - but in can be "mWatt" etc.

> > I think this approach is nice because if other vendors than Logitech
> > want to ship such a daemon they now what properties to export.
Yeah, putting these properties into specs could be useful...

Sergey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lwm.fdi
Type: application/octet-stream
Size: 748 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/hal/attachments/20041130/760e88f6/lwm.obj
-------------- next part --------------
_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal


More information about the Hal mailing list