Will somebody do the legwork, based on the HID remote notes I have dumped in the Gyration thread, and make a device template that uses wminput to handle the wiimote? preferrably someone who has a mobile orbiter in use?
First of all, please forgive me for any noob questions. I can get around Linux and C++ well enough, but I'm very new to LinuxMCE with a recently setup core, MD, wiimote and no orbiter. Ideally these questions are already answered somewhere and you can just point. However I have not yet found them. When things make sense, I think a clear step-by-step wiki page is in order. I can certainly help with that.
I appreciate the valuable info you put in the other thread. Could you point me to additional information for creating device templates?
I took a stab at a device template based on what I could find in the wiki, which sadly wasn't much. I looked at the webadmin for creating device templates and aside from not understanding many of the fields, based on comments in the forums here it seems clear that's only one piece of the puzzle.
As a starting point, I would like to know the top-level flow of events and from there can ask more informed questions / more likely to figure things out on my own.
Let's take our case here of the Wii remote. I assume there are two levels of polish for the device template for lack of a better term. The first would be to have the buttons do what we want (ala create a Play/Pause key being the top priority here, methinks). The more complete version would also handle creating the wminputd script, wminputd.conf, etc as described on the wiki so that when it's detected all those things are setup automatically. Am I correctly understanding the scope of responsibility for device templates?
Let's focus on the first level of polish as the remainder is clearly laid out on the wiki and should be easy to automate.
My first question is associating a device with a template. When creating the template I see you can specify a MAC range, etc. How can I tell that the device has been associated with the template? I assume one of the log files would contain that info? Where/which one?
When a template is loaded it reads the mapping and configuration as you pointed out in your post. Mapping is irrelevant for the Wiimote task as the wminputd.conf is doing the mapping. So configuration is the only one we're interested in for this case.
You mentioned the syntax for configuration is:
The UDH,Y portions are clear (thanks to your post). x scancode is the same as keycode, correct? For some reason I thought scancodes were more raw than even keycodes, but xev is only showing the keycode and keysym, so perhaps I'm mistaken there.
The RemoteMapping_Entry I'm not clear on. You provided an example of a RemoteMapping entry early in your post, but I missed where this is actually defined, whether this needs to be defined for every template, or where to find the list of existing mappings for standard actions (like Play/Pause).
Now with those pieces, it looks like making the right entries in #59 Configuration - Default Value would do the trick (assuming there's an existing RemoteMapping to point to).
So where do the changes for bluetooth & bluetooth_dongle code enter the picture? (Your post here: http://forum.linuxmce.org/index.php?topic=4755.msg51423#msg51423
said those are needed too).
Long post, but I hope it makes sense. I'll write a wiki article when I understand things myself.