Thanks to Benjamin, we have changed the stereotypes of all elements in the FRAME Repository.
We have overlooked one minor thing, in addition to "elements", we also have stereotyped "connectors" in our model.
The IN and OUT connectors are using the old stereotypes from FrameNext profile that was created by Sparx.
I hope the same script can be used in changing stereotypes of connectors as well.
I believe we have to create new connectors, called FRAME_IN and FRAME_OUT, for the script to work properly (the new and old stereotype names must be different) (but also as i argue in #69 , we dont really need TWO seperate stereotyped connectors for this, we can happily live with only one)
I do not know of any other specialized connector that is coming from SPARX, i think if we change the IN and OUT, we will be done :)
Thanks to Benjamin, we have changed the stereotypes of all elements in the FRAME Repository.
We have overlooked one minor thing, in addition to "elements", we also have stereotyped "connectors" in our model.
The IN and OUT connectors are using the old stereotypes from FrameNext profile that was created by Sparx.
I hope the same script can be used in changing stereotypes of connectors as well. I believe we have to create new connectors, called FRAME_IN and FRAME_OUT, for the script to work properly (the new and old stereotype names must be different) (but also as i argue in #69 , we dont really need TWO seperate stereotyped connectors for this, we can happily live with only one)
I do not know of any other specialized connector that is coming from SPARX, i think if we change the IN and OUT, we will be done :)