>> 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 device.
>
> 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
> minutes though.

I also like that idea - how often do people really change themes?

Maybe with this there would be no reason to have the S/M/L/XL categories at
all, just work out the number of bytes required, compare to the number
allocated, and prompt for a reboot to change theme if needed?

pondlife
Received on 2009-12-22