Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: Guillaume on October 07, 2022, 09:21:35 pm
-
Hi,
I have a SysML based MDG with custom metamodels views to create bdd and idb diagrams.
Using perspectives, I can disable diagrams so users only end up for instance with activity, bdd, and ibd. Yet when then select BlockDefinition, I would like to only provide the custom MDG view and not the built-in ones such as SysML 1.4::BlockDefinition, SysML 1.4 Views: Basic Blocks, etc.
This doesn't seem to be supported. Could it be integrated in a future build ?
-
If you're asking here only, your chances to see it implemented are near zero. Send a feature request and encourage others to do the same.
q.
-
If you're asking here only, your chances to see it implemented are near zero. Send a feature request and encourage others to do the same.
q.
I think Guillaume's been around long enough to know that. I suspect he pasted a copy of the report he made to Sparx. As you know, that's my usual "modus operandi".
Paolo
-
From memory... 16.0 added the capability for the new diagram dialog to show a page for profiles that only offer views. Which means you no longer need to have SysML in your perspective in order to make your views accessible.
If you're not after a strict perspective or you extend all of the SysML elements that you want to use, that should be sufficient.
If you're after a strict perspective you may need to add a toolbox in your technology that references the original SysML stereotypes.
-
Thank you for your feedback. We're after a strict perspective.
Does it mean that we could move from the "View Specification" definition to proper Toolbox profiles to list the SysML stereotyped blocks and ports ?
I'll have to try it in EA 16.
-
Adding a toolbox was only because the strict perspective includes stereotypes referenced in the included toolboxes. The added bonus is that if your technology only includes a single toolbox all of the view specifications will use that toolbox to control the ordering and grouping of items when they view specification is controlling the toolbox.
A completely separate improvement in 16 does indirectly allow you to specify that your diagram type is an extension of a built-in diagram type. The downside of that is that it requires an add-in.
https://www.sparxsystems.com/enterprise_architect_user_guide/16.0/add-ins___scripting/technology_rules.html (https://www.sparxsystems.com/enterprise_architect_user_guide/16.0/add-ins___scripting/technology_rules.html)
If your add-in did nothing other than respond to EARules_Initialize by setting the output parameter to "SysML1.4" and returning your diagram profile name, the result is that your diagram type will have all the behavior of a SysML diagram. The feature is intended for you to perform further customizations, which is why it's an add-in function, but it will allow you to fully customize a diagram type and toolbox while maintaining the SysML behavior.