| Summary: | [Controls Demo] Provide a style contributions for "special-red" and "special-blue" variants | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ivan Furnadjiev <ivan> | ||||
| Component: | Demo | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | nmussin, tbuschto | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 M6 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 362166 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Ivan Furnadjiev
This bug is blocked by 362166. By using variants, the widgets cannot be fully re-styled as subwidgets still use the default theme. One could only try to define a variant that somehow matches the default look and feel (for example, it's not possible to create a dark combobox, because Combo-Button will remain default-styled). My idea was to extract and improve the "special-red" and "special-blue" related definitions from the old "tea" theme (org.eclipse.rap.demo\theme1\theme.css) and set them as a theme contribution to the default theme. Here is the segment from the "tea" theme:
/* Custom variants */
.special-red {
color: red;
background-color: #ffaaaa;
}
.special-red:disabled {
color: white;
}
.special-blue {
color: blue;
background-color: #aaaaff;
}
.special-blue:disabled {
color: white;
}
Shell.special-red {
border: 3px solid red;
padding: 10px;
}
Shell.special-blue {
border: 3px solid blue;
padding: 10px;
}
Link-Hyperlink.special-red {
color: #ffaaaa;
}
Link-Hyperlink.special-blue {
color: #aaaaff;
}
Button[PUSH].special-red, Button[TOGGLE].special-red {
border: 2px solid red;
}
all right, I will use the custom variants from "tea" theme and just adjust the colors a bit. Created attachment 210302 [details]
adds theme contribution to default theme with properties for custom variants 'special-red' and 'special-blue'
Applied patch to CVS HEAD. |