Issue subsystem general description - Revision history

Tuukka Lehtonen: /* Continuous issue sources */

2012-03-15T15:51:16Z

Continuous issue sources

← Older revision		Revision as of 15:51, 15 March 2012
Line 109:		Line 109:
	* '''org.simantics.issues.common.IssueUtils.listenActiveProjectIssueSources'''		* '''org.simantics.issues.common.IssueUtils.listenActiveProjectIssueSources'''
	* '''org.simantics.issues.common.DependencyIssueValidator2''' for validating a context resource		* '''org.simantics.issues.common.DependencyIssueValidator2''' for validating a context resource
	* '''org.simantics.issues.common.~~DependencyIssueSynchronized2~~''' for synchronizing the model		* '''org.simantics.issues.common.DependencyIssueSynchronizer2''' for synchronizing the model

	In practice, the developer needs to define		In practice, the developer needs to define

Tuukka Lehtonen: /* Issues View */

2012-03-15T15:16:29Z

Issues View

← Older revision		Revision as of 15:16, 15 March 2012
Line 57:		Line 57:
	= Issues View =		= Issues View =

	The ''Issues'' view shows all issues in the active model(s). Active models are determined by the set of models linked to the current '''project''' with '''L0X.Activates'''.		The ''Issues'' view shows all issues in the active model(s). Active models are determined from the set of models linked to the current '''project''' with '''L0X.Activates'''.

	= User issues =		= User issues =

Tuukka Lehtonen at 15:15, 15 March 2012

2012-03-15T15:15:58Z

← Older revision		Revision as of 15:15, 15 March 2012
Line 54:		Line 54:

	Typically these are computational properties and e.g. the Description value is asserted in the issue type and computed from context resources.		Typically these are computational properties and e.g. the Description value is asserted in the issue type and computed from context resources.

			= Issues View =

			The ''Issues'' view shows all issues in the active model(s). Active models are determined by the set of models linked to the current '''project''' with '''L0X.Activates'''.

	= User issues =		= User issues =

Tuukka Lehtonen: /* Batch issue sources */

2012-03-12T07:17:49Z

Batch issue sources

← Older revision		Revision as of 07:17, 12 March 2012
Line 86:		Line 86:
	Batch issue source instances (ISSUE.BatchIssueSource) adapt to the interface '''org.simantics.issues.common.BatchIssueSource'''.		Batch issue source instances (ISSUE.BatchIssueSource) adapt to the interface '''org.simantics.issues.common.BatchIssueSource'''.

	The code '''org.simantics.issues.ui.handler.RunActiveValidations''' performs active batch validations. Currently batch issue sources are searched from the '''project''' resource by relation '''L0X.Activates'''.		The code '''org.simantics.issues.ui.handler.RunActiveValidations''' performs active batch validations. Currently batch issue sources are searched from the '''project''' resource by relation '''L0X.Activates'''. The activations are put in place using project features that link the project to the issue sources in the ontology.

	= Continuous issue sources =		= Continuous issue sources =

Antti Villberg at 21:50, 11 March 2012

2012-03-11T21:50:57Z

← Older revision		Revision as of 21:50, 11 March 2012
Line 1:		Line 1:
	The Simantics issue subsystem is defined in various plugins including		The Simantics issue subsystem is defined in various plugins including

			Please note, that the issue subsystem is still in early stage of development and is subject to changes in the near future.

	* Issue model		* Issue model

Antti Villberg: /* Continuous issue sources */

2012-03-11T21:49:51Z

Continuous issue sources

← Older revision		Revision as of 21:49, 11 March 2012
Line 107:		Line 107:
	In practice, the developer needs to define		In practice, the developer needs to define

	* A set of issue types		* A set of issue types with asserted properties (with computation) and severity
	* A set of constraints assigned to types and associated issue sources		* A set of constraints assigned to types and associated issue sources
			* Possible extension functions for ensuring proper updates for all relevant changes

			The issue ontology supplies some templates for modelling typical cases

	= Miscellaneous code =		= Miscellaneous code =

Antti Villberg at 21:45, 11 March 2012

2012-03-11T21:45:59Z

← Older revision		Revision as of 21:45, 11 March 2012
Line 72:		Line 72:
	* '''org.simantics.issues.common.<severity>Issues'''		* '''org.simantics.issues.common.<severity>Issues'''
	* '''org.simantics.issues.common.IssuesOfSeverity'''		* '''org.simantics.issues.common.IssuesOfSeverity'''

	~~= Batch issues =~~

	~~Batch issue source instances (ISSUE.BatchIssueSource) adapt to the interface '''org.simantics.issues.common.BatchIssueSource'''.~~

	The code '''org.simantics.issues.ui.handler.RunActiveValidations''' performs active batch validations. Currently batch issue sources are searched from the '''project''' resource by relation '''L0X.Activates'''.

	= Computational issues =		= Computational issues =
Line 86:		Line 80:
	* Continuous issue sources, which can track the set of issues from given context		* Continuous issue sources, which can track the set of issues from given context

	= ~~Code~~ =		= Batch issue sources =

	~~The~~ issue ~~model can be manipulated using~~ the ~~following codes~~		Batch issue source instances (ISSUE.BatchIssueSource) adapt to the interface '''org.simantics.issues.common.BatchIssueSource'''.

	* '''org.simantics.issues.~~common~~.~~Issue~~''' ~~and especially~~ '''~~org~~.~~simantics.issues.common.StandardIssue~~''' ~~for manipulating, comparing and storing issues into database. StandardIssue assumes that all properties of an issue are determined by assertions in the issue type~~.		The code '''org.simantics.issues.ui.handler.RunActiveValidations''' performs active batch validations. Currently batch issue sources are searched from the '''project''' resource by relation '''L0X.Activates'''.

	~~Some utility codes can be found in~~		= Continuous issue sources =

			Continuous issue source instances (ISSUE.IssueSource with ISSUE.IsContinuous) adapt to the interface '''org.simantics.issues.common.IssueSource'''.

			Currently the only supported implementation of IssueSource is '''org.simantics.issues.common.DependencyIssueSource2'''. The implementation is defined for '''ISSUE.Sources.DependencyTracker'''. It uses

	* '''~~org~~.~~simantics~~.~~issues~~.~~common~~.~~IssueUtils~~'''		* DependencyChanges metadata for determining which resources need revalidation. The set of changed resources from DependencyChanges is expanded to include all resources reachable by '''L0.IsDependencyOf'''.
			* '''ISSUE.Sources.DependencyTracker.HasType''' for determining which resource instances to validate
			* '''ISSUE.Sources.DependencyTracker.HasSearchType''' for determining which resource to traverse after changes and before applying the '''extension'''.
			* '''ISSUE.Sources.DependencyTracker.HasExtension''' for applying an extension function for the set of potentially changed resources
			* '''ISSUE.Sources.DependencyTracker.HasBaseFunction''' for determining a resource under which changes are tracked (by default before this function the base resource is the L0.PartOf of the issue source)
			* '''ISSUE.Sources.DependencyTracker.HasConstraint''' for defining the test to be performed on the selected resources

	The main codes for continuous validation are		The main codes for continuous validation are
Line 101:		Line 104:
	* '''org.simantics.issues.common.DependencyIssueValidator2''' for validating a context resource		* '''org.simantics.issues.common.DependencyIssueValidator2''' for validating a context resource
	* '''org.simantics.issues.common.DependencyIssueSynchronized2''' for synchronizing the model		* '''org.simantics.issues.common.DependencyIssueSynchronized2''' for synchronizing the model

			In practice, the developer needs to define

			* A set of issue types
			* A set of constraints assigned to types and associated issue sources

			= Miscellaneous code =

			The issue model can be manipulated using '''org.simantics.issues.common.Issue''' and especially '''org.simantics.issues.common.StandardIssue'''. The interface and implementation supports manipulation, comparison and storing of issues into database. StandardIssue assumes that all properties of an issue are determined by assertions in the issue type (i.e. the issue is fully determined by type, contexts, name and creation time)

			Some utility codes can be found in

			* '''org.simantics.issues.common.IssueUtils'''

Antti Villberg: /* Batch issues */

2012-03-11T21:24:24Z

Batch issues

← Older revision		Revision as of 21:24, 11 March 2012
Line 74:		Line 74:

	= Batch issues =		= Batch issues =

			Batch issue source instances (ISSUE.BatchIssueSource) adapt to the interface '''org.simantics.issues.common.BatchIssueSource'''.

			The code '''org.simantics.issues.ui.handler.RunActiveValidations''' performs active batch validations. Currently batch issue sources are searched from the '''project''' resource by relation '''L0X.Activates'''.

	= Computational issues =		= Computational issues =

Antti Villberg at 21:14, 11 March 2012

2012-03-11T21:14:28Z

← Older revision		Revision as of 21:14, 11 March 2012
Line 72:		Line 72:
	* '''org.simantics.issues.common.<severity>Issues'''		* '''org.simantics.issues.common.<severity>Issues'''
	* '''org.simantics.issues.common.IssuesOfSeverity'''		* '''org.simantics.issues.common.IssuesOfSeverity'''

			= Batch issues =

	= Computational issues =		= Computational issues =

Antti Villberg: /* Basics */

2012-03-11T21:13:26Z

Basics

← Older revision		Revision as of 21:13, 11 March 2012
Line 49:		Line 49:
	* Path ('''ISSUE.Issue.path'''), which is a textual representation of the location of the main context resource		* Path ('''ISSUE.Issue.path'''), which is a textual representation of the location of the main context resource
	* Severity ('''ISSUE.Issue.severity'''), which is a textual representation of issue severity		* Severity ('''ISSUE.Issue.severity'''), which is a textual representation of issue severity
			* Creation time ('''ISSUE.HasCreationTime'''), which is a textual representation of time of creation of the issue

	Typically these are computational properties and e.g. the Description is asserted in the issue type and computed from context resources.		Typically these are computational properties and e.g. the Description value is asserted in the issue type and computed from context resources.

	= User issues =		= User issues =