Currently we have the Ambience QML theme and a similar Ambiance HTML5 theme for local HTML5 applications. We don't have a mechanism for changing the theme and having those changes respected across the range of apps that the device can have. We don't have any mechanism for remote web applications to reference the current device theme. For accessibility or aesthetic reasons a user might choose a different base font size, different primary and accent colours etc. If all the apps use a local copy of the ambience theme then they are going to be inconsistent. It should be possible for the core phone to expose it's current theme for apps to use. If we can serve up the theme in a context that can be shared to remote web applications then we have an opportunity for a much more consistent visual experience than other platforms can achieve.

Workshop session: Scopes keywords & departments

Convergence Tooltips Key navigation - Tab/Shift+Tab Date and Time Pickers Menus Application and context menus

Q&A Session for developers or prospective developers to get their questions answered about scopes.

Tasks for implementing features and fixes through the 15.10 release, including finishing the "reboot" series initial release

Tasks for implementing features and fixes through the 15.10 release

15.10 - 1.3 release The upcoming cycle the focus is on convergence. Complete and as fast toolkit for other form factors and for devices with other capabilities. The emphasis here is on capability. Not only form factor or device mode. The next release (1.3) of the UITK will adopt to the host environment according to its capabilities. Like input capabilities, size and others.

The focus of this session is to collect questions and ideas from the application developers. We will cover both UITK and tools.

talk about using jasmine and autopilot; helpers that exist, and how to test your webapp