|
Re: Filter EObject-Tree shown in aird Editor [message #1804405 is a reply to message #1804404] |
Mon, 25 March 2019 15:07 |
|
Hi Konrad,
1- Using the CNF can allow you to reduce the amount of data displayed in the Model Explorer view, another idea could be to activate the "groups" as described in the Model Explorer part of the User manual [1]. Note that this will have no impact on the load mecanisms. But both solutions could help to reduce the amount of time required to build de explorer view content (and reduce the amount of SWT handles).
2- Sirius needs the whole domain model to be loaded and resolved to work correctly (stable and safe result for the evaluation of interpreted expressions used to define the modeler, use of the cross references, ..) . When Sirius opens a session
, it loads and resolve all the referenced semantic/domain resources. If you split your project and the aird into several aird files, it could have an impact but only if the load/resolve of the reference Xtext files triggers the load of a subset of your files.
Note that regarding the changes you will make from one of this session, it could break the other aird files which will not be loaded (they might reference elements whose uri/uriFragment will change due to modifications done in one of the "sub" aird).
Overriding DAnalysisSessionImpl.collectAllReferencedResource is not a good idea. I have update my answer on your other post to add references to the slides of the video.
[1] https://www.eclipse.org/sirius/doc/user/general/Modeling%20Project.html#ModelExplorer
Maxime Porhel - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Re: Filter EObject-Tree shown in aird Editor [message #1804406 is a reply to message #1804405] |
Mon, 25 March 2019 15:27 |
Konrad Jünemann Messages: 93 Registered: December 2018 |
Member |
|
|
Hi Maxime,
thanks for your reply, I did not realize you answered to my other question.
Regarding 1: Thanks for that advice, I will look into both options.
Regarding 2: I've looked into all of these resources before, although I did not study the examples provided by Cedric in greater detail (FowlerDsl, etc.) I will do this as a next step.
- However, most reasons seem to be related to the problem of enabling the user to modify the same model by XText and Sirius - in my case I only want the user to modify the model through XText. This should simplify the issue, as the Sirius model can never be dirty, should it not?
- Furthermore, if Entity A references a Library Function L but not Entity B, while B references L as well, there is a transitive relation between A and B, but I would not want to load B automatically when I load A. Imagine L is Type "String": I would not want to automatically load all other Strings into the model, just because A is a String, right? What would be the correct way to achieve this behavior, if the mentioned collectAllReferencedResource is not the right way? My Idea was to stop the transitive cross-reference-resolution at library types, e.g., at the mentioned String-Resource.
Thank you very much for your help, I was beginning to think I am alone on this. :-)
Konrad
|
|
|
|
Powered by
FUDForum. Page generated in 0.04399 seconds