Revision history [back]

I think i can expect that any application that builds for the target architecture will work...

But does hardware adaptation include tweaks to, e.g. the Silica.Theme constants?

When new hardware arrives, which should be soon, applications will have to adapt to different screen resolution.

How is theming going to change to allow different screen sizes and DPI?

For example, for a 4.5" screen with a higher DPI I would probably want the theme to report larger pixel sizes for fonts and maybe icons.

On a tablet, with larger screen but higher resolution, we would probably want most measurement to stay the same, but maybe have larger Theme.fontSizeLarge.

On a small screen device, with a low DPI, sizes should be tweaked as well, but what would be the best compromise I cannot tell without trying, you need to have buttons and widgets big enough that activating them by touch is reliable.

It would be useful to know what is the expected behavior, and best practices we can put in place to be sure our applications will still work on a variety of display -- and maybe, having a tool to test various configurations.

The SDK could have different simulators with e.g a 480x800 screen, and a 1280x800 screen, to let us try the interface on a small device and a tablet, for example.

I think i can expect that any application that builds for the target architecture will work...

But does hardware adaptation include tweaks to, e.g. the Silica.Theme constants?

When new hardware arrives, which should be soon, applications will have to adapt to different screen resolution.

How is theming going to change to allow different screen sizes and DPI?

For example, for a 4.5" screen with a higher DPI I would probably want the theme to report larger pixel sizes for fonts and maybe icons.

On a tablet, with larger screen but higher resolution, we would probably want most measurement to stay the same, but maybe have larger Theme.fontSizeLarge.

On a small screen device, with a low DPI, sizes should be tweaked as well, but what would be the best compromise I cannot tell without trying, you need to have buttons and widgets big enough that activating them by touch is reliable.

It would be useful to know what is the expected behavior, and best practices we can put in place to be sure our applications will still work on a variety of display -- and maybe, having a tool to test various configurations.

The SDK could have different simulators with e.g a 480x800 screen, and a 1280x800 screen, to let us try the interface on a small device and a tablet, for example.

I think i can expect that any application that builds for the target architecture will work...

But does hardware adaptation include tweaks to, e.g. the Silica.Theme constants?

When new hardware arrives, which should be soon, applications will have to adapt to different screen resolution.

How is theming going to change to allow different screen sizes and DPI?

For example, for a 4.5" screen with a higher DPI I would probably want the theme to report larger pixel sizes for fonts and maybe icons.

On a tablet, with larger screen but higher resolution, we would probably want most measurement to stay the same, but maybe have larger Theme.fontSizeLarge.

On a small screen device, with a low DPI, sizes should be tweaked as well, but what would be the best compromise I cannot tell without trying, you need to have buttons and widgets big enough that activating them by touch is reliable.

It would be useful to know what is the expected behavior, and best practices we can put in place to be sure our applications will still work on a variety of display -- and maybe, having a tool to test various configurations.

The SDK could have different simulators with e.g a 480x800 screen, and a 1280x800 screen, to let us try the interface on a small device and a tablet, for example.