>> entirely off topic. No, this has nothing to do with android native >> widgets.
Yes, I was being cheeky. step 1) the playback engine is made into a library - being worked on in gsoc step 2) a *entirely brand new* java UI is built around librockbox/warble iirc? step 3) ??? Step 3 is a big one; there's a lot of Rockbox that's not playback code but which is a good reason to prefer using it over other Android players (e.g. database, voicing, quickscreen). Plus if we end up with 2 seperate UIs, then that's potentially twice the work to add new features etc. Could the seperation be "per-widget", with theming/viewports used to glue it all nicely? pondlife
