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.

Topics - Uffe

Pages: [1] 2 3 ... 27
Suggestions and Requests / Flash on the web site
« on: June 26, 2020, 05:17:10 pm »
Hey guys,

Time to get rid of all the Flash already. It makes a very bad impression on any potential customer with the least tech savvy, in addition to the practical difficulties in even viewing Flash videos these days.
And six months from now, it will be impossible.

Tick tock. Tick tock.



If you store a file in an element's Filename property, you can hit F12 to view the file in EA's internal source viewer.
Word documents are recognized and open the document editor, and of course there's the internal browser as well.

It would be useful to be able to launch files / URLs from the internal source viewer / document editor / browser. This would just pass the file path / URL to Windows, which would then open the resource with whatever application is registered for the resource type. So just like the Launch button in the File tab of the element properties dialog.


Automation Interface, Add-Ins and Tools / Setting the Special Action
« on: June 23, 2020, 06:08:59 pm »

In the browser context menu for an element, there's a submenu Properties where you can open the Properties dialog or execute the Special Action, which often does the same thing but in some cases does something else (some element types have two property dialogs associated with them).

Is there a way for the profile modeller to specify what the special action should be?
Now or in the nearish future?



Suggestions and Requests / Keyboard shortcut to open file
« on: June 23, 2020, 05:58:27 pm »

If you store a file path in an element's Filename property, you can hit F12 (with the element selected) to view the file (in EA's text editor). This is useful.

You can also store file paths and URLs in an element's list of Files (in the property dialog), and Launch them with a button (starting another program to view the file). This is also useful.

It would be usefuler still if there was a keyboard shortcut for this latter function -- Ctrl-F12 or something.

This should:
  • =1 File in the list: Launch the File;
  • >1 Files in the list: Pop a selector dialog that contains all the element's Files with Path/URL, Type and Notes, and then launch the selected one on OK;
  • =0 Files in the list: Open the properties dialog to the Files tab.
A few notes.

The Filename-view function only works on files. While you can input anything into the property value, such as a URL, EA won't open it. It has to be a file (it can't even be a directory).
The File-launch on the other hand can handle both files and "web addresses", ie URLs. There is no requirement that the protocol must be HTTP(S) or anything, so any registered protocol will work (registered in Windows, that is; it's Windows that does the actual launching).

I'm not proposing making any changes to the Filename-view function. That's used in source code engineering, and can be abused in other situations, it's great the way it is.
I'm also not proposing any changes to how the File list works. This is just a way of making it a little more user friendly.



There are two very similar metaconstraint relationships; «metarelationship» and «stereotyped relationship». In both of these, you must specify the metaclass / stereotype as free text.
This is stupid.

They should be selectable from dropdown lists or selector dialogs, as is the case when you create a new metaclass or add stereotypes to toolboxes using the profile helper.



I've been trying to create two element stereotypes in different profiles, with «trace» the only permitted connector between them. In the course of my heroic struggles I've come across a pretty massive inconsistency: metaclasses and stereotypes.

If you add a new metaclass to a profile diagram, EA pops the Extend Metaclass dialog. In this, Trace is listed as a Core Connector. So it's a metaclass.
So I should be able to specify "Trace" as the value in a «metarelationship» metaclass tag.

But no -- I have to use a «stereotyped relationship», which has a stereotype tag where I must specify "EAUML::trace". So Trace is a stereotype.

Going back to the Extend Metaclass dialog, trace is actually listed under EAUML in the Stereotypes tab.

So that's Metaclass 1, Stereotype 2. In the same dialog.

My humble suggestion: sort out once and for all which element / connector is actually a metaclass and which is a stereotype, and while you're at it, how about documenting which relationship needs to be specified with a «stereotyped relationship» and which with a «metarelationship»?



I've got an MDG Technology with two stereotypes between which I want to be able to draw «trace» and nothing else.
So I've set _HideUmlLinks, drawn a «stereotyped relationship», and added «trace» to the relevant toolbox.

This doesn't work.

When I try to draw a new connector using the quick linker, I get nothing. No popup menu, zip.
If I disable Filter to Toolbox, the popup menu appears and contains only Trace.

So even though I have added «trace» to the toolbox, it doesn't work with Filter to Toolbox enabled.

1) Can someone verify whether this is still the case in 15.1? I'm on 15.0 and there's nothing in the release notes.

2) Is there a way to get EA to do what the documentation and the support people say it's supposed to do?



Bugs and Issues / Cross-profile «stereotyped relationship»
« on: June 22, 2020, 10:15:59 pm »

I've got an MDG Technology with two profiles, where I want to allow «trace» connectors from a stereotype in one profile to a stereotype in the other. The way to allow «trace» is to use a «stereotyped relationship» connector, specifying EAUML::trace in the stereotype tag.

This doesn't work.

In the diagram for profile A, where stereotype S1 is defined, I add stereotype S2 from profile B and draw the connector between them. I then export the profiles using Publish Package [not diagram] as UML Profile.
B.xml has no mention of the relationship, as expected. In the <Stereotypes> section of A.xml I find
Code: [Select]
<Stereotype name="S1" ...>
<stereotypedrelationship stereotype="EAUML::trace" constraint="A::S2"/>

Note: constraint="A::S2". It should be "B::S2".

So the profile publishing function just assumes that the target of a «stereotyped relationship» is in the same profile as the source. It writes it into the XML file as a fully-qualified name, but it doesn't actually retrieve that fully-qualified name from the profile model -- it retrieves the simple name and tacks on the profile name itself.

If I manually correct the profile XML file, the resulting MDG Technology works as expected.


1) Can anyone check whether this error is still in 15.1? I'm on 15.0, and there's no mention of this in the release notes.

2) Does anyone know of a workaround so I don't have to edit the files?



Automation Interface, Add-Ins and Tools / webdoc wtf
« on: June 18, 2020, 11:38:02 pm »
Hi everybody,

I'm working on a profile where I want some artifact stereotypes for off-model documentation.

To this end I've created a stereotype webdoc. This has no shape script or anything, and I've got another couple stereotypes that work just fine.
But webdoc is rendered with an extra icon next to the artifact icon, looks like an old IE-style green globe thing.

Looking in the element's properties the webdoc stereotype comes from my profile and nowhere else.
I've got basically no other technologies enabled; I tried disabling even Basic UML2 and Core Extensions, but that icon is still there.
(Then I had to exit and start EA without opening a project and re-enable the core technologies but that's just because the MDG management thing is completely broken but that doesn't mean it needs fixing or anything so that's OK.)

I also grep'ed for "webdoc" in the installation's MDGTechnologies folder. Nothing.

What? I mean... what?



If you work really hard you can get EA to pop a message telling you the requested connector is not UML compliant.

With the introduction of metamodel constraints it would be helpful if, when a user tries to create a relationship that is not permitted by the constraints, EA popped a similar message but referring to the metamodel. More helpful still if it could specify which metamodel was prohibiting the relationship. (Technology I guess?)

"Relationship" refers to all types of relationship that can be specified with the metamodel constraints, not just connectors.


Automation Interface, Add-Ins and Tools / Trace in metarelationship
« on: June 18, 2020, 10:26:03 pm »
Hey guys,

I've got two abstract stereotypes between which I want to be able to draw a Trace relationship. What should I specify in the metarelationship metaclass tag?

I've tried Trace and TraceLink, but neither works.
The toolbox definitely includes a UML::TraceLink (initial value "Trace"), but the quick linker doesn't provide Trace as an option.



Suggestions and Requests / Connector layout: take type into account
« on: June 18, 2020, 09:44:29 pm »

If you create connectors of different types targetting the same element, one end decoration (arrow head) can obscure another. Same goes for the connector line itself; a solid line can obscure a dashed one. This becomes more of a problem when you use one of the more automatic line styles (anything but Custom Line, really).

So the proposal is: in a situation where two different connector end decorations need to be drawn in the same place (eg an open and a triangular arrow head), they should be moved with respect to one another so that both are visible.
Similarly, if two different connector line (segment)s need to be drawn on top of one another, they should be placed side by side instead.
Both of these would obviously affect other line segments as well.

This change would also need to take shape scripts into account. That might be too hard to do for the end decorations, but shouldn't be much of a hassle with the line segments.


Bugs and Issues / Provided/required interface classifiers
« on: June 16, 2020, 09:09:19 pm »
Hey everybody,

Um... In 15, how do you specify that a provided/required interface is an instance of an Interface element?

Ctrl-L doesn't pop a dialog and there's no menu item that leaps out. But there is Advanced -- Convert to Instance, implying that the provided/required interface is a classifier type.

What's going on?
Is it just me?

I could have sworn you used to be able to do this.
Aren't you supposed to?



Hey hackers,

DocumentGenerator.InsertHyperlink(), right?
"Inserts a hyperlink at the current location. If you use a URL with the  #BOOKMARKNAME syntax, the hyperlink will link to another part of the document."

I want to link to another part of the document.
My question is: how?
How, using DocumentGenerator, do I create the target for this hyperlink?
Not the link itself. The target. The place in the document that I want the link to point to. How do I create that?



Hello boys and girls,

Is there a way to open the template editor, preferably with a specific template, through the API?
Asking for a friend.



Pages: [1] 2 3 ... 27