Ui specification 3 of eclipse

Language

Guideline 1.7

Create localized version of the resources within your plug-in.

Error Handling

Guideline 1.8

When an error occurs which requires either
Explicit user input or immediate attention from users, communicate
Occurrence with a modal dialog.

Guideline 1.9

If a programming error occurs in the product, communicate the occurrence with a dialog, and log it.
When an internalProgramError. Use the dialog box to interact with the event and make a history record.

Visual Design
Visual Design
Consistency
Consistency
Guideline 2.1

Re-use the core visual concepts to maintain consistent representation and meaning implements SS Eclipse plug-ins.
Use the core visualization concepts to maintain a unified expression, and implement it through Eclipse plug-ins.

Icon palettes
Icon version
Guideline 2.2

Use the eclipse 256 color palette for creating the active or selected state of all icon types.
Use the eclipse 256 activation board to create an activation/selected icon.
Guideline 2.3

Use the eclipse 8 color palette for creating
Enabled state of perspective, view, toolbar, toolbar wizard, and local
Toolbar icons.
You can use the eclipse 8 Development Board to create the perspective, view, toolbar, toolbar wizard, and toolbar icons.

Guideline 2.4

Use the eclipse 2 color palette for creating
Disabled state of toolbar, toolbar wizard, and local toolbar icons.
Use the eclipse 2 Development Board to create unavailable toolbar, toolbar wizard, and local toolbar icons

Icon types
Icon type
Guideline 2.5

Use the appropriate icon type in the location it is designed for within the user interface.
Icon Localization

Icon size & Placement

Guideline 2.6

Follow the specific size specifications for each type of icon.

Guideline 2.7

Cut the icons with the specific placement shown to ensure alignment in the user interface.

Icon Positioning

Guideline 2.8

Follow the positioning guidelines for the different
Types of icons for optimal alignment of these elements relative to one
Another.

Icon Positioning

Guideline 2.9

Use the eclipse special blue 183 color palette for creating wizard graphics.

Wizard size & Placement

Guideline 2.10

Follow the specific size specifications for wizard graphics.

Guideline 2.11

Cut the wizard graphics with the specific placement shown to ensure alignment in the Wizard banner area.

Implementation conventions
Implementation Specification
Guideline 2.12

Follow the predefined directory structure and naming convention.
Follow the directory structure and naming rules

Guideline 2.13

Keep the original directory names provided.
Provide sub-scripts for keeping the original directory name

Guideline 2.14

Minimize duplication of graphics within a plugin
Keeping all graphics in one, or few, first level user interface
Directories.
Minimize image duplication. In the same plug-in, make sure that all images are in the same position or a few places,

Guideline 2.15

Use the active, enabled, and disabled States provided.
Activate, use, and disable Ram users.
Guideline 2.16

Abbreviate file name instead of using the full icon name, e.g. New interface becomes "newint ".
Abbreviated file name

Guideline 2.17

Use lower case characters in your file names, e.g. DTD becomes "DTD ".
Lowercase file name
Guideline 2.18

Use 10 characters or less in your file names if possible (underscores count as a character ).
The file name should be less than 10 Characters
Guideline 2.19

Use a file name suffix that describes its location or function in the tool, e.g. newint_wiz.
Use the file suffix to indicate his/her
Guideline 2.20

Use transparent *. GIF format for all user interface
Icons and Wizard graphics, unless the context requires a different file
Format.
Use transparent GIF format

Guideline 2.21

Keep the original file names provided.
Keep original file name

Component development
Control Development
Commands
Command
Guideline 3.1

Each Command must have a label, tool tip, and full
Color image. The label and tool tip must use headline Style
Capitalization.
Each Command must have a label, tooltip, and full-color image. Label. The tooltip is in upper case.
Guideline 3.2

The command tooltip shocould describe the result
The command, not the current state of the command. Use the text same
That for the command label.
The tooltip of a command must describe the execution result rather than the current command status. The same applies to command label.
Guideline 3.3

Adopt the labeling terminology of the workbench for new, delete and add commands.
Use the workbench label term (new, delete and add ).
Guideline 3.4

An command shoshould only be enabled if it can be completed successfully.
The command can be set to enabled only when the command can be successfully executed.
Guideline 3.5

Command enablement shocould be quick. If command
Enablement cannot be quick, enable the command optimistically and
Display an appropriate message if the command is invoked, but cannot be
Completed.
You need to quickly reflect the executable status of the command. If the command execution status cannot be quickly reflected, an appropriate message must be displayed to indicate whether the command is executed but not complete.
Dialogs
Dialog Box
Guideline 4.1

When a dialog opens, set the initial focus to
First input control in the container. If there are no input controls,
The initial focus shoshould be assigned to the default button.
When the dialog box opens, the initialization focus is directed to the first input control in the container. If no control is input, the initialization focus is positioned to the default button.

Guideline 4.2

Slush bucket widget (or twin box) shold flow from
Left to right with the source objects on the left hand side. It shold
Have the >,<, >>,< control buttons in this order.

Wizards

Guideline 5.1

Use a wizard for any task consisting of specified steps, which must be completed in a specific order.

Guideline 5.2

Each wizard must contain a header with a banner
Graphic and a text area for user feedback. It must also contain
Back, next, finish, and cancel buttons in the footer.

Guideline 5.3

Start the wizard with a prompt, not an error message.
In wizard, the user is prompted rather than using an error message.
Guideline 5.4

Seed the fields within the wizard using the current workbench state.

Guideline 5.5

Validate the wizard data in tab order. Display
A prompt when information is absent, and an error when information is
Invalid.
Perform data verification in the Wizard. If the input information is incomplete, a prompt is displayed.
Guideline 5.6

Only enable the next/finish buttons if all required information in the dialog is present and valid.

Guideline 5.7

Remove all programming Message ID's from Wizard text.

Guideline 5.8

Use a browse button whenever an existing object is referenced in a wizard.

Guideline 5.9

If a new file is created, open the file in
Editor. If a group of files are created, open the most important,
Or central file in an editor. Open the readme.html file upon creation
Of an example project.

Guideline 5.10

If a new project is created, prompt users and change the active perspective to suit the project type.

Guideline 5.11

If a new object is created, select and reveal the new object in the appropriate view.
When a new object is created, it is selected and displayed in the appropriate view.
Guideline 5.12

Create folder objects in a wizard if reasonable defaults can be defined.

Guideline 5.13

Use the term "project name" for the input field
Label when the item must be a project; otherwise, use the term "folder
Name ". Do not qualify the term.