The Eclipse platform provides a web user interface, also known as Flat Look, design alternative for implementing content editors. For example, the editor in the Eclipse plug-in development environment (PDE) perspective uses Flat Look.
The Flat Look design may be more suitable for certain type of user tasks, and more appealing to certain user profile.
However, this design should not be used just because it provides a different look than the native platform look and feel.
The use of Flat Look design should be considered in the context of the supported user scenarios.
This design is usually a good fit for extensive property and configuration editing,
such as editing Eclipse’s plugin.xml file, and J2EE Web application’s deployment descriptors.
|
Tip
|
Guideline 16.1 Use Flat Look design for user scenarios that involve extensive property and configuration editing. |
When required, use a btn:[More…] button for navigation purpose (function similar to a hyperlink).
On the overview page, initially expand basic or core sections, but collapse advanced sections.
Don’t use tabs within a Flat Look editor tab. Use an alternative design or rendering of the tabs.
When applicable, always provide a "Source" tab. Assign mnemonics for sections, controls, etc. for keyboard navigation.
Plug-ins that use Flat Look design for content editor should provide support for full two way interactions between the editor and outline view.
In the outline view, use grouping elements corresponding to tabs in the content editor for the organization of the tree view.
