von Nasrullah Memon
Statistik und Sichtungsnachweis dieser Seite findet sich am Artikelende
| [1.] Nm/Fragment 186 03 - Diskussion Zuletzt bearbeitet: 2012-04-26 20:23:34 WiseWoman | Fragment, Gesichtet, Heer et al 2005, Nm, SMWFragment, Schutzlevel sysop, Verschleierung |
|
|
|
| Untersuchte Arbeit: Seite: 186, Zeilen: 3-32 |
Quelle: Heer et al 2005 Seite(n): 4, Zeilen: left column 24-38 - right column |
|---|---|
| To ensure performance, the ItemRegistry also recycles item instances when they are removed from the registry, avoiding object initialization costs that can cripple performance.
6.3.4 Actions Actions are basic components of application design in Prefuse. Actions are composable processing modules that update the VisualItems in an ItemRegistry. Actions are the mechanism for selecting visualized data and setting visual properties, performing tasks such as filtering, layout, colour assignment, and interpolation. To facilitate extensibility, Actions follow a simple API: a single run method that takes an ItemRegistry and an optional fraction indicating animation progress as input. In addition, base classes for specific Action types such as filters and layout algorithms are provided. While Actions can perform arbitrary processing tasks, most fall into one of three types: filter, assignment, and animator actions. Filter actions performs tasks like filtering as described in previous subsections. Assignment actions are used to set attributes of VisualItems, for example: its position or colour. A variety of layout management techniques are also coded as actions in Prefuse. Animator actions interpolate visual attributes between starting and ending values to achieve animation, using the animation fraction provided by the Action interface. Prefuse includes animators for locations, colours, fonts, and sizes. 6.3.5 ActionLists and Activities ActionLists are runnable routines which contain actions. A user may add as many Actions to ActionList as one wants. ActionList sequentially execute them as a sequential pipeline executing resources. These lists form processing pipelines that are invoked in response to user or system events. ActionLists are Actions themselves, allowing lists to be used as sub-routines of other lists [and recursion.] |
To ensure performance, the ItemRegistry also recycles item instances when they are removed from the registry, avoiding object initialization costs that can cripple performance.
Actions The basic components of application design in prefuse are Actions: composable processing modules that update the VisualItems in an ItemRegistry. Actions are the mechanism for selecting visualized data and setting visual properties, performing tasks such as filtering, layout, color assignment, and interpolation. To facilitate extensibility, Actions follow a simple API: a single run method that takes an ItemRegistry and an optional fraction indicating animation progress as input. In addition, base classes for specific Action types such as filters and layout algorithms are provided. While Actions can perform arbitrary processing tasks, most fall into one of three types: filter, assignment, and animator actions. Filter actions perform the filtering process discussed earlier, controlling what entities and relations are represented by VisualItems in the ItemRegistry [...] Assignment actions set visual attributes, such as location, color, font, and size, for VisualItems. prefuse includes extensible color, font, and size assignment functions and a host of layout techniques for positioning items. Finally, animator actions interpolate visual attributes between starting and ending values to achieve animation, using the animation fraction provided by the Action interface. prefuse includes animators for locations, colors, fonts, and sizes. ActionLists and Activities To perform data processing, Actions are composed into runnable ActionLists that sequentially execute these Actions. These lists form processing pipelines that are invoked in response to user or system events. ActionLists are Actions themselves, allowing lists to be used as sub-routines of other lists. |
Continuation from previous page. The second portion is marginally rewritten. |
|
Letzte Bearbeitung dieser Seite: durch Benutzer:WiseWoman, Zeitstempel: 20120426202423