I just had a play with your Wii code, and though I’d give a few comments.
First of all, I think you should definitely rethink the way you’ve put everything into the Juce namespace. That’s really reserved for Juce classes and code, and this certainly isn’t part of it! There’s really no need to put it in there, so I’d remove all the JUCE_API and namespace stuff from it.
The other thing is that it doesn’t really seem to actually follow the Juce style like you say - the way it interacts with the bluetooth base isn’t really clear at all. I hope this doesn’t sound like I’m being cruel or anything - you’ve done a great job! It’s just not particularly clear how to actually use it.
I’ve dug out my own Wii code again; my new job has me actually developing games for the Wii, so it’s beneficial to be able to experiment with the remote at home away from my devkit. I’m going to have a go at merging our ideas and code, to see if I can get something a little easier to use. When I think of a ‘Juce style’ system, I imagine something like the audio/midi classes; just open a device and use it. For example,
WiiMote* wiimote = WiiMote::openDevice(0);
… where everything else is hidden. This is the sort of thing I’d had going before, but it looks like I need to grab the DDK again as I’m missing some headers.
I imagine I’m probably missing something though - I haven’t had the longest look at your code yet [I will be looking closer later this weekend], so please let me know if there’s a straightforward way of using it!
I hope this doesn’t read like I’m panning your work, as I’m really not. I’d just really like to get it to a point where it really is as simple as the rest of the Juce stuff is.