2007/7/11, Matthew Bodkin <lists@...>:
> Hi All -
I'm the member of Ubuntu Media Center who have done this new name space and
I've been having some off-list discussions with several groups (Ubuntu
> related mostly) about implementing the LIRC standard namespace since we
> created the online LIRC Config and have database of button names and
> To recap the current situation (and bring anyone up to speed):
> - defines what buttons events are generated by each remote
> - irrecord'ed for each remote
> - no standard naming of standard buttons (play, pause, vol+, etc)
> - defines what button events are accepted by each program
> - eg: "prog =3D mythtv", "config =3D Left"
> - also maps which lircd.conf event should trigger an lircrc program
> - eg: "button =3D vol+"
> ** The exponential problem is every lircd.conf needs a custom lircrc
> to correctly map its non-standard button names to non-standard events.
> To recap what's been proposed for the standard namespace:
> - define standard events
> - use standard button names for standard events (to prevent vol+ vs
> VOLUME_UP mismatched lircrc configurations)
> ** Doing this will make the vast majority of remotes and buttons names
> match program events, and thus work with LIRC programs "out of the box",
> without any manual configuration.
> /end recap
> So we would need standard lircrc's for all LIRC compatible programs
> And an easy way to 'upgrade' hundreds of lircd.conf remotes, or at
> least provide end-users any easy way to upgrade their lircd.conf.
> The Ubuntu people are maintaining a 'conversion standard' here:
> So it appears that it would be a good idea for us to add the following
> to our online LIRC Config (http://lircconfig.commandir.com/ ):
> - Add the new standard lircrc's
> - Add JOINing lircd.conf buttons (already in our DB tables) with the
> above nns_light.txt mapping to generate new standard lircd.conf's
> Any thoughts / comments on this?
For the moment the work is not closed. See the stats. There are some name
not traduced. For the moment I'm alone to do this work. if some of you want
to help, especially for the name of mouse button.
Another problem is that we have define a name space, with the little set fo
remote. maybe it can be good to do the same on every remote control.
To include the new name space, I've done a script that convert lircd.conf.
Be in touch with me :)
Have I correctly recapped and summed up the situation?
> Are program devs (MythTV, FreeVo, VDR, Xine, Mplayer, VLC etc) all on
> board with setting a standard, since they would need to support it?
> Is anyone else already doing this?
> Systems Design
> InnovationOne Applied Technology
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.