> And how did they tested SplashPlay? That app needed two hardware
> ('pod' and 'panel') which are not released yet.Hey, contrary to other apps, the apk files as well as the source code to SplashPlay ( http://splashplay.co.uk/ ) are fully available (as part of the OpenIntents distribution), so you may try it out yourself: http://code.google.com/p/openintents/downloads/list We stated clearly in the readme that bluetooth connectivity was simulated (mocked up), but implemented the back-end on the phone: Run the application, press play: You see that the chord display is in sync with the tune. It is not hard to imagine that the same chord changing commands could be sent to a hardware device via bluetooth. We had a couple of usability gimmicks that will make practising really convenient: * The A/B repeat button lets you specify a loop region. * Click any chord to jump to that position. * Click and drag over a couple of chords to mark a loop region that starts playing automatically. All of this is no mock-up, but fully functional. (and open source :-) ) Please try it out. We look forward for any feedback, as we will try to bring the software backend to SplashPlay to the next level in round 2 :-) Peli http://code.google.com/p/openintents/ http://www.openintents.org/en/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Challenge" group. To post to this group, send email to android-challenge@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-challenge?hl=en -~----------~----~----~----~------~----~------~--~---
