Delete Menu entries

[AlexP]

Is VMware any better regarding the initial cross-compiler stuff?

In CygWin ../tools/rockboxdev.sh takes a million years to complete, but at least it's done for you right?

Why are you running rockboxdev.sh in cygwin?  We supply precompiled binaries for it.  This is step 3 of the instructions...

http://www.rockbox.org/wiki/CygwinDevelopment#Step_3_Select_the_Rockbox_mirror

[Serenity]

seani, I'd very much enjoy this feature in Rockbox (sounds like it won't happen, but....) and was very interested in your "*Not* another 'Can we have...'" post a bit ago.

Apart from myself not using a good half of the menu options, the only thing stopping me from setting up an iRiver H320 for a friend of mine is the overwhelming number of options than will only confuse him (he's an old hippie who just wants to record his friends' jam sessions).  If I could delete (or just hide) menu items according to a master list, my friend (and probably my wife as well) would love Rockbox.

As for the hellish support issues that would arise from having clueless end users hiding critical options, how about an un-hide-able menu option for "Show All Options" or an indicator at the top of the menu by the Rockbox flag that says "Full Menu" or "Custom Menu"?

I'm not a programmer, so I've no idea how difficult it would be to implement.

[[Saint]]

Why are you running rockboxdev.sh in cygwin?  We supply precompiled binaries for it.  This is step 3 of the instructions...

http://www.rockbox.org/wiki/CygwinDevelopment#Step_3_Select_the_Rockbox_mirror

The short answer to this would be, I was guessing.

I got stuck, had no idea what I was doing/doing wrong so I took a guess...

My Cygwin setup didn't go that smoothly for some reason, well I thought it had (novice cygwin user had no ability to determine otherwise) but when it came to the actual compiling part of creating a "Test Build" it froze for some time and then spat out a list of errors I gathered after some time were reletive to the cross-compiler directories.

I read http://www.rockbox.org/wiki/CrossCompiler#Step_2a_Automatic_build, ran rockboxdev.sh, and all is now well in compilerville 

The Cygwin setup directions are lacking....at best.

CygwinDevelopment Wiki page should include prompting the user to download the package:

NET/cURL

and also should include some basic directions on using nano from the command line but that's a different post altogether...


[St.]

[Llorean]

NET/cURL is completely unnecessary if/when the other steps are working properly. Rockboxdev.sh shouldn't be necessary in cygwin unless something is wrong, and the ideal solution wouldn't be to add that to it, but rather to fix what's actually wrong.

[GodEater]

The short answer to this would be, I was guessing.

I got stuck, had no idea what I was doing/doing wrong so I took a guess...

My Cygwin setup didn't go that smoothly for some reason, well I thought it had (novice cygwin user had no ability to determine otherwise) but when it came to the actual compiling part of creating a "Test Build" it froze for some time and then spat out a list of errors I gathered after some time were reletive to the cross-compiler directories.

Did you attempt to run step 3 at all? Did it go wrong? Or did you just miss it somehow?

If there's something we can do to improve the instructions or the process we need to know the answers here. Running rockboxdev.sh is a very bad idea under cygwin on account of how long it takes to compile.

[AlexP]

and also should include some basic directions on using nano from the command line but that's a different post altogether...

I don't think it should.  The use of e.g. nano is very basic linux usage, and this isn't "How to use linux" - there is google for that.

Besides, the instructions are type "nano filename" then look at the key controls on screen.

[Lope]

Would it be better if Rockbox only allocated DB memory if?
A: The player has a non-empty database
B: DB is created
(I'm not familiar with RB architecture)

[torne]

Rockbox only allocates memory to store the database if loading the database to ram is enabled, but the database *implementation* still takes up some memory: the actual code and so on.

[Lope]

oh you mean the implementation code takes up disk storage?
A couple of MB is quite significant on a multi-gigabyte MP3 player though.

[saratoga]

oh you mean the implementation code takes up disk storage?

Yes, and space in RAM as well.

A couple of MB is quite significant on a multi-gigabyte MP3 player though.

RAM is what people are concerned about, since some devices have as few as 2MB total.

[Lope]

I see.