Extending SysML Profile elements

[Hulbert@localhost Chris Hulbert]

I want to generalize, extend, etc. elements from SysML profile (e.g. block). What's the correct way to get the SysML profile stereotypes on the profile diagram to make sure I am not duplicating the SysML block stereotype?
[original message]

[M@localhost Simon M]

There is partial support for extending stereotypes from other profiles. You can use it by adding a stereotype element with the fully qualified name (eg. SysML1.2::block) to your profile. (I haven't tested if it needs to be made abstract or not.) You can then specialize the added stereotype.

Limitations that I am currently aware of that we will address in a future build

• Shape scripts and custom icons are not inherited. It's likely other things such as composite diagram types etc aren't either.
  
• It's a painful unintuitive process.
  

[original message]

[F Cantoni@localhost Paolo F Cantoni]

[original message]

[M@localhost Simon M]

It means that if you inherit from a SysML1.2::block it will be drawn currently as a stereotyped class.

Calling the parent script is a situation that we have thought of. I'm not sure at this stage if it will be possible to override subshapes.
[original message]

[Hulbert@localhost Chris Hulbert]

Any idea when inheriting the shape scripts/icons could be implemented?

Maybe there is another way to get some of what I want. One thing I would like is to set the default appearance for blocks based on multiple stereotypes. For example I all <<block,logical>> blocks to be green, and all <<block,physical>> blocks to be red. I changed my custom profile to extend the "Class" metaclass with stereotypes logical and physical. I import that profile and apply those stereotypes to blocks in a template package. Whenever I create a block and add that stereotype it's as if the template package for a block with those stereotypes is not checked again. Does it only check the template package once?
[original message]

[qwerty]

38332E37393E6A5B0 wrote:

Any idea when inheriting the shape scripts/icons could be implemented?

There is a way to extract the existing shape scripts from the provided MDG files so you can paste them in your stereotypes. I posted that in another thread and I can try to find it if you're interested.

q.
[original message]

[Hulbert@localhost Chris Hulbert]

7B7D6F787E730A0 wrote:

[quote author=38332E37393E6A5B0 link=1330884294/0#4 date=1330961044]

Any idea when inheriting the shape scripts/icons could be implemented?

There is a way to extract the existing shape scripts from the provided MDG files so you can paste them in your stereotypes. I posted that in another thread and I can try to find it if you're interested.

q.[/quote]

Yes, I would be interested. I did a quick search and did not see what you were talking about so if it is not too much trouble to find, please send me the link or repost.

Chris
[original message]

[qwerty]

Searching the forum is a PITA. I think it's easier to sum up once again (sorry for the brevity then):

- Open the MDG and locate the stereotype with notepad++
- locate the according EAShapeScript attribute inside
- copy its base64 tag contents
- paste it into a new file buffer
- select all
- Plugins/Mime Tools/Base64 Decode
- save the binary result to a temp.zip on disk
- open the zip
- inside you find a str.dat containing the shape script

q.
[original message]