Org.simantics.views - Revision history

Antti Villberg: /* Modelling */

2011-10-24T13:49:49Z

Modelling

← Older revision		Revision as of 13:49, 24 October 2011
Line 8:		Line 8:

	== Modelling ==		== Modelling ==

			The scene graph hierarchy is defined by the property http://www.simantics.org/Views-1.0/HasChildren which evaluates to list of resources.

	=== Composite ===		=== Composite ===

Antti Villberg: /* SWT */

2011-10-24T13:47:52Z

SWT

← Older revision		Revision as of 13:47, 24 October 2011
Line 83:		Line 83:
	root.createControls(body);		root.createControls(body);

			</pre>

			A typical modelled view such as org.simantics.selectionview.ModelledTabContribution tracks the workspace selection and writes the selection value in the runtime resource.

			<pre>
			graph.claimLiteral(runtime, VIEW.Runtime_HasVariable, uri, Bindings.STRING);
			</pre>

			A modelled view then defines e.g. a value of a Text control by a function, which depends on the input.

			<pre>
			@SCLValue(type = "ReadGraph -> Resource -> Variable -> String")
			public static Object getName(ReadGraph graph, Resource resource, Variable context) throws DatabaseException {
			Variable var = ViewUtils.getVariableSelection(graph, context);
			return var.getPropertyValue(graph, Variables.NAME, Bindings.String);
			}
			</pre>

			Another function can depend on some state written by other controls (user input).

			<pre>
			@SCLValue(type = "ReadGraph -> Resource -> Variable -> String")
			public static Object getModelName(ReadGraph graph, Resource resource, Variable context) throws DatabaseException {
			DomainResource DR = DomainResource.getInstance(graph);
			return ViewUtils.getParameter(graph, context, DR.ExportWizard_SelectedModel, Bindings.STRING);
			}
	</pre>		</pre>

Antti Villberg: /* SWT */

2011-10-24T13:38:53Z

SWT

← Older revision		Revision as of 13:38, 24 October 2011
Line 64:		Line 64:

	}		}

			</pre>

			The loader requires a virtual runtime resource which is used to store transient model data served by the context Variable.

			<pre>

			VirtualGraph vg = session.getService(VirtualGraph.class);
			Resource runtime = session.sync(new WriteResultRequest<Resource>(vg) {
			@Override
			public Resource perform(WriteGraph graph) throws DatabaseException {
			return graph.newResource();
			}
			});

			SWTViewLoaderProcess loader = new SWTViewLoaderProcess(null, null);
			SWTRoot root = loader.load(viewURI, runtime);
			root.createControls(body);

	</pre>		</pre>

Antti Villberg at 13:33, 24 October 2011

2011-10-24T13:33:05Z

← Older revision		Revision as of 13:33, 24 October 2011
Line 50:		Line 50:

	== Implementation ==		== Implementation ==

			=== SWT ===

			SWT view scene graphs are created using org.simantics.views.swt.SWTViewLoaderProcess. The loader creates a scene graph based on org.simantics.views.swt.client.base.ISWTViewNode, which allows for creating the view under a SWT composite.

			<pre>

			public interface ISWTViewNode extends INode {

			Control getControl();
			IWorkbenchSite getSite();
			void createControls(Composite parent);

			}

			</pre>

Antti Villberg: /* Modelling */

2011-10-24T13:16:52Z

Modelling

← Older revision		Revision as of 13:16, 24 October 2011
Line 9:		Line 9:
	== Modelling ==		== Modelling ==

			=== Composite ===

			Composites are used mainly to lay out other controls.

			=== Label ===

			Labels display read-only text.

			=== Text ===

			Text represents an editable text, which produces instant notification of any changes.

			=== Button ===

			Button represents a standard button.

			=== Combo ===

			Combo represents a standard drop-down.

			=== Tracked Text ===

			Tracked text represents an editable text, which produces change notifications only when the editing operation ends.

			=== Explorer ===

			Explorer represents a browse context as tree.

			=== TabFolder ===

			Tab folders represent a stack of composites.

			=== Scrolled Composite ===

			Scrolled composite is a composite which does not impose its size restrictions on its children.

			=== Combo2 ===

			Combo2 is a variation of Combo.

	== Implementation ==		== Implementation ==

Antti Villberg: /* Basic concepts */

2011-10-24T13:07:29Z

Basic concepts

← Older revision		Revision as of 13:07, 24 October 2011
Line 5:		Line 5:
	A modelled view is a structural model of '''controls'''. The model configuration can be evaluated to produce a scene graph as defined in org.simantics.scenegraph. A single view configuration can be evaluated into multiple different scene graphs with different node types (e.g. SWT, AWT, PDF, HTML). The evaluation is done in the context of org.simantics.db.layer0.variable.Variable.		A modelled view is a structural model of '''controls'''. The model configuration can be evaluated to produce a scene graph as defined in org.simantics.scenegraph. A single view configuration can be evaluated into multiple different scene graphs with different node types (e.g. SWT, AWT, PDF, HTML). The evaluation is done in the context of org.simantics.db.layer0.variable.Variable.

	The properties of controls in a modelled view are often defined as functions of an external input assigned to the evaluation context e.g. a view can be defined to represent the current workspace selection.		The properties of controls in a modelled view are often defined as functions of an external input assigned to the evaluation context e.g. a view can be defined to represent the current workspace selection. In the control hierarchy, relative references can also be modelled e.g. an action can be applied on an output of a specific control. It is also possible to declare a substructure of controls as a type such that some properties in the substructure are defined as functions of some interface properties declared in the type and defined in instances of that type.

	In the control hierarchy, relative references can also be modelled e.g. an action can be applied on an output of a specific control.

	It is also possible to declare a substructure of controls as a type such that some properties in the substructure are defined as functions of some interface properties declared in the type and defined in instances of that type.

	== Modelling ==		== Modelling ==

Antti Villberg: /* Basic concepts */

2011-10-24T13:07:07Z

Basic concepts

← Older revision		Revision as of 13:07, 24 October 2011
Line 3:		Line 3:
	== Basic concepts ==		== Basic concepts ==

	A modelled view is ~~defined as~~ a ~~hierarchy~~ of ~~parametrized~~ '''controls'''. The model ~~generates~~ scene graph ~~models~~ defined in org.simantics.scenegraph. ~~The created~~ scene graphs ~~can then be used to populate~~ e.g. a SWT ~~containers or~~ PDF ~~documents~~.		A modelled view is a structural model of '''controls'''. The model configuration can be evaluated to produce a scene graph as defined in org.simantics.scenegraph. A single view configuration can be evaluated into multiple different scene graphs with different node types (e.g. SWT, AWT, PDF, HTML). The evaluation is done in the context of org.simantics.db.layer0.variable.Variable.

	The ~~hierarchy and properties of the modelled view~~ is ~~defined~~ in the context of org.simantics.db.layer0.variable.Variable ~~e.g. all modelled properties are evaluated using ReadGraph.getRelatedValue2 with a Variable context~~.

	The properties of controls in a modelled view are often defined as functions of an external input assigned to the evaluation context e.g. a view can be defined to represent the current workspace selection.		The properties of controls in a modelled view are often defined as functions of an external input assigned to the evaluation context e.g. a view can be defined to represent the current workspace selection.

Antti Villberg at 13:00, 24 October 2011

2011-10-24T13:00:37Z

← Older revision		Revision as of 13:00, 24 October 2011
Line 3:		Line 3:
	== Basic concepts ==		== Basic concepts ==

			A modelled view is defined as a hierarchy of parametrized '''controls'''. The model generates scene graph models defined in org.simantics.scenegraph. The created scene graphs can then be used to populate e.g. a SWT containers or PDF documents.

			The hierarchy and properties of the modelled view is defined in the context of org.simantics.db.layer0.variable.Variable e.g. all modelled properties are evaluated using ReadGraph.getRelatedValue2 with a Variable context.

			The properties of controls in a modelled view are often defined as functions of an external input assigned to the evaluation context e.g. a view can be defined to represent the current workspace selection.

			In the control hierarchy, relative references can also be modelled e.g. an action can be applied on an output of a specific control.

			It is also possible to declare a substructure of controls as a type such that some properties in the substructure are defined as functions of some interface properties declared in the type and defined in instances of that type.

	== Modelling ==		== Modelling ==

Antti Villberg: Created page with "Modelled views are structural models of graphical user interfaces defined in org.simantics.views* == Basic concepts == == Modelling == == Implementation =="

2011-10-24T12:24:05Z

Created page with "Modelled views are structural models of graphical user interfaces defined in org.simantics.views* == Basic concepts == == Modelling == == Implementation =="

New page

Modelled views are structural models of graphical user interfaces defined in org.simantics.views*

== Basic concepts ==

== Modelling ==

== Implementation ==