Rockbox Development > New Ports
Rockbox as an Application (Android, WebOS etc.)
[Saint]:
You were using a truly ancient build from kugel with a patch that isn't in svn, and almost certainly never will be, to increase the list item height.
So its no surprise it didn't look as you expected when you installed an svn head version.
I've had multiple testers for this theme port, and I can honestly say that with the 48pt font I have never had a complaint about touchscreen usability in the lists.
I /could/ of course increase the font size, but I think (and testing so far has shown) that 48pt is a good balance between list height, total items displayed in the list (you don't want the menus to be needlessly sparse when scrolling long lists), and usability.
I continue to update these theme ports as I develop and work on new ideas...and nothing is set in stone.
I can tell you, though, that the only way (for now) you'll get the lists the way you wanted them is to revert to the build you were using if it still is hosted anywhere. That patch isn't going to get into svn, I'm ~99% sure of that.
There are sane ways to alter the list item height with the skin engine on a per screen basis (committed recently) that I would find to be an acceptable solution as opposed to forcing gigantic lists in all cases where a list is drawn.
This would allow for an (optional(depending on how creative I'm feeling)) way to expand only lists that need it (menus for instance), and not the lists you don't want to have vast amounts of blank space (long scrolling lists).
[Saint]
a_b_c_d:
--- Quote ---I've had multiple testers for this theme port, and I can honestly say that with the 48pt font I have never had a complaint about touchscreen usability in the lists.
I /could/ of course increase the font size, but I think (and testing so far has shown) that 48pt is a good balance between list height, total items displayed in the list (you don't want the menus to be needlessly sparse when scrolling long lists), and usability.
--- End quote ---
I agree it's a good compromise between touchscreen usability and handling long lists.
But for those without sensitive fingers: Would it be time-consuming to add an option that provides bigger fonts (at the moment I can switch between 36-cabbiev2-[bold], 36-cabbiev2-[regular] and 48-cabbiev2-[regular])?
--- Quote ---I can tell you, though, that the only way (for now) you'll get the lists the way you wanted them is to revert to the build you were using if it still is hosted anywhere.
--- End quote ---
I've got the ".apk"-file still on my phone, but I think I will use the newest version with 48-cabbiev2-[regular] anyway, although I'd prefer menu items that are a bit higher.
--- Quote ---There are sane ways to alter the list item height with the skin engine on a per screen basis (committed recently) that I would find to be an acceptable solution as opposed to forcing gigantic lists in all cases where a list is drawn.
This would allow for an (optional(depending on how creative I'm feeling)) way to expand only lists that need it (menus for instance), and not the lists you don't want to have vast amounts of blank space (long scrolling lists).
--- End quote ---
*sign*
And thanks for the fast support. :)
Falco98:
Could anyone point me to a build they think would be optimal for use on the Thunderbolt? I was running a decent one ago on my old Eris, a while ago, but honestly I forget whether I found the build here or on another forum. A brief browse of the last few pages has left me generally unsure which one I should try to use :-P
[Saint]:
--- Quote from: Falco98 on September 21, 2011, 09:12:26 PM ---Could anyone point me to a build they think would be optimal for use on the Thunderbolt? I was running a decent one ago on my old Eris, a while ago, but honestly I forget whether I found the build here or on another forum. A brief browse of the last few pages has left me generally unsure which one I should try to use :-P
--- End quote ---
RaaA doesn't care about anything except the screen dimensions and the Android version.
So, "optimal" in this instance just means:
"an Android OS greater than 1.6 and a RaaA .apk built for a resolution the same as my device or smaller"
That's all.
The build doesn't need to be the exact screen dimensions, but it cannot be larger than the screen dimensions in either width or height. Builds for resolutions smaller than the devices LCD resolution will be aligned to the top left corner and the rest of the screen will remain unused.
As for availability, the *only* RaaA .apk I recommend installing is:
rasher's unmodified daily builds
As these builds contain no third party patches that may or may not be applied/built correctly, and they reflect the current svn state of RaaA.
Just remember that these builds are *unsupported!*, so don't lodge bugs against them, and they are not officially sanctioned by the Rockbox project. They are provided by rasher so that people may test the current state of RaaA.
Remember, RaaA is still officially "Unusable" as stated on the main page.
[Saint]
Falco98:
--- Quote from: [Saint] on September 22, 2011, 09:48:58 AM ---As for availability, the *only* RaaA .apk I recommend installing is:
rasher's unmodified daily builds
As these builds contain no third party patches that may or may not be applied/built correctly, and they reflect the current svn state of RaaA.
--- End quote ---
Thanks, this is basically what I was looking for :) As I said, I'd used it on my eris (sloooooow) and it worked okay there, except for the inability to move an app to the SD card and the eris' built-in memory became an extreme limiter with only a handful of apps installed. By this point I didn't even remember where I got the build I had on there, but this was probably it (but presumably updated some, by now).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version