Rockbox General > Rockbox General Discussion
Proposition: SimpleBox
Febs:
--- Quote from: mnhnhyouh on September 23, 2006, 08:25:38 AM ---3) Make it more intuitive
(snip)
3) I have yet, besides option 2) seen any indication of what this might mean.
--- End quote ---
You mean besides my suggestion that the "Play" button always go to the WPS, from both the browser and the menu system? ;)
I would implement this feature myself if I could. In fact, I have looked into the code and while I have learned a great deal about how it works, unfortunately, I just haven't had time to learn enough to make the changes that are required to make this work. So for the time being at least, I have to just keep making the suggestion in the hope that someone will implement it.
mnhnhyouh:
--- Quote from: Febs on September 23, 2006, 08:37:48 AM ---
You mean besides my suggestion that the "Play" button always go to the WPS, from both the browser and the menu system? ;)
--- End quote ---
I am using Senabs second last build, and it is implemented on that. Well unless you are a couple of layers into the menu, then sometimes it doesnt work....
:)
Forgot that I am not using the standard build.
h
Llorean:
I thought there was a working play-button-to-wps-from-menu patch already? Like, on the tracker. That someone just needs to be browbeaten into committing..
To follow the previously posted breakdown of some of the general concerns in this thread, these are how I would address them:
1) What about things Apple doesn't have but iRiver does? The idea is for Rockbox to have the same menu layout on all targets so someone can updgrade to a different Rockboxable player and be on familiar ground. Again, it's vitally important that choices *not* be made simply because that's what a commercial firmware did. As well, hiding the options just makes it more of a hassle to get to them once a user *is* ready to use them, and I don't see how having them available from the start can actually *confuse* someone. If you don't know what it does, don't change it or look it up. How confusing is that?
2) How do graphics "make it more intuitive" since all they do is the exact same things as word. Graphics are only more intuitive for the illiterate, and it's very hard to express "Sound Settings" as an image, let alone "Playlist" and various other things.
3) What do you even mean by "more intuitive" exactly here? I mean, ideally that means "things are where a person could reasonably expect them to be" as in the category and submenu names follow a progression that if someone thinks "I want to change the equalizer" and sees several choices, one of them is clearly enough the one they think they should go through to find it. In most cases this is already true, though I've no doubt a few things are in unintuitive places. If you mean something else with "intuitive" please expand.
4) As has been said, it makes the most sense in to return to the filetree/tagtree since if you're using the device for the intended purpose of "being a file-based music player" the filetree is the primary place you return to, as most menu settings aren't changed as often as you start new playlists or pick songs.
5) Removing options doesn't really "improve" the situation so much as sticking your head in the sand and trying to pretend it's not there. One could respond "Why remove them when you can simply ignore them?"
Febs:
--- Quote from: Llorean on September 23, 2006, 08:45:18 AM ---I thought there was a working play-button-to-wps-from-menu patch already? Like, on the tracker. That someone just needs to be browbeaten into committing..
--- End quote ---
I just tested that patch against current CVS on my iPod 5G. It applies cleanly. The "quick exit" part works, but the "Play to WPS from within menus" does not.
I'm compiling a build for my H100 right now and will test it there.
Llorean:
Well, it's rather easy for things to fall out of date, I suppose.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version