Bugzilla – Full Text Bug Listing
| Summary: | Improve layout or reusability of widgets | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Sirius | Reporter: | Arthur Daussy <arthur.daussy_ssii> | ||||||||
| Component: | Properties | Assignee: | Pierre-Charles David <pierre-charles.david> | ||||||||
| Status: | NEW --- | QA Contact: | |||||||||
| Severity: | enhancement | ||||||||||
| Priority: | P3 | CC: | maxime.porhel | ||||||||
| Version: | 4.0.0 | Keywords: | triaged | ||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 7 | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 263079 [details]
Code use case (MM/Viewpoint/Test model)
Created attachment 263080 [details]
Metamodel screenshot
|
Created attachment 263078 [details] Layout problem Hello, Here is the problem we are trying to solve. We have a big metamodel with (300 EClass) with a lot a features (850 features). We would like to group our features using the EClass hierarchy in order to reuse it. However when we do so the layout is not so nice (see screenshot). To understand our problem I have created an small use case (see attachment). Our needs would be to: * Only define 1 widget for an EStructural feature and reuse it for all EClasses * We don't want to visually group those features * Have a proper layout Here is the leads that we think might solve our problem: * Group can reference other widgets (no containment) * Or if a group have no style (no concrete representation) the widgets are added directly in the SWT composite of the page * Or page can reference other widgets (no containment) * Or other... Regards Arthur