[TIMOB-7237] MobileWeb: Theme support for UI widgets
| GitHub Issue | n/a |
|---|---|
| Type | Sub-task |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Fix |
| Resolution Date | 2017-06-29T18:44:53.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | MobileWeb |
| Labels | themeable |
| Reporter | Chris Barber |
| Assignee | Chris Barber |
| Created | 2012-01-16T16:15:10.000+0000 |
| Updated | 2018-04-04T23:20:36.000+0000 |
Description
There are a number of UI widgets that have no native UI and that need some sort of styling. We should have a theme system that allows us to control these UIs.
Themes would follow a common interface, then define specific visual looks and behaviors.
There would be at least one theme, Appcelerator, and we can consider adding platform specific themes (e.g. iOS, WP7, etc).
Each UI widget would not only apply certain CSS classes, but would also read the theme's configuration for specific behavior hints, such as tabs on the top or bottom.
The tiapp.xml would allow the developer to select which theme they wanted to use. The build system would then optimize the project for that theme.
It should also be possible to dynamically serve a specific theme per request based on the type of device connecting.
We will want to use SASS or LESS (https://gist.github.com/674726). May also need to use clean-css (https://github.com/GoalSmashers/clean-css).
We would prefer LESS since it is JavaScript based
@Sehyo We will almost certainly use LESS. :)
I would recommend doing this in Alloy and using tss. Is there a reason not to?
@Russell, the point of the theme support is to implement the default look. Because Mobile Web is extremely performance sensitive, I believe a native CSS approach will be more efficient. This theme system is not intended for end developers to use. It's solely for the default look.
Resolving ticket as "Won't fix" as MobileWeb has been deprecated.
Closing as will not fix.