Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "E4/CSS/Visual Design"
(→Visual Design Items) |
|||
Line 39: | Line 39: | ||
* April | * April | ||
** stabilize design | ** stabilize design | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Visual Design Items == | == Visual Design Items == | ||
Line 109: | Line 102: | ||
| Medium | | Medium | ||
| [[Image:Progress.gif]] Susan to push on default workbench model for SDK and use of perspectives. | | [[Image:Progress.gif]] Susan to push on default workbench model for SDK and use of perspectives. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| Workbench background | | Workbench background | ||
Line 145: | Line 132: | ||
| ? | | ? | ||
| [[Image:Question.gif]] | | [[Image:Question.gif]] | ||
− | |-} | + | |- |
+ | |- | ||
+ | | UI Forms | ||
+ | | Are there additional requirements for styling ui forms components? | ||
+ | | Apps desiring styling control over forms should be encouraged to use web UI technology to achieve this. There will be no more effort applied to styling ui forms. | ||
+ | | Low | ||
+ | | [[Image:Ok_green.gif]] No work to be done | ||
+ | |} |
Revision as of 12:23, 20 October 2009
This page summarizes the investigations into an updated visual design (default stylesheet) for the e4 workbench.
Goals
The goals of this work are:
- design a compelling visual style for e4
- reduce visual noise, focus on the data
- investigate additional breathing space, lessons learned from publishing and web
- sleek/modern
- drive the ability/flexibility of the CSS styling for SWT widgets
- demonstrate the ability to keep a "classic" look and supply alternate designs
- identify the major interaction design issues (workbench model) that might block visual design
Timetable/approach
- October
- Investigate/define implementation constraints
- Bogdan - explore tab shape definition, border control, Windows 7 implications (if any)
- Prioritize visual design areas
- Susan - work within e4 plat UI team to prioritize focus areas for design exploration
- Investigate/define implementation constraints
- November
- Visual design explorations
- Linda - multiple design explorations with limited constraints
- Susan - solicit team response/consensus on alternatives
- Choose a direction by end of November
- Interaction design explorations
- Susan/Eric - work within e4 team to develop default workbench assumptions wrt perspectives, activity-based layouts, role of the editor area
- Visual design explorations
- Dec/Jan/Feb
- Visual design
- Linda/Susan/Bogdan - Iterate (push/pull) on default design
- Susan - project team consensus, communicate to community
- Susan/Bogdan - investigate programmatic reduction of clutter (fades, decorator removal, etc.)
- Bogdan - implementation/evolution of CSS/SWT styling engine, CTabFolder, etc.
- Interaction design
- Eric/Susan (?) - implementation
- Visual design
- March
- EclipseCon goals
- Show the new design
- Show a "classic" stylesheet based on 3.x
- Show radical alternatives to demonstrate CSS flexibility
- EclipseCon goals
- April
- stabilize design