WiiLi.org

[mik]

Update!

Cadex has send me the code, which was basically
the same like mine an didn#t work on the Mac.

So there is an issue with the BT-Lib on the Mac,
which will now probably be fixed by the developer
of avetana BT.

On PC the upper code should work wit the BTLib.

[Cha0s]

I'll confirm this. I tried something similar and met with the same results. I've emailed Avetana and hopefully they'll fix it. I'm currently developing Java interface for the WiiRemote and hope to have it done in the next few days. It will support all of the basic features as outlined in the Wiki (assuming that's up to date ).
_________________
Cha0s

[mik]

Nice!
What are your plans for the Lib?

I would like to be able to use more Wiimotes at the same time and would like to support this with something like a MultiDevice MotionListener etc.. Someting like: http://www.cs.umd.edu/hcil/mid/
Also some gesture stuff would be nice.

Too bad i'm facing those BT issues on the Mac at the moment. Hope aventana will fix this issue that i can continue working on it.

But I am looking forward to see your lib.
Mik

[Cha0s]

My library already supports multiple remotes! Theoretically, it could support up to 7 (a limit imposed by Bluetooth, not Java). I've tested it with four and it worked fine (I did have to do some trickery to make sure it didn't discover the same remote twice. >_<). Basically, I'm trying to make this as Java-friendly as possible, so you'll be able to register a listener with each instance of WiiRemote. The finding mechanism for multiple remotes is somewhat clunky now (due to listener registration issues), though you can of course just find one remote multiple times (this makes it easier to register listeners).

I have currently implemented:
-Button input
-Vibration control
-Status report input
-Read Data
-Accelerometer input (mostly)
-Interleaved data input (not tested)

I've made a pretty programmer-friendly user interface. I hope to have write data (this is pretty easy), IR, and possibly the speaker done by the end of next week. Then, I need to do the extension ports and I'll be done. When the library is complete, I will release it as a free download. I've also been javadoccing, so it should be well-documented as well. I welcome any suggestions! I may put up the Javadoc in a few days if you'd like to comment on it.

EDIT: Here's a good question, regarding the way WiiRemotes are found... There are a few methods I've considered. They are as follows:
1. Single WiiRemote is queried in a blocking method and returned.
2. Multiple WiiRemotes are queried in a non-blocking method and placed into an array or Arraylist passed in by the user.
3. Multiple WiiRemotes are queried in a non-blocking method and returned in events. This would require a WiiRemoteDiscoverer class and a WiiRemoteDiscoveryListener class, or something to that effect. This is more flexible, but requires a lot more work to setup for the user.

If you haven't already guess, I'm currently using methods 1 and 2. I'm considering hopping to 1 and 3, since 2 is REALLY clunky. Your opinion?
_________________
Cha0s

[Amablue]

Yay!

Java's the only language I'm really good in, so it'll be nice to be able to do stuff with the Wiimote in it, rather than just making little demos that just use a mouse script.

[mik]

Wow, that sounds nice.

I think i didn't completley understand you're architecture yet, but that is fine if it is documented well.

Are you talking of Threads whne you say non-blocking? And, so at the moment all devices will be detected at once (2) and you want to change that to 3, that devices can be resgistered at runtime, right? That would be perfect.

Are you planning to release the src as well?

Anyway, thanks for your effort.
Can't wait to get my hands on this.

cu
Mik

[deceased]

Nice. I work in mostly Java at the moment and would love to see this.
_________________
-deceased-

Wiili - a gnu revolution