Community
Participate
Working Groups
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.
Requested by AiE (SH)
Out-of-scope for Juno unless there are contributions in this area
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
