> 1) Make RaaA use all of the existing Rockbox UI code, and just talk to
> that code with whatever interface is availble on the device running the
> application.
> 3) Use as much of the Rockbox UI as necessary, using native UI elements
> where appropriate to improve usability. Primarily, replace the list
> with a more 'normal' file browser and menu structure, in many cases
> while preserving more custom screens that won't have an analogue in
> other software.
>
>
> I have to side with those two options. Rockbox UI cleverly uses SDL which covers many many platforms. Remember that Rockbox UI already runs on motorola mobile phones which support SDL (running linux). SDL is aslo ported to Windows CE which is a vast pool of future targets. It would be a shame to use a less crossplatform-able framework.
>

My plan from last year was the following:

1) Remove IFDEF SIMULATOR stuff and move SDL code into the target tree so that you can compile rockbox as an app and not a sim. (this was actually completed)

2) Work on actually getting SDL and rockbox to compile on another target (this proved quite difficult for me on Windows CE)

3) Begin platform specific optimizations

IMO the best way to do things is to leave SDL in place entirely, but to put it into the target tree so that new platforms can use it as needed, or reimplement functions as native code if SDL imposes too much overhead or is for some reason unsuitable.

Talking about changing the rockbox GUI is premature. We don't have the basics in place, and we probably won't for a very long time.

_________________________________________________________________
Quick access to Windows Live and your favorite MSN content with Internet Explorer 8.
http://ie8.msn.com/microsoft/internet-explorer-8/en-us/ie8.aspx?ocid=B037MSN55C0701A
Received on 2009-03-30