_tv_ with regard to integrating with XBMC keep the following in mind (I just copied and pasted my comment from elan's blog):
Quote:@elan
“In terms of Bluetooth, d4rk is working on implementing a UDP client-server protocol, and planning on having an external server running which communicates input events to a running XBMC.”
It’s actually an internal server that receives the event messages. Also the messages aren’t restricted to purely input events. For example, there is also a notification event that pops up a little window on screen with a message. What’s external would be the various clients that communicate with the server.
“I have no issue with people doing the same for now and internally supporting OS X Bluetooth HIDs.”
The whole point of the new protocol is to abstract out device specific code and at the same time not compromise on speed. At this point, I wouldn’t encourage anyone to write any device specific code that ties in tighlty with XBMC, Bluetooth or otherwise, since it won’t get accepted. Ideally write your code so that the device specific portions are modular so that it can be reused using the new protocol.
The protocol is close to completion at this stage and basic commands are functional. I already have a few working examples. I’ll be posting examples, documentation etc on the forums once it’s more usable.
As mentioned, the intent of the new protocol is to decouple device specific code from XBMC code. This has quite a few advantages. Firstly, XBMC will not need to be recompiled for every new device that needs to be supported. Secondly, users/developers can write their own input "drivers" in their language of choice (which can eventually be
packaged along with the official XBMC distributions once that gets going).
The new protocol will support both analog and digital button events as well as mouse events, which can in turn be used by devices that have accelerometers, support motion sensing etc. Since it's a network based protocol, devices that aren't hooked up to the computer that XBMC is running on can be used as well (in fact the computers could be running different OSes).
The new protocol will be supported in the Linux, Mac and Win32 builds and possibly even the XBox build.
Anyway, just keep these things in mind during your development.
PS: Is your program open source?
).
And this app, it's not even worth really open sourceing atm, so bad example for everyone, as it is my first apps. Do you have any time when to expect input abstraction to finish? Which is closer, week or month? I'm really looking forward to it. Thanks for the nice job.
