High Level Requirement Specification

Modification to the Gui.

Overview

There is general consensus that the current Gui design of Taverna lacks uniformity and compliance to Gui standards. This requirement is to 'tidy up' the Gui and make it comply to the Java Look and Feel standards better.

From the JLAF Book - "As the Java platform has matured, designers and developers have recognized the need for consistent, compatible, and easy-to-use Java applications. The Java look and feel meets that need by providing a distinctive platform-independent appearance and standard behavior ...

...The Java look and feel is the default interface for applications built with the JFC. The Java look and feel is designed for cross-platform use and can provide:

• Consistency in the appearance and behavior of common design elements
• Compatibility with industry-standard components and interaction styles
• Aesthetic appeal that does not distract from application content

Three distinctive visual elements are the hallmarks of the Java look and feel components: the flush 3D style, the drag texture, and the color model. "

Overall Goals

A Gui that looks better and is easier and more intuitive to use, and that conforms to the Java Look and Feel standards. In Taverna 1.3 the GUI refactoring should be combined with further seperation between the GUI and the underlying architecture where doing so won't risk the stability of the code base.

Affected Components

All components that incorporate a Gui.

Key Tasks

• Define the standards for the GUI, based upon the Java Look and Feel standards.
• Commission the production of images for icons, buttons, splashscreen etc. (ClearCrystal^?)
• (Taverna 1.3) Refactor UI, replacing images and improving seperation between the UI and the business logic behind it.
• Save user preferences for window positions/sizes
• ? A button to rerun workflow with the same input data as last time?
• ? Workflow templates - ability to sktech out workflow with placeholder processes not bound to a real service which can then be fleshed out by the user later?
• ? Ability to refactor workflows? e.g. to say "change all instances of this service provider to this version instead?

Appendix

Java Look and Feel Guidelines