Difference between revisions of "Pattern Library"
| Line 1: | Line 1: | ||
This library is written for service | This library is written for service managers and GUI developers to support them in building graphical interfaces; especially to save time investigating web interfaces and their numerous implementations. The Library is also written to point out usability issues on a detailed level at an early stage. | ||
Building web applications that serve scientific needs have specific demands on graphical user interfaces. Such interfaces are not limited to common interface techniques used in commercial applications. The pattern library aims at providing development activities with a growing set of interface elements called patterns. These | Building web applications that serve scientific needs have specific demands on graphical user interfaces. Such interfaces are not limited to common interface techniques used in commercial applications. The pattern library aims at providing development activities with a growing set of interface elements called patterns. These patterns are | ||
* '''documented concerning the scenario they aim for''' | * '''documented concerning the scenario they aim for,''' | ||
* '''described how they work and what components are applied''' | * '''described how they work and what components are applied,''' | ||
* '''considered what varieties can evolve''' | * '''considered what varieties can evolve,''' | ||
* '''discussed in terms of usability pros and cons''' | * '''discussed in terms of usability pros and cons.''' | ||
'''Terminology''' | '''Terminology''' | ||
Each description follows the structural template explained below. | |||
'''Which Scenario fits?''' | '''Which Scenario fits?''' | ||
| Line 26: | Line 26: | ||
'''Varieties''' | '''Varieties''' | ||
In case the pattern appears in many different forms that can be classified. This section shows how the pattern | In case the pattern appears in many different forms that can be classified. This section shows how the pattern varies and which part is variable. | ||
Revision as of 11:38, 12 October 2007
This library is written for service managers and GUI developers to support them in building graphical interfaces; especially to save time investigating web interfaces and their numerous implementations. The Library is also written to point out usability issues on a detailed level at an early stage.
Building web applications that serve scientific needs have specific demands on graphical user interfaces. Such interfaces are not limited to common interface techniques used in commercial applications. The pattern library aims at providing development activities with a growing set of interface elements called patterns. These patterns are
- documented concerning the scenario they aim for,
- described how they work and what components are applied,
- considered what varieties can evolve,
- discussed in terms of usability pros and cons.
Terminology
Each description follows the structural template explained below.
Which Scenario fits?
Gives information how the pattern deals with a specific problem (Information architecture)
How does it work?
Gives a general description how the pattern is operated by users.
Pros and cons
Many patterns are already tested and evaluated so far. If so their drawbacks and advantages are listed here.
Varieties
In case the pattern appears in many different forms that can be classified. This section shows how the pattern varies and which part is variable.
The Vocabulary: Pattern Components[edit]
Patterns for Web Applications[edit]
- Organizing Layout and Display (Draft)
- User Input (Not started ...)
- Navigating Functionality (Not started ...)
- Browsing Data (Not started ...)
- Display Data (Draft)