Difference between revisions of "Pattern Library"
| Line 7: | Line 7: | ||
* '''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== | |||
The following description is underlying: | |||
'''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 vary and what is the variable part. | |||
Revision as of 18:57, 1 October 2007
This library is written for service manager and GUI developer 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 pattern are bound to the following preliminaries:
- 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[edit]
The following description is underlying:
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 vary and what is the variable part.
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)