Support and General Use > Theming and Appearance Customization

My Themes will no longer work in the Current Build r30819-111021 - Clip

(1/3) > >>

KiwiCam:
It was suggested to me that I try the latest Rockbox build. Two of my themes no longer work (nOIsE and pULsE). I'm really enjoying creating themes, but I'm becoming demoralised, because I know there's so much more I can do with my ideas, but because I use so many Tags, Conditions & Viewports I am constantly pushing the Skin Buffer, which I understand to be the limiting factor regarding how far I can push my themes.

48.0KB's is a challenge and now the lastest build has reduced this to 40.4KB, which breaks my themes.

The manual specifically makes mention that the Skin Buffer is 80KB, which I WOULD LOVE to make use of. What happened to the 80Kb?

It also talks about a text file 'skin_buffer_size.txt" which would also mean I could be more creative with my themes. I've also tried this in the current build and that doesn't work either. I assume that I just place an "80" in the text file and restart the Clip. Correct?

PLEASE.

Am I correct in assuming that it's the Skin BUffer that is causing these theme limitations?
Is so, how can I get an increase in the Skin Buffer size?

If not, then what's causing the limitations?

[Saint]:

--- Quote from: KiwiCam on October 21, 2011, 06:38:28 PM ---It also talks about a text file 'skin_buffer_size.txt" which would also mean I could be more creative with my themes. I've also tried this in the current build and that doesn't work either. I assume that I just place an "80" in the text file and restart the Clip. Correct?

--- End quote ---

This feature the manual speaks of was reverted...and, apparently this was left in place in the manual.

This is an error, disregard it.

It would be nice if the feature itself wasn't reverted, especially as the feature itself wasn't in contention at all, only the way it was implemented. But instead of changing the implementation to one that everybody was comfortable with it was decided to just yank the whole thing, but...hey. That's a whole other kettle of fish.

<mournful violin music>
I too have "broken" themes that worked fine prior to recent commits...
</mournful violin music>


[Saint]

KiwiCam:
It sounded like a darned good feature. But, in addition to that feature removal, the buffer appears to have been reduced for future releases. This sucks. You might as well not have the ability to theme at all, if you can't be creative with them. I want to go WILD with these things. I'm brimming with ideas. It's incredible what we should be able to do with these themes, and I'm so enthusiastic about this. But, I'm striking what seems to be a deliberately placed artificial barrier, and I don't know why.

Admittedly, having a 48KB buffer has helped me be as creative as possible, so that's been great but I might as well just give up with doing anything more, if it's going to be lowered 40.4KB. I'm pushing the limits with 48KB. I'd like to be pushing the limits of 80KB or 120KB, or more. Is their a physical limit to this buffer size? Or, will the Clip just become noticeably slower to operate?

What's the reason please as to why this option was removed, and why does it need to be lowered to 40.4KB?

I'm at the point, where I can't make, more interesting and (IMO) better themes. I'm certain the Clip can handle it. Easily.

I'd like to start doing SBS's and FMS screens, but that forces me to make, what I feel now, are necessary sacrifices in my current WPS screens.

Yes, I am ranting, and I'm sorry if this gets me off on a bad footing with some important people here. But this is the first time I've ever actually been interested in doing something like this and I feel I'm contributing something here. I'd like to do more.

I'd really appreciate it if this buffer situation could be looked at again. A reinstatement of the .txt file would be my preferred option.

Please.

Llorean:
Saint has been a little unclear. The feature wasn't removed, it was removed until it's implemented in an agreeable way. Even the person who wrote the previous version admitted it wasn't the right way to do it.

As it stood, someone couldn't install your theme from the theme site and just expect it to work. They'd have to make sure their text file allocated the appropriate amount, which might be impossible if they discovered the theme wasn't working once they turned on their player on the bus. An appropriate solution should be something either a user can configure within Rockbox, or better yet, not depend on the user to take action at all other than possibly rebooting the player.

So please, curb your rant a little. There is desire to make sure that themes work. While there may be some constraint on theme size (the players don't have infinite memory obviously, and there's a need to balance its availability to other things), it should allow a fair amount of complexity to be involved. What we're dealing with now is more "bug" than basic "limitation."

Obviously themes working previously (to the contentious commit) and not working now is clearly a bug. If it's not in the tracker documenting when these themes stopped working (not with the removal of that commit, but the first time they stopped working) it needs to be. Other than that, it's just an issue of someone coming up with a more comprehensive fix to the problem, rather than a temporary bandaging over of it.

KiwiCam:

--- Quote from: Llorean on October 22, 2011, 03:18:32 AM ---
So please, curb your rant a little.
--- End quote ---

Consider it parked and in the garage.

But, why the reduction? Why not, at the very least, keep it at the 48.0KB? Couldn't it just be pushed up just a little bit more than what it is now?  ???

Navigation

[0] Message Index

[#] Next page