Community
Participate
Working Groups
create sub models (integration of EMF control command) With "control" command, a wizard is displayed to choose the name and directory of the new sub model file. By default, the directory is the same as the current (parent) model and the name is the one of the current element on which the "control" command is applied. If there are profiles applied in the parent model, those profile applications must be done for the controllled sub model so that stereotypes can be seen. In parent model, the submodel can be seen but is in readOnly. In sub model, if there are dependencies with the parent model (types, actors...) the parent model maight be loaded as additional resource but must be set in readonly.
the feature is now available on the trunk and partially implemented. Applied profiles are not managed yet. You can read specifications document to know the status. It is available as attached file of task 275628. For now you can control as a first level. Notation and/or DI metamodel must be improved to manage several levels.
The feature is now implemented. There are some restrictions on Uncontrol command because of additional resources saving. It will be implemented once we will be able to save the additional resources.
- update history when uncontrol is done is specific cases. Need to update resourceURL of controlled resources in low levels - disable control/uncontrol action from an incorrect resource. Control is possible from the resource that contains the selection. A popup warn the user about this behavior
fix bug with children assignment in historic for specific cases of control
fix bug with children assignment in historic for specific cases of control and relative paths
I backported the getAssociated* methods in diresourceset. This is added to avoid completely breaking the control mode but this needs to be removed before the release by modifying the di model to be hierarchical for example.
(In reply to comment #3) > - update history when uncontrol is done is specific cases. Need to update > resourceURL of controlled resources in low levels > - disable control/uncontrol action from an incorrect resource. Control is > possible from the resource that contains the selection. A popup warn the user > about this behavior Fixed.
regarding the history model : This is now quite useless, we have a fallback method (in 0.8 at least) that go throught all the resources in the resource set looking for the fragment. I am planning to deprecate the history model and remove all references to it but this will be done after the release since I am quite busy ATM.
