Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • kieler.png
  • ptolemy.png
  • synthesis.png
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Discontinued Projects

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.uru
	1	+XWiki.cds

Content

...	...	@@ -1,3 +1,7 @@
	1	+{{warning title="Moved to GitHub"}}
	2	+This project moved to [[its own GitHub repository>>url:https://github.com/kieler/ptbrowser||shape="rect"]].
	3	+{{/warning}}
	4	+
1	1	{{panel title="Project Information"}}
2	2	Responsible:
3	3
...	...	@@ -101,4 +101,4 @@
101	101
102	102	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.
103	103
104		-
	108	+\\

kieler.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.XWikiGuest

Size

...	...	@@ -1,0 +1,1 @@
	1	+178.6 KB

Content

ptolemy.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.XWikiGuest

Size

...	...	@@ -1,0 +1,1 @@
	1	+163.7 KB

Content

synthesis.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.XWikiGuest

Size

...	...	@@ -1,0 +1,1 @@
	1	+4.9 KB

Content

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-57802848
	1	+7700687

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/57802848/Ptolemy Browser
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7700687/Ptolemy Browser