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 - Viking

Pages: 1 ... 5 6 [7] 8 9 ... 16
91
Suggestions and Requests / Re: ToolBox - reuse of other stereotypes
« on: February 23, 2017, 01:40:09 am »
No and no. You have to create your toolboxes from scratch. q.
Thank you very much.

92
Suggestions and Requests / Re: ToolBox - reuse of other stereotypes
« on: February 23, 2017, 12:40:37 am »
Another question is: can I change an element in a "standard" toolbox? I want to replace the stereotype of the BPMN Actvity with a shape script, created by me. Is that possible? Probably is is possible to change the MDG-file under Sparx Systems\EA\MDGTechnologies and reimport it. But I cannot imagine that this is recommended.

93
Suggestions and Requests / ToolBox - reuse of other stereotypes
« on: February 22, 2017, 11:57:44 pm »
Hello together,

I want to create ToolBoxes that offer the elements the users are allowed to use. So a toolbox will not contain self-created shapes only. It should also show standard elements from e.g. BPMN and ArchiMate. The easiest way is to use the shape scripts of these elements. But this is not really wanted because I want to reuse (reference) what's already there. Is that possible?

Many thanks in advance, V.

94
Suggestions and Requests / Re: Properties versus Tagged Values
« on: February 22, 2017, 09:01:17 pm »
Can you confirm that's what you've done? -> Confirmed.

You will need to research MDGs. -> Agreed.

Then you ask questions. -> Agreed.

Thank you, Paolo.

95
Suggestions and Requests / Re: User Interface for Tagged Values
« on: February 22, 2017, 02:13:48 am »
I think you want to create 'profiles' to extend the types.
http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/modeling_tools/using_the_profile_helpers.html
Thank you, VKN. Seems to be exactly what I am looking for. V.

96
Suggestions and Requests / Re: Properties versus Tagged Values
« on: February 21, 2017, 06:27:33 pm »
Hi Paolo, thank you very much.

You may find that assigning the same properties you find in the original ArchiMate MDG  metatype to the new metatype in your MDG should force EA to retain the property.
HTH,
Paolo

How can I do this? I do not use MDG (as far as I undestand EA, at least not intentionally). V.


97
Suggestions and Requests / Default Colour of an Element resp. Shape
« on: February 21, 2017, 04:44:15 am »
Hello,

I am confused where the ArchiMate BusinessProcess gets its color from. It is not set in the corresponding shape script. The standard color is set to another color.

(1) Could somebody explain to me, where the default color for the ArchiMate BusinessProcess shape script is definded resp. where the shape scripts retrieves the color from?

I have implemented my own shaped scripts which uses an exact copy of the ArchiMate BusinessProcess shape script. When I assign this script to an element and the copied script gets executed, it uses a different color than the original one.

(2) Could somebody explain to me, why the exact copy of a script uses a different color than the original one?

Many thanks in advance, V.

98
Suggestions and Requests / User Interface for Tagged Values
« on: February 21, 2017, 01:42:44 am »
Elements normally have Property Dialogs assign to them. For my project I need to assign additional property-value-pairs in form of Tagged Values. I do not want to bother end-users with a text list with potential tags where the have to select the appropriate tag and add it to the property sheet with e appropriate value.

Is there a more convenient way, e.g. by prefilling the tag-list of the property sheet?

99
Suggestions and Requests / Re: Properties versus Tagged Values
« on: February 21, 2017, 12:22:47 am »
@qwerty, @paolo, thank you very much.

What confuses me is:
(1) Geert said in another discussion "Yes, Archimate properties are also Tagged Values."
(2) The original Shape Scripts of EA uses the function hastag. If I set the appropriate "property" (e.g. "showdecoration" = TRUE) the function "hastag" returns "TRUE" (and an arrow gets shown).
(3) If I create an ArchiMate BusinessProcessI on a diagram, it is normally has the property "showdecoration" set to "TRUE". The arrow (decoartion) gets displayed on the top right of the element in the diagram. As soon as I assign a sterotype (with my new Shape Script), the properties disappear in the properties sheet. I have to assign the hashtag (not hashtag) "showdecoration"to TRUE to the element to show the arrow again.

I know what properties, hashtags, stereotypes, etc. are, but I am confused in conjunction with EA.

Any ideas? V.


100
Suggestions and Requests / Properties versus Tagged Values
« on: February 20, 2017, 02:09:12 am »
Hello,

My understandig was that Properties of elements are Tagged Values. But when I use a Shape Script, than I have to add the tagged value again for the property set before (in my case "showdecoration" of ArchiMate Activity).

Did I do something wrong or is my understanding wrong?

V

101
Suggestions and Requests / Re: ShapeScript for BPMN activity
« on: February 20, 2017, 02:01:46 am »
The proplem has been solved. I missed a bracket. The correct code can be found in "ShapeScript - conditional setting of variables" http://sparxsystems.com/forums/smf/index.php/topic,37909.0.html.

Thank you all for your valuable input.

102
My problem has been solved. I "forgot" one bracket and the editor did not recognize, that there are more open than close brackets. Many thanks to all. It is always a good choice using the outliner carefully.

Thank you all for your valuable input.

Edit: Unfortunately it is not solved. Now I run into property-issues :-(

103
Suggestions and Requests / Re: mdgtype,meta class, base class
« on: February 19, 2017, 10:53:40 pm »
Hi Viking,

If you are talking about the "base class" in the stereotype page of the UML types dialog, it is misnamed.  It should be captioned: "Metaclass to which to apply this stereotype".   You can define more than one stereotype with the same name and apply each to a different metaclass.  You may even note that you can apply it to "<All>", but not to "<Shapes>" or "<Lines>".
I don't believe it has anything (directly) to do with inheritance - since you can apply the "<All>" value.
HTH,
Paolo

Hi Paolo, thank you very much.

For my opinion the manuals are to short for this domain.

V

104
Because decoration needs to be on top level.q.
O.K., this is also what I told Paolo.

That's why I wanted to use an if-statement. But the variable-seeting has to be before the if-statement. Is there a way to put the variable-setting inside the if-statement?

The reason why I stick to the decorations is that I want to reuse the standard-shapescripts due to maintenance.

105
... and if I use the decoration statement after a shape-statement, it is not excuted either.

Code: [Select]
shape ProcessStep
{
layouttype="border";
v_align="center";
h_align="center";

if(hasproperty("rectanglenotation","0"))
{
defsize(90,40);
startpath();
moveto(0,0);
lineto(75,0);
lineto(75,-30);
lineto(100,50);
lineto(75,130);
lineto(75,100);
lineto(0,100);
lineto(0,0);
endpath();
fillandstrokepath();
}
else
{
defsize(105,70);
roundrect(0,0,100,100,20,20);
addsubshape("padding","n");
addsubshape("name","center");

shape padding
{
preferredheight=20;
}

shape name
{
h_align="center";
print("#name#");
}
}

shape label
{
setorigin("sw",0,0);

if(hasproperty("rectanglenotation","0"))
{
print("#name#");
}
}

decoration process
{
orientation="ne";

if(hasproperty("rectanglenotation","0"))
{
}
else
{
if(hastag("showdecoration","true"))
{
moveto(0,25);
lineto(55,25);
lineto(55,0);
lineto(80,50);
lineto(55,100);
lineto(55,75);
lineto(0,75);
lineto(0,25);
}
}
}

decoration atomic
{
orientation="nw";

if(hastag("atomic","true"))
{
ellipse(0,0,100,100);
moveto(20,80);
lineto(50,20);
lineto(80,80);
moveto(35,50);
lineto(65,50);
}
}

decoration composite
{
orientation="SE";
if(hasproperty("iscomposite","true"))
{
ellipse(0,40,40,60);
ellipse(60,40,100,60);
moveto(30,50);
lineto(70,50);
}
}
}

If I put the decoration-statement after the shape-statement (on the same level resp. top-level) it gets executed.

Why?

Pages: 1 ... 5 6 [7] 8 9 ... 16