Hierarchical models via multiple GGraph instances? #446
-
Hello! I came across a discussion post (#353) while trying to research the same use case it proposes. I was wondering if there is a publicly accessible example somewhere using the "workaround number 1" in the provided answer (Navigating between separate diagrams, presumably GGraph objects?). This solution sounds perfect for what I am attempting to implement with GLSP (that being UML-RT). Though, the concept seems outside the scope of current examples that I've come across in my attempted adaptation. From what I can already tell, I'll probably need to represent certain objects as both GNodes and GGraphs, in order to have this work. I'm also not certain what would be the best way to cache these objects. Finally, I'm not a very experienced front-end developer, so the client plugin would probably be the hardest part. Is there an existing GLSP message/call that can ask the server to switch the graph view within the same model? (Perhaps as part of the context menu?). Any info on this particular implementation/workaround would be greatly appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi, I'm afraid there is no publicly accessible example. However, I would recommend to proceed as follows:
This will result in a new rendering of the detail diagram whenever the trigger defined in the first step is activated. |
Beta Was this translation helpful? Give feedback.
Hi,
I'm afraid there is no publicly accessible example. However, I would recommend to proceed as follows:
RequestModelAction
from the client to the server on the aforementioned event. You can use theRequestModelAction.options
to specify the context (e.g. the ID of the element for which you want to request the detail model).RequestModelAction
e.g. in your ModelSourceLoader and construct the detail model (GModel) and send it to the client via theModelSubmissionHandler
.T…