Rockbox

Tasklist

FS#5700 - XML Menu Config

Attached to Project: Rockbox
Opened by Gnelik (Gnelik) - Sunday, 23 July 2006, 07:12 GMT
Last edited by Jonathan Gordon (jdgordon) - Sunday, 15 April 2007, 13:13 GMT
Task Type Feature Requests
Category User Interface
Status Closed
Assigned To No-one
Operating System All players
Severity Very Low
Priority Low
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Many users sujested menu reordering here, i sujest to make XML menu file like this:

<menu menu_type="one_per_screen">
<subitems>
<item type="dir" menu_type="list">
<lang_file_capt></lang_file_capt>
<image>1.bmp</image>
<subitems>
<item type="command">
<lang_file_capt></lang_file_capt>
<image>1.bmp</image>
<command>browse_plugins</command>
</item>
</subitems>
</item>
</subitems>
</menu>

With some modifications, and to make visual utilite to generate such files.

PS: menu_type= is how menu items shown on the screen one per screen such as in nokia phones, or in the list.
This task depends upon

Closed by  Bj√∂rn Stenberg (zagor)
Wednesday, 09 May 2007, 07:11 GMT
Reason for closing:  Rejected
Additional comments about closing:  Closing all feature requests.
Comment by Bryan Childs (GodEater) - Wednesday, 24 January 2007, 12:39 GMT
I'm thinking about doing something similar to this - but I absolutely refuse to use an xml file for this.

I imagine a file which looks a bit like this :

Caption->Function

Much easier to parse.
Comment by James Munro (xen) - Tuesday, 20 March 2007, 14:53 GMT
This is something I am interested in. What would be the problem with using XML? You have mentioned that it is difficult to parse, but there are many existing XML parsing libraries available. I only have experience using one named TinyXML, it worked flawlessly. However I do not know of the efficiency of porting it to Rockbox.
Comment by Bryan Childs (GodEater) - Tuesday, 20 March 2007, 14:57 GMT
XML is a reasonable solution on a big powerful PC - but it's completely overkill for an embedded target. What meta-data do you need to store about each entry other than it's name, and what it does ?

Having to port over an XML parser library, no matter it's source, is probably going to be a complete nightmare because I bet you can't find one that doesn't use malloc() or similar.
Comment by James Munro (xen) - Tuesday, 20 March 2007, 15:11 GMT
Sorry I hadn't really thought my response out, you are completely correct. Do you think there is any other logical decision to make syntactically, Something users may be familiar with? This is merely a suggestion.

Also with the parser: for each entry, how is the 'function' to be determined, perhaps by a defined keyword for each menu function?
Comment by Bryan Childs (GodEater) - Tuesday, 20 March 2007, 15:13 GMT
I think the syntax is going to initially down to whoever starts coding this - I've not had time personally.

Given that the menu structure was completely overhauled a while after I initially added that comment to this FS#, I'm not sure how I'd go about doing this at all actually.

Give it a crack and see what happens!
Comment by Jonathan Gordon (jdgordon) - Sunday, 15 April 2007, 13:13 GMT
GodEater: with the new menu system this is actually fairly easy to get working (assuming the menus you want are all accessable from the main setting menu (not the main rockbox menu).

That said, it is incredibly unliekly that a patch for this would be accepted

Loading...