11.3. RFRS ConsiderationsThe "User Interface" section of the RFRS Requirements includes five itemsfour requirements and one best practicedealing with wizards. Most of them are derived from the Eclipse UI Guidelines. 11.3.1. Wizard look and feel (RFRS 3.5.2)User Interface Guideline #5.2 is a requirement that states:
Show that your wizards conform to the standard wizard look and feel. Make sure that they contain the proper buttons in the correct order as well as an appropriate banner graphic. 11.3.2. Open new file in editor (RFRS 3.5.6)User Interface Guideline #5.9 is a requirement that states:
If your wizard creates a file, show that it automatically opens in an editor when the wizard is finished. For the Extract Strings wizard, you would show that the plugin.properties file is opened after the wizard creates it. 11.3.3. New project switches perspective (RFRS 3.5.7)User Interface Guideline #5.10 is a requirement that states: If a new project is created, change the active perspective to suit the project type. If your plug-in provides a new project wizard and an associated perspective, show that the system automatically switches to your perspective when your wizard is used to create a new project. 11.3.4. Show new object (RFRS 3.5.8)User Interface Guideline #5.11 is a requirement that states:
If your wizard creates a file, show that it is automatically selected in the appropriate view. For the Extract Strings wizard, you would show that the plugin.properties file is selected in the Navigator view after the wizard creates it. 11.3.5. One-page wizard buttons (RFRS 5.3.5.13)Best practice #1 states:
If your plug-in contains any one-page wizards, show that it contains the appropriate buttons in the correct state. |