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"
Line 12: | Line 12: | ||
== Timetable/approach == | == Timetable/approach == | ||
− | |||
{| border="1" cellpadding="2" width="100%" | {| border="1" cellpadding="2" width="100%" | ||
!width="20%"|October 2009 | !width="20%"|October 2009 | ||
Line 24: | Line 23: | ||
* Prioritize visual design areas | * Prioritize visual design areas | ||
** Susan - work within e4 plat UI team to prioritize focus areas for design exploration | ** Susan - work within e4 plat UI team to prioritize focus areas for design exploration | ||
− | |||
|* Visual design explorations | |* Visual design explorations | ||
** Linda - multiple design explorations with limited constraints | ** Linda - multiple design explorations with limited constraints | ||
Line 31: | Line 29: | ||
* Interaction design explorations | * Interaction design explorations | ||
** Susan/Eric - work within e4 team to develop default workbench model [https://bugs.eclipse.org/bugs/show_bug.cgi?id=292789 Bug 292789] | ** Susan/Eric - work within e4 team to develop default workbench model [https://bugs.eclipse.org/bugs/show_bug.cgi?id=292789 Bug 292789] | ||
− | | | + | |* Linda/Susan/Bogdan - Iterate (push/pull) on default design |
− | * Linda/Susan/Bogdan - Iterate (push/pull) on default design | + | |
* Susan - project team consensus, communicate to community | * Susan - project team consensus, communicate to community | ||
* Susan/Bogdan - investigate programmatic reduction of clutter (fades, decorator removal, etc.) | * Susan/Bogdan - investigate programmatic reduction of clutter (fades, decorator removal, etc.) | ||
* Bogdan - implementation/evolution of CSS/SWT styling engine, CTabFolder, etc. | * Bogdan - implementation/evolution of CSS/SWT styling engine, CTabFolder, etc. | ||
* Eric/Susan (?) - working toward default workbench model and other interaction design issues | * Eric/Susan (?) - working toward default workbench model and other interaction design issues | ||
− | |||
|* EclipseCon goals | |* EclipseCon goals | ||
** Show the new design | ** Show the new design | ||
** Show a "classic" stylesheet based on 3.x | ** Show a "classic" stylesheet based on 3.x | ||
** Show radical alternatives to demonstrate CSS flexibility | ** Show radical alternatives to demonstrate CSS flexibility | ||
− | | | + | | stabilize design |
− | + | ||
== Visual Design Items == | == Visual Design Items == |
Revision as of 14:25, 27 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 2009 | Nov/Dec 2009 | Jan/Feb 2010 | March 2010 | April 2010 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
* Investigate/define implementation constraints
|
* Visual design explorations
|
* Linda/Susan/Bogdan - Iterate (push/pull) on default design
|
* EclipseCon goals
|
stabilize design
Visual Design ItemsThe following table tracks visual design elements that are being considered and any constraints that the implementation imposes on the design. Note that the priority listed in the table is related to its impact on the overall visual design. High priority items must have their constraints defined first, while lower priority items can be defined later in the design process without affecting the overall design approach.
|