Rockbox mail archiveSubject: Re: themes, skins, backdrops and RAM usage... (i.e sure to be controversial)
Re: themes, skins, backdrops and RAM usage... (i.e sure to be controversial)
From: Thomas Martitz <thomas.martitz_at_student.htw-berlin.de>
Date: Tue, 22 Dec 2009 12:42:43 +0100
Am 22.12.2009 12:18, schrieb Matthias Mohr:
> Hi everybody,
>> - the ability to set colours to work on the fly (i.e. as it always
>> did, most
>> useful for actually seeing the colour/readability on target. A
>> reboot, or
>> text file editing, should not be part of this)
> I absolutely second that!
> Users will not understand why they need to reboot or edit a text file
> for such a "simple" task as changing colours...
> And the ability to dynamically use the colour settings of the menu in
> a viewport by using "-" as colour should absolutely be kept (and fixed!)
> That allows the use of user colour preference in themes.
I agree too.
> E.g. you could make parsing a two-way process and only detect the
> memory needs (small, medium, large, very large) in the first pass.
> The first pass could be done when the user selects a new theme or the
> themes could define which size they need.
> If the new size match the previous one (e.g. still "medium") it could
> keep the current buffer size;
> if the new one needs less size (e.g. previous "medium", now "small")
> it could define the new buffer size but still use the current one; the
> new size will be set and used after next reboot.
> if the new one needs more space (e.g. previous "medium", now "large")
> it could define the new buffer size and tell the user to reboot the
I like that idea (I think it has come up before, but still)! Might be a
little pain for people who are addicted to changing themes every few
Received on 2009-12-22