View Single Post
Old 02-14-2013, 01:33 PM   #94
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Yeah... the best solution for all devices is what evades.

Choices:

I suppose a choice of "Expanded" and "Panelled" is in order. Either global in some config file or other (eugh) or on the screen at all times (I think I like this)

And while we are at it... a choice of "Die on command" or "Do next Command" would also no doubt be of benefit... NOT global in some config file: on the screen at all times. perhaps even embedded in the button itself - but I don't like the navigational implications of that.

Also a "Favourites" filter could maybe one day make some sense if this thing gets colossal. but once again I want a GUI god to step in from the heavens and say "LO, HERE IS THE PERFECT DESIGN!!!". Not hearing any angel trains at this time unfortunately.

What no Touch?

I honestly am starting to think that keyboard shortcuts auto assigned to the various buttons would be a good start (we could do 26 shortcuts without too much pain)
This will only help on "Key Enabled devices" but those are the ones that really bother me for this "collapsible" design concept. "Less Clicks" is more betterer. The final solution with hopefully result in LESS clicks not more on those devices.

The ability to "Jump" to the 1st letter of a matched button on the same page (or even in the entire results set perhaps) could be an alternate solution taking advantage of the keys of course.

What no Keys?

The 4 with it's general lack of keys and Touch is of course the most badly affected in the whole "clicks" stakes, but since I do not have one... well. makes it harder to judge, I have played with one for a day so I have half an idea.

What no plan?

so yeah. in précis: It's not so much the code as the best solution for all devices.

I should do some click diagrams and calculate some shortest paths I suppose.
I currently have 31 buttons on the touch and TBH on the touch having lots of pages is not such a pain. but yes 20 pages would be a real chore. especially if you only used say.. 4 of the buttons regularily. and they were in the middle (since the end is one click back away)

And. For the record. I know you know all this. I'm just saying it out loud.

Anyone with Angelic Guidance feel free to step in now with your "Lo! Advice!"

So... Paper. dull diagrams. guts coding. decisions on choices. then hopefully a little divine intervention from Ixtab too, since my code is always an affront to processors everywhere.

bit by bit, byte by byte it progresses.
You make excellent points.

Last edited by twobob; 02-14-2013 at 01:41 PM. Reason: betterer, solution
twobob is offline   Reply With Quote