[Cuis] Better Themes

[Juan Vuletich]

Phil (list) wrote:
> Juan,
>
> On May 19, 2012, at 5:01 PM, Juan Vuletich wrote:
>
>   
>> Hehehe. My current phone is http://www.gsmarena.com/nokia_5200-1717.php . It can not run anything at all! I'd get something newer. Perhaps a Motorola Defy+.
>>
>>     
>
> Ouch!  Well whatever device you go with next time it will definitely do more :-)  I'd generally advise techies to get a Nexus (whatever the current model is when it's time) as you're likely to appreciate the easy root and ROM options it offers and miss it if you go with something else (not to mention be stuck on older versions of Android like the Defy+ with 2.3 when 4.x is the current version)
>   

Nexus is not available here.. and if it was, It would be over $700 I 
guess. I need something cheaper!

>> Thanks for the links. This is a summary of what I understood:
>>
>> Android:
>> - Not zoomeable
>> - GUI is not specified in pixels but in physical units, not unlike inches or milimeters. This is already better than what most platforms do.
>> - Variation in display density (dpi) between devices is handled via bitmaps sets with multiple resolutions and / or automatic scaling.
>> - Variation in physical display size between devices (from 3" to 10", usually from 4" to 7") is handled like usual window resize on a PC (i.e. widget physical size does not change, but the amout of stuff that can be shown varies).
>>
>>     
>
> You got it.  The layout system is pretty interesting in that you design a screen in an app for a tablet but chop it up into functional sublayouts (i.e. fragments) that will still function and look good on a phone.  It also has an interesting menu design where you'll see more items on a larger dp device such as a tablet that can roll off into an overflow menu on a phone

Yes. Stealing that kind of ideas would be great.

>> Morphic 3:
>> - Zoomeable
>> - GUI is specified in whatever units the developer chooses. For example, inches or milimeters.
>> - Variation in display density between devices is handled automatically by the vector graphics engine. Rendering of vector graphics is always high quality.
>> - Variation in physical display size between devices can be handled like window resize on a PC. But in addition:
>> - The user can zoom de UI, enabling, for example:
>>   - Make room for more widgets or more content (widgets with smaller phisical size, whole GUI physical size doesn't change)
>>   - Enlarge widgets for easier view (whole GUI physical size doesn't change, less widgets or content is visible). This would be like emulating a smaller Android inside a bigger one (but without pixelated artifacts, always high quality rendering of vector graphics).
>>   - Enlarge widgets for easier view (whole GUI physical size grows, scrollbars are added if needed; amount of widgets or content visible doesn't change). This wouldn't be too unlike the display zoom option on Mac OS-X, but with high qualit rendering, like, for example, zooming a properly built PDF file.
>>
>>     
>
> Cool... I didn't realize all that was in scope for Morphic 3.  Carry on, sir! :-)
>   

:)

> Thanks,
> Phil
>   

Cheers,
Juan Vuletich