von Nasrullah Memon
Statistik und Sichtungsnachweis dieser Seite findet sich am Artikelende
| [1.] Nm/Fragment 185 01 - Diskussion Zuletzt bearbeitet: 2012-04-25 22:43:33 WiseWoman | Fragment, Gesichtet, Heer et al 2005, Nm, SMWFragment, Schutzlevel sysop, Verschleierung |
|
|
|
| Untersuchte Arbeit: Seite: 185, Zeilen: 1-27 |
Quelle: Heer et al 2005 Seite(n): 3-4 (internet version), Zeilen: p. 3, right column 42-53 - p. 4 left column 1-16 |
|---|---|
| [Individual filters are provided in] Prefuse as Action modules, discussed later in this section.
In the data state model of (Chi, E.H., 2000), filtering is made up of the Visualization Transformation: reducing abstract data to visualizable content. Filtering can also be understood as implementing a tiered version of the model-view-controller pattern (Krasner, G.E. and S.T. Pope, 1988). Abstract data provides a base model for any number of visualizations, while filtered data constitutes a visualization-specific model with its own set of view controllers. This enables multiple visualizations of a shared data set by using separate filters, and different views of a specific visualization by reusing the same filtered items, while isolating filtering logic away from the main application logic 6.3.3 Managing Visual Items: The ItemRegistry Prefuse provides three types of VisualItem by default: NodeItems to visualize individual entities, EdgeItems to visualize relations between entities, and AggregateItems to visualize aggregated groups of entities. These items are arranged in a graph structure separate from the source data, maintaining a local version of the data topology and thereby enabling flexible representations of visualized content. If desired, additional VisualItem types can also be introduced. VisualItems are recorded centrally in “ItemRegistry”. ItemRegisrty [sic!] data structure contains the overall state for a specific visualization. Filter Actions request visual analogues from the registry, which returns the VisualItems, creating them as needed. ItemRegistry can be viewed as a mapping between the abstract data and VisualItems. The ItemRegistry also contains a FocusManager. |
[p. 3]
Individual filters are provided in prefuse as Action modules, discussed later in this section. In the data state model of [EN 15], filtering constitutes the Visualization Transformation: reducing abstract data to visualizable content. Filtering can also be understood as implementing a tiered version of the model-view-controller pattern [EN 29]. Abstract data provides a base model for any number of visualizations, while filtered data constitutes a visualization-specific model with its own set of viewcontrollers. This enables multiple visualizations of a shared data set by using separate filters, and different views of a specific visualization by reusing the same filtered items. [p. 4] Managing Visual Items: The ItemRegistry prefuse provides three types of VisualItem by default: NodeItems to visualize individual entities, EdgeItems to visualize relations between entities, and AggregateItems to visualize aggregated groups of entities. These items are arranged in a graph structure separate from the source data, maintaining a local version of the data topology and thereby enabling flexible representations of visualized content. If desired, additional VisualItem types can also be introduced. VisualItems are created and stored in a centralized data structure called the ItemRegistry, which houses all the state for a specific visualization. Filter Actions request visual analogues from the registry, which returns the VisualItems, creating them as needed, and records the mapping between the abstract data and visualized content. The ItemRegistry also contains a FocusManager, [...] --- [EN 15] Chi, E.H. A Taxonomy of Visualization Techniques Using the Data State Reference Model. InfoVis '00. pp. 69-75 2000. [EN 29] Krasner, G.E. and S.T. Pope, A Description of the Model-View-Controller User Interface Paradigm in the Smalltalk-80 System. Journal of Object-Oriented Programming, 1988. 1(3): p. 26-49. |
Continuation from previous page. A typo is to be found, where the text is not taken identically from the source. Interesting: a corresponding phrase in both texts (Visualization Transformation) is in italics. |
|
Letzte Bearbeitung dieser Seite: durch Benutzer:WiseWoman, Zeitstempel: 20120425224435