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 - David Rains

Pages: [1] 2 3 ... 6
1
Sorry, but I just can't seem to find this option again... in version 14...

Okay - Found IT: Start | View | Visual Style | Application | ....  <sigh>

2
Reviving this as I have the same question, but could not find a response...

This looks like it could be handy for storing some option switches for a stereotyped element... then based on the "values" checked (true/false) I will react via a shapescript...
(other solutions but was interested in this approach.... as I was interested in some visual cues...)


3
Okay, so the stereotype package's frame is the exact same size as a default package, so it seems that the frame size is based on the "source" element type.
My only way to achieve my goal with a stereotype package, is to:
   fixedAspectRatio = "true";
   defsize(100,100);

Then after importing the MDG containing the stereotyped package with the shapescript (redrew the image maximizing screen 100 x 100), drag onto diagram (the drawn image is NOW the same size as the frame and manually grab a corner and reduce it's size... of course the font size becomes too small and moves UP... so I increase the FONT and I can live with the name displayed in the middle...

Thanks to KP and qwerty (read through the ShapeScript made Easy again!), Looking forward to checking out the updates on Scripting EA too!

I remember reading about a project/tool to create a point and click to define shape-script commands for shapes... any idea where that was and any status on that?

David 'Biofom' Rains - Dragging BA's into the ReqEng arena 1 project at a time :)

4
I have a similar issue, I am chasing on modifying the default "frame" size of the source element for the stereotyped image created with a shapescript...

Okay, got that working (redrew image to occupy 100X100 in X/Y in shapescript and adjusted shape proportions accordingly) then added...

   fixedAspectRatio = "true";    defsize(100,100);

When loaded via MDG, dragged onto diagram Frame Same size as Image... then used corner to shrink as needed.... changed the font, etc. since it is a package that I stereotype, once I adjusted it... I can't just copy and paste.... have to repeat those steps each time :( Could add some automation code later....


David

5
I have created a custom shape for a stereotype using a shape script, however the size of the "frame" when you click on the element is bigger than the shape. Is there a way to redefine that frame to be closer to the size of the displayed image.

Problem will be when multiple images are displayed on a diagram the selection "frames" will overlap resulting in an unpleasant experience  :o

Am I forgetting a setting within the script or a "_setting" as an attribute of the element?

Thanks,

David (Bioform) Rains - It is good to be back working in EA!  :D

6
I will try that. It was accepted as a bug, and I am now actually creating an MDG instead (in the past I am not creating profiles for other users, just myself). So I have bit the bullet and have started down that path... Partly implementing OntoUML... (1st attempt without model validation, but with constraints on relationship type connectors against stereotype classes)

Just tried to implement constraints on multiplicity of my stereotyped association using the Add Stereotype | Profile Helper (Who new how easy that was!) - Okay, almost everyone else... I was searching for a list of relationship properties.... and thought hey, I wonder.... :)


7
Okay I have verified that my profiles in both 14.1 and 15 create nothing but packages... The XML looks valid to my eyes... (selected parts below)... Not an exhaustive test, but of 7 different element types each of which is NOT a class, they all represent as classes... [going to delete the project and start from scratch...]

<?xml version="1.0" encoding="WINDOWS-1252"?>
-<UMLProfile profiletype="uml2">
<Documentation notes="Party" version="" name="Party" id="3E785814-4"/>
-<Content>
-<Stereotypes>
-<Stereotype notes="" name="memberIn" hideicon="0" borderwidth="-1" bordercolor="-1" fontcolor="-1" bgcolor="-1" cy="70" cx="90">
-<AppliesTo>
-<Apply type="Association">
<Property name="compositionKind" value="none"/>
<Property name="direction" value="Source -> Destination"/>
</Apply>
</AppliesTo>

</Stereotype>
-<Stereotype notes="" name="orgOf" hideicon="0" borderwidth="-1" bordercolor="-1" fontcolor="-1" bgcolor="-1" cy="70" cx="90">
-<AppliesTo>
-<Apply type="Dependency">
<Property name="direction" value="Source -> Destination"/>
</Apply>
</AppliesTo>

</Stereotype>
-<Stereotype notes="" name="MyActor" hideicon="0" borderwidth="-1" bordercolor="-1" fontcolor="-1" bgcolor="-1" cy="70" cx="90">
-<AppliesTo>
<Apply type="Actor"/>
</AppliesTo>
</Stereotype>
....

8
There seems to have been done quite some rework (and again I feel the direction is much better than what hit me in latter versions. One strong point: the WHere Is my Menu (WHIM) is still manifested in EA releases....q.

Yes the UI in v15 does look a bit cleaner and WHIM is always an issue in major releases :) 
My tagged values in my stereotypes are showing up (as pointed out) with the other properties which is nice.. however my issues seems to be worse than I thought... my stereotyped associations are also being implemented as CLASSES?!!
So right now I am unable to produce working MDGs in v15?!!!  Could someone verify if they are having this issue? <going back to v14.1 and see what happens>

9
I am back to using EA in my new job :)  Starting creating some profiles (stereotyped packages and classes) in 14.1 (last build) and switched to 15...
Problem (tested in 14.1 and 15) is when I extend my stereotype "package" to the package metaclass, and my stereotype "class" to the class metaclass; export/import I get:

- Class Icon represented as Package, but when dragged onto diagram - it IS a stereotyped Class (ok, can live with that... I guess)
- Package Icon represented as Package, but when dragged onto diagram - it IS a stereotyped Class (umm, can't live with that....)

Anyone else experiencing this... Any workarounds... I can live without some of the tagged values on the packages, and such if I have to... and just define the Stereotypes manually...

BTW: Was going to stay in 14 as an add-in I am trying out (OntoUML) works in 14.1 but not in 15. But is it worth jumping into 15 at this time? Might not be a bad time for me (or my client as this will be totally new to them...)


Thanks as always... (this seems to be a common issue with releases if memory serves me...)

David "Back in the EA space" Rains

10
Bugs and Issues / Re: Glossary matching options
« on: July 31, 2019, 07:13:16 am »
And yet years have gone by with no action...

11
"a full-fledged scripting experience" - gave me hope... Last time had to install MS Studio app and uninstall to get the script debugger to be retained... your link saved me a lot of trouble and uninstalls. Thanks

12
Like a charm!!  Added to my karama debt and my EA download collection! (New Laptop, so still doing installs)... Having some fun with Python/nltk and NLP of requirement and engineering documents at work :); and well playing/learning with corpus of Holy Grail... keep getting sidetracked on quotes about swallows and coconuts...

13
Hmm... edited link in my post that should work now...

14
"If you just need the Debugging Tools for Windows 10, and not Windows Driver Kit (WDK) for Windows 10 or Visual Studio 2017, you can install the debugging tools as a standalone component from the Windows SDK. In the SDK installation wizard, select Debugging Tools for Windows, and deselect all other components."
from (UPDATED LINK): https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools

WinDbg Preview is a new version of WinDbg with more modern visuals, faster windows, a full-fledged scripting experience, built with the extensible debugger data model front and center. WinDbg Preview is using the same underlying engine as WinDbg today, so all the commands, extensions, and workflows still work as they did before.

So do we know if this will work with EA scripting as the debugger?

15
Okay, so I did some other work on my new laptop, reopened the EA 14.1 file and it is fine?! <sigh>

Pages: [1] 2 3 ... 6