Org.simantics.scenegraph - Revision history

Tuukka Lehtonen: /* Scenarios */

2011-10-13T22:52:16Z

Scenarios

← Older revision		Revision as of 22:52, 13 October 2011
Line 281:		Line 281:

	== Scenarios ==		== Scenarios ==

			* [[Scene Graph: Sysdyn-scenario]]

	=== Implementing a 2D node ===		=== Implementing a 2D node ===

Tuukka Lehtonen: /* Mouse capture/grabbing */

2011-10-13T22:52:08Z

Mouse capture/grabbing

← Older revision		Revision as of 22:52, 13 October 2011
Line 314:		Line 314:
	=== Mouse capture/grabbing ===		=== Mouse capture/grabbing ===
	* TODO: mouse capture		* TODO: mouse capture

	* [[Scene Graph: Sysdyn-scenario]]

	== Links ==		== Links ==

Tuukka Lehtonen: /* Scenarios */

2011-10-13T22:47:56Z

Scenarios

@@ Line 282: / Line 282: @@
 == Scenarios ==
-* TODO: implementing your own G2DNode, what render needs to do
+=== Implementing a 2D node ===
-* TODO: hooking nodes to UI events
+* TODO: implementing your own G2DNode
 * TODO: picking
 * TODO: global <-> local coordinate system transformations
 * TODO: mouse capture

Tuukka Lehtonen: /* org.simantics.scenegraph features */

2011-10-13T12:08:31Z

org.simantics.scenegraph features

← Older revision		Revision as of 12:08, 13 October 2011
Line 159:		Line 159:
	== org.simantics.scenegraph features ==		== org.simantics.scenegraph features ==

	[[svn:2d/trunk/org.simantics.scenegraph/src/org/simantics/scenegraph\|org.simantics.scenegraph]] package contains lots of readymade nodes and features. For a list of g2d nodes, see [[~~svn:2d/trunk/org.simantics.scenegraph/src/org/simantics/scenegraph/g2d/nodes\|org.simantics.scenegraph.g2d.nodes~~]].		[[svn:2d/trunk/org.simantics.scenegraph/src/org/simantics/scenegraph\|org.simantics.scenegraph]] package contains lots of readymade nodes and features. For a list of g2d nodes, see [[Scene graph node list]].

	===Swing support===		===Swing support===

Tuukka Lehtonen: /* Architecture */

2011-10-04T09:58:58Z

Architecture

← Older revision		Revision as of 09:58, 4 October 2011
Line 27:		Line 27:
	These annotations (except PropertySetter) are handled with cglib MethodInterceptor which is a proxyclass for the actual class implementation, and contains an interceptor for performing actions before and after the actual method is called. For this reason, the Node classes should not be instantiated directly, but through <code>ParentNode.addNode</code> method. Cglib support is implemented in org.simantics.scenegraph.remote plugin, and thus org.simantics.scenegraph plugin does not depend on cglib.		These annotations (except PropertySetter) are handled with cglib MethodInterceptor which is a proxyclass for the actual class implementation, and contains an interceptor for performing actions before and after the actual method is called. For this reason, the Node classes should not be instantiated directly, but through <code>ParentNode.addNode</code> method. Cglib support is implemented in org.simantics.scenegraph.remote plugin, and thus org.simantics.scenegraph plugin does not depend on cglib.

	{{tip\|Scene graph ~~subnodes~~ must not be instantiated directly, but through <code>ParentNode.addNode</code> or <code>ParentNode.getOrCreate</code> methods. Only the root node may be instantiated directly.}}		{{tip\|Scene graph sub-nodes must not be instantiated directly, but through <code>ParentNode.addNode</code> or <code>ParentNode.getOrCreate</code> methods. Only the root node may be instantiated directly.}}

	ParentNode and Node classes implement only functionalities for creating and modifying the scene graph datastructure but do not contain any methods for rendering.		ParentNode and Node classes implement only functionalities for creating and modifying the scene graph datastructure but do not contain any methods for rendering.

Tuukka Lehtonen: /* Architecture */

2011-10-04T09:57:31Z

Architecture

← Older revision		Revision as of 09:57, 4 October 2011
Line 27:		Line 27:
	These annotations (except PropertySetter) are handled with cglib MethodInterceptor which is a proxyclass for the actual class implementation, and contains an interceptor for performing actions before and after the actual method is called. For this reason, the Node classes should not be instantiated directly, but through <code>ParentNode.addNode</code> method. Cglib support is implemented in org.simantics.scenegraph.remote plugin, and thus org.simantics.scenegraph plugin does not depend on cglib.		These annotations (except PropertySetter) are handled with cglib MethodInterceptor which is a proxyclass for the actual class implementation, and contains an interceptor for performing actions before and after the actual method is called. For this reason, the Node classes should not be instantiated directly, but through <code>ParentNode.addNode</code> method. Cglib support is implemented in org.simantics.scenegraph.remote plugin, and thus org.simantics.scenegraph plugin does not depend on cglib.

	{{tip\|Scene graph ~~node classes~~ must not be instantiated directly, but through <code>ParentNode.addNode</code> or <code>ParentNode.getOrCreate</code> methods.}}		{{tip\|Scene graph subnodes must not be instantiated directly, but through <code>ParentNode.addNode</code> or <code>ParentNode.getOrCreate</code> methods. Only the root node may be instantiated directly.}}

	ParentNode and Node classes implement only functionalities for creating and modifying the scene graph datastructure but do not contain any methods for rendering.		ParentNode and Node classes implement only functionalities for creating and modifying the scene graph datastructure but do not contain any methods for rendering.

Tuukka Lehtonen: /* Architecture */

2011-10-04T09:55:34Z

Architecture

← Older revision		Revision as of 09:55, 4 October 2011
Line 25:		Line 25:
	Without these annotations, the Node will not work properly when using scenegraph remotely.		Without these annotations, the Node will not work properly when using scenegraph remotely.

	These annotations (except PropertySetter) are handled with cglib MethodInterceptor which is a proxyclass for the actual class implementation, and contains an interceptor for performing actions before and after the actual method is called. For this reason, the Node classes should not be instantiated directly, but through ParentNode.addNode method. Cglib support is implemented in org.simantics.scenegraph.remote plugin, and thus org.simantics.scenegraph plugin does not depend on cglib.		These annotations (except PropertySetter) are handled with cglib MethodInterceptor which is a proxyclass for the actual class implementation, and contains an interceptor for performing actions before and after the actual method is called. For this reason, the Node classes should not be instantiated directly, but through <code>ParentNode.addNode</code> method. Cglib support is implemented in org.simantics.scenegraph.remote plugin, and thus org.simantics.scenegraph plugin does not depend on cglib.

			{{tip\|Scene graph node classes must not be instantiated directly, but through <code>ParentNode.addNode</code> or <code>ParentNode.getOrCreate</code> methods.}}

	ParentNode and Node classes implement only functionalities for creating and modifying the scene graph datastructure but do not contain any methods for rendering.		ParentNode and Node classes implement only functionalities for creating and modifying the scene graph datastructure but do not contain any methods for rendering.

Tuukka Lehtonen: /* Scenarios */

2011-09-30T11:33:28Z

Scenarios

← Older revision		Revision as of 11:33, 30 September 2011
Line 279:		Line 279:

	== Scenarios ==		== Scenarios ==

			* TODO: implementing your own G2DNode, what render needs to do
			* TODO: hooking nodes to UI events
			* TODO: picking
			* TODO: global <-> local coordinate system transformations
			* TODO: mouse capture

	* [[Scene Graph: Sysdyn-scenario]]		* [[Scene Graph: Sysdyn-scenario]]

Tuukka Lehtonen: /* Serialization */

2011-07-19T15:55:56Z

Serialization

← Older revision		Revision as of 15:55, 19 July 2011
Line 75:		Line 75:
	serializer.start();		serializer.start();

	After this, the root node can be used normally. Any child added to it will be created by cglib automatically, hence Serializer works automatically with ~~these~~ whole scene graph data structure.		After this, the root node can be used normally. Any child added to it will be created by cglib automatically, hence Serializer works automatically with the whole scene graph data structure.

	On the client side, Serializer can be directly attached to object streams, and it will create G2DSceneGraph object for you:		On the client side, Serializer can be directly attached to object streams, and it will create G2DSceneGraph object for you:

Tuukka Lehtonen: /* Implementation scenarios */

2011-07-19T15:52:07Z

Implementation scenarios

← Older revision		Revision as of 15:52, 19 July 2011
Line 278:		Line 278:
	public <TC> TC appendParent(String id, Class<TC> nc);		public <TC> TC appendParent(String id, Class<TC> nc);

	== ~~Implementation scenarios~~ ==		== Scenarios ==

	* [[Scene Graph: Sysdyn-scenario]]		* [[Scene Graph: Sysdyn-scenario]]