<
From version < 21.1 >
edited by Alexander Schulz-Rosengarten
on 2023/07/11 10:33
To version < 22.1
edited by Richard Kreissig
on 2023/09/14 10:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -Kieler.Discontinued Projects.WebHome
1 +KIELER.Discontinued Projects.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.als
1 +XWiki.stu230980
Content
... ... @@ -2,7 +2,7 @@
2 2  This project moved to [[its own GitHub repository>>url:https://github.com/kieler/ptbrowser||shape="rect"]].
3 3  {{/warning}}
4 4  
5 -{{panel title="Project Information"}}
5 +== Project Information ==
6 6  Responsible:
7 7  
8 8  * [[Christoph Daniel Schulze>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/christoph-daniel-schulze/||shape="rect"]]
... ... @@ -11,11 +11,10 @@
11 11  
12 12  * [[Standalone Ptolemy Viewer Based on KLighD>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/videos/ptolemyViewer/PtolemyViewerHQ.html||shape="rect"]]
13 13  * [[Navigating and Customizing Views with KLighD>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/videos/klighd-ptolemy/||shape="rect"]]
14 -{{/panel}}
15 15  
15 +
16 16  [[doc:KIELER.Development.Downloads Subpages.Downloads - KIELER Ptolemy Browser.WebHome]]
17 17  
18 -{{excerpt-include/}}
19 19  
20 20  A complex example for using KLighD technology, the Ptolemy Visualization project is about generating transient views of Ptolemy II models that are easy to browse through. [[Ptolemy II>>url:http://ptolemy.eecs.berkeley.edu/ptolemyII/index.htm||shape="rect"]] is an open source program developed at UC Berkeley for experimenting with actor-oriented modelling. Actors are graphical representations of components with a certain functionality that generate outputs as a function of the inputs they receive. To use the output of one actor as the input of another, actors are connected by links. A typical Ptolemy model might for instance look like this:
21 21  
... ... @@ -23,11 +23,11 @@
23 23  
24 24  In some respect, Ptolemy models are a typical example of graphical modelling languages:
25 25  
26 -* (% style="line-height: 1.4285715;" %)Actors are represented as boxes, with edges connecting the actors to each other. The edges are routed orthogonally: each edge segment is aligned either horizontally or vertically.
25 +* (% style="line-height:1.4285715" %)Actors are represented as boxes, with edges connecting the actors to each other. The edges are routed orthogonally: each edge segment is aligned either horizontally or vertically.
27 27  * Actors can have more than one input, and more than one output. To be able to distinguish the data coming in and going out, inputs and outputs are routed to dedicated connection points, called ports. Thus, links never connect two actors directly, but rather connect them through their ports.
28 28  * Actors can contain further models that define their functionality (we call such actors //hierarchical actors//). To be able to see the model inside an actor, Ptolemy provides the possibility to look inside the actor. This effectively opens a new Ptolemy window displaying the actor's implementation.
29 29  
30 -(% style="line-height: 1.4285715;" %)However, Ptolemy models have some features that are not that common:
29 +(% style="line-height:1.4285715" %)However, Ptolemy models have some features that are not that common:
31 31  
32 32  * Ports are not restricted to be either input ports or output ports: they can be both. As a consequence, links are undirected and can transport data in both directions.
33 33  * Models have a director that defines the model of computation used to execute the model. In fact, if an actor in turn has another model inside it, that model, too, has a director. One of the research goals of the Ptolemy project is to find out how different models of computation can be composed.
... ... @@ -41,7 +41,7 @@
41 41  
42 42  [[image:attach:kieler.png]]
43 43  
44 -{{tip title="Try This"}}
43 +{{info title="Try This"}}
45 45  Open and browse a Ptolemy model:
46 46  
47 47  1. Start Eclipse with the //KIELER Ptolemy Viewer// feature installed.
... ... @@ -49,7 +49,7 @@
49 49  **
50 50  1. Open the model by double-clicking it in Eclipse. If that doesn't show a graphical view of the model, right-click the file, click //Open With -> Other...// and select //Ptolemy Model Viewer// from the dialog that pops up.
51 51  1. Open and close some of the hierarchical actors by double-clicking them.
52 -{{/tip}}
51 +{{/info}}
53 53  
54 54  We have also added further features that may be helpful when browsing models:
55 55  
... ... @@ -105,4 +105,3 @@
105 105  
106 106  Only one detail deserves some more explanation: how we get our hands at how entities are rendered in Ptolemy. This is done through a mechanism similar to what we already used in the first stage: we simply instantiate the entities using our Ptolemy library, ask Ptolemy to render them, and convert the rendering information into something KLighD supports. This can either be SVG code (if the rendering was originally specified as an SVG image) or a bitmap image. If an actor cannot be instantiated, we have no rendering information and display the actor as a simple rectangle with a black border and white background.
107 107  
108 -\\