Community
Participate
Working Groups
The following point was raised by Stan on the dev list when he was looking at Composition/Extraction in the UI ----------------------------------------------------------------------------- Also, when you create a new concern by extraction or composition, the result ends up only under the Workspace concern. If extraction and composition apply only to units, then I understand that the result should end up at least under the Workspace. However, it seems to me that users will most of the time want to extract or compose into a new concern elsewhere in the concern space (say, under Features). It would be nice to have the ability to target the new concern to both the Workspace and to some number of additional concerns. ------------------------------------------------------------------------------ Sian's response: With composition I believe this is possible, by de-selecting 'compose immediately' in the wizard. Extraction creates a project and contents from a user-defined concern. It seems to me that it makes sense that this would go into the workspace, otherwise it would just be copying part of the model to another place in the model. ---------------------------------------------------------------------------- my response: Extraction and Composition are not fully implemented in the ui as yet. At the moment you cant extract (or the ui doesn't drive anything at the moment) and composition only follows the demo scenario i.e. you can't deselect "compose immediately" and you can only compose through merging rather than any of the other options. As for the result of composition ending up under Features, then yes, it should do (or we always planned it to), however, we didn't get this working in the demo time frame. -------------------------------------------------------------------------- This feature (enhancement request) is being raised to cover these issues
Created attachment 13907 [details] design proposal for Extraction/Composition in the UI This is the design proposal, with Andy's comments, which I put together in Feb 2004 about how extraction and compositon would work/look in the UI
The composition does not appear under 'Features' because we do not serialize it correctly, so when the model is rebuilt it is not restored. Perhaps this part should be a separate bug report and should be assigned to Matt since he wrote the serialization?
