[ohm] monitoring INPUT state
Nils Faerber
nils.faerber at kernelconcepts.de
Fri Jun 29 08:49:39 PDT 2007
Richard Hughes schrieb:
> On Fri, 2007-06-29 at 17:20 +0200, Nils Faerber wrote:
>> Question that comes to my mind here is would we end up with two idle
>> modules or one generic idle module with additional "idle source"
>> plugins?
>> I would actually prefer the first in order not to duplicate code.
> TBH, the xorg idle plugin doesn't share hardly any code with the INPUT
> plugin, apart from the standard boilerplate stuff. You can just choose
> one in /etc/ohm/modules.ini and then that will be used everytime.
>
> I don't think having lots of plugins is a problem, indeed, I think it's
> quite a good thing being able to pick and choose for a specific device.
Oh oh... probable misunderstanding here...
I thought that it might be a good design decision to create first an
idle plugin which will handle aggrgating data to decide if an idle state
is reached and possibly which state of idleness.
X11 and the input events would then serve as data input plugins for this
idle module.
Else you might end up with two plugins that both measure idleness
differently and have to decide one idle over the other - which is idler,
X11 idle or input idle?
It could be useful too to have both source activated but then you have
to make a choice.
> Richard.
>
> p.s. all the general code is in git. review welcomed. :-)
Oh I will, thanks!
Just got the pointer beginning some days ago ;)
Thanks again!
Cheers
nils faerber
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48 Fax: +49-271-771091-19
D-57072 Siegen Mob: +49-176-21024535
--
More information about the Ohm-devel
mailing list