On Sat, Feb 10, 2001 at 03:51:00PM +0000, Christoph Bartelmus wrote:
> Manuel Estrada Sainz "ranty@..." wrote:
> > A couple ideas I am planing to implement:
> > o Making irexec and irxevent "well behaved" daemons
> > o Make lircd or some startup script launch ir???? daemons for selected
> > users.
> > o Maybe rework the configuration file format, the current format is
> > IMHO a pain to write.
> > o I understand that this point could be problematic, as whoever
> > chose the current format probably had his reasons. I mainly
> > propose some discusion.
> > o The new format could be simply a backwards compatible
> > extension to the current one.
> Manuel, thank you for your offer to help!
> I'm quite happy with irexec and irxevent, so I don't think there's real
> need for the first and second point (YMMV).
I personaly miss those features, so I will do it for myself and post it, it
is a matter of 10 minutes anyway.
> What in fact is lacking is a
> better documentation how to set up both. Maybe a HOWTO like doc would be
> the best approach for this.
I will think about it, but don't hold your breath.
> But the config file definitely is an issue. You are absolutely right that
> it's a pain to write. The question just is whether the situation will be
> better if there's a *program* that generates the config file.
> Currently I won't agree with a change of the current format. In my opinion
> it's flexible enough.
Maybe some macro based config file (with m4?) which converts into the
> There are few things I encountered that couldn't be
> implemented with it. As it's already quite complicated I also don't think
> it should be extended much. One problem with the current implementation is
> that each application has to keep track of the mode and IR sequences
> itself. This can lead to inconsistencies between applications. But this is
> nothing that couldn't be solved by a daemon application that would manage
> these internal variables.
How about a daemon which:
o parses the config file
o keeps track of IR sequences, mode and all
o sends only "config" strings to clients
o clients don't read .lircrc
o clients don't keep track of anything, simply obey orders
> If you are still interested my proposal would be to implement a GUI that
> helps you create a config file. I have already made a small screen design
> some time ago and IIRC Pablo already started implementing a bit.
Please, show me the screen design and the code and I will try to do something.
How about Perl/Gtk or Python/Gtk as the language? I will probably end up coding
it in good old C anyway though.
Also, how about some way to tell who has the remote, so that only that user's
clients get/ovey IR sequences?
God grant us the serenity to accept the things we cannot change, courage to
change the things we can, and wisdom to know the difference.