Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Murat

Pages: [1]
1
Yes, sorry. I'm no longer a power user and only comment on my fainting memory. I dug into and yes, the ex ist just something that is useful when setting it where it will accept an FQN

....

q.

That works perfectly. Thank you very much!
I parse the profile name via regex with "FQName=([^:]+)" (or the whole FQN with "FQName=([^;]+)") and it does its job  :)

How did you figure that out? Is there some kind of documentation for the SQL tables?

2
1) Basically yes, but making individual tooloxes is a bit more complex overall.

2) If stereotypex does not give the profile name then the stereotype is likely some "wild" one. Have you cross-checked with the stereotype properties?

3) That's probably either a manual task or one done by a script knowing how to transform the one stereo into another.

Thank you for your quick response!
So I have an example Project, where I have two "test"-elements. Here you can see the properties of the first element inside EA ("MDG-Test::My Stereotype A"):

Here you can see the properties I am retrieving in my add-in ("My Stereotype A"):


I still haven't found a way to read the technology name (in this case "MDG-Test").
The manual, messy way would be to have the user manually enter the technology name in the add-in. From this I could then "build" the stereotypes.
What do you think? Is there a better way to do this?

3
You can't really extract the toolbox content. You would need to read and parse the corresponding MDG which is not always available. If so, parsing it will give you headaches. Probably you have to hard-code  you menu. Question: why? If you have a good answer: go ahead. Else: teach them to use the toolbox which is adaptable flexibly.

q.

Thank you for your response! This is the problem I am facing now:

I want to provide users with their own MDGs the capability to have my tool recursively scan and extract the types and stereotypes of the elements within the project. The goal is to store these types and stereotypes and make them available to users later, allowing them to create new elements. I understand that the selection will be limited to the elements that have already been created but that's fine.

Now, I have a couple of questions that I hope you can help me with:

For creating elements within these custom MDGs, do I only need the type name and stereotype name in the format "Technologyname::Stereotype," or is there more information required?

My second question is related to extracting the technology name. When I use element.StereotypeEx to retrieve the stereotype name of the elements, it returns only the stereotype without the technology name. How can I obtain the technology name as well?

The reason I'm trying to do this is to allow users to import elements from another tool and specify as which element type and stereotype these imported elements should be recognized.

4
Hey guys,

I would like to enable users of my Add-In to have a dropdown menu within the Add-In that provides them with all (for them) possible diagram elements (Actor, Use Case, State, Activity and so on) from UML, SysML, and BPMN for selection.

My idea was to retrieve the version of Enterprise Architect that the user is using and based on that, extract the available element types to later utilize these types in the "repository.elements.AddNew(Name, type)" function. However, I am facing two challenges: I don't know how to retrieve the version within the Add-In, and I'm unsure how to extract the element list based on that version.

Therefore, what I need is a list of possible "UML metaclass types" and "fully-qualified metatypes defined by an MDG Technology" for SysML and BPMN.

I would appreciate any guidance on how to approach this issue or if there is a better alternative solution available.

Thank you in advance for your help!

Pages: [1]