Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352113

Summary:	Interactive and Programmatic Features
Product:	[Modeling] Graphiti	Reporter:	Michael Wenz <michael.wenz>
Component:	Core	Assignee:	Project Inbox <graphiti-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	hjg.com.ar
Version:	0.8.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Michael Wenz

2011-07-14 11:17:26 EDT

Graphiti should allow to distinguish between interactive and programmatic features in the  FeatureProvider. Example: the user should no be able to move/resize/delete Shapes. This happens only programmatically, so the FeatureProvider must not deliver any features. On the other hand it would ease and make development more consistent, if one could always use the FeatureProvider => Features differentiate by method IFeature.isAvailableAsInteraction() oder or different methods in the FeatureProvider.

Comment 1 Michael Wenz

2011-07-14 11:17:47 EDT

Requested by AiE (SH)

Comment 2 Michael Wenz

2011-07-14 11:18:03 EDT

Out-of-scope for Juno unless there are contributions in this area

Comment 3 Hernan Gonzalez

2011-08-30 11:11:38 EDT

I agree that this distinction "between interactive and programmatic
features" merits consideration, even if it's only for clarifyng some concepts.

- Does the FeatureProvider provides features to ... whom? 

- Is a Graphiti application supposed to have (tipically? always?) a single Feature
Provider? 
Perhaps it should be emphasized (it we agree!) that a Graphiti application has typically a single DiagramTypeProvider which in turns reference a single FeatureProvider (the "main" or "front" one), but that some scenarios (some features) can use/instantiate other providers? 

Could be the case that a Feature "has" a FeatureProvider different from the FeatureProvided that created it? 

See here http://www.eclipse.org/forums/index.php/m/720417/#msg_720417