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 ... 15 16 [17] 18 19 ... 27
241
Suggestions and Requests / Linked Feature in tooltip
« on: October 29, 2013, 12:43:08 am »
Hi!

Link to Element Feature is a cool function which is occasionally extremely useful indeed. It may not (correct me if I'm wrong) be strictly UML compliant, but what's that between good friends eh?

One thing which would make it even more useful is if the linked feature, if any, were shown in the connector tooltip, which currently shows "A > B" for a connector from A to B. "A.attr > B.op" would be great.

Cheers,

/Uffe

242
Suggestions and Requests / Command Sets in MDG Technologies
« on: October 28, 2013, 07:20:10 pm »
Heeeey!

Command sets are really cool, but in order to realize their potential as a productivity enhancer we need to get them into MDG Technologies.

Nobody who runs a three-person programming/modelling team will care, but those of us who support hundreds of users including business analysts, project managers and other non-IT-nerd-type people will thank you forever.

Cheers,


/Uffe

243
Suggestions and Requests / Command Sets: Security override
« on: October 28, 2013, 07:16:00 pm »
Hi!


As noted in http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1382010385, it is quite possible to configure yourself into a corner by selecting the wrong command set: pick one that doesn't include Security, log into a security-enabled project, and you're stuck.

Would it be possible to override the command set and enable the security commands if the project has security enabled?

It shouldn't be a problem from the data integrity perspective: it will still be the user's permissions which determine whether or not they can actually unlock stuff.

Cheers,


/Uffe

244
Suggestions and Requests / Request: "Unlock" button in Properties dialog
« on: August 06, 2013, 12:25:03 am »
Hey hi,

Just what it sounds like - a button to unlock the current element. There's plenty of space in the dialog, and it's annoying to have to close the dialog, right-click and select Apply Lock, then open the dialog and find the right tab again.
Could even be a Lock/Unlock toggle.

/Uffe

245
Suggestions and Requests / Traceability: hide backwards link
« on: May 24, 2013, 04:19:45 pm »
Hi all,

When you're traversing a model structure using the Traceability window, you get something like this:
Code: [Select]
A
    links to
        B
            links from
                A
You can't expand the inner "A" node, since that would lead to a loop in the tree.

I'd like an option to hide backwards links, so that the inner "A" node would not be shown. If that would turn the "links from" node into a leaf, that node should be hidden too.

Sound good?

Cheers,


/Uffe

246
Hi!

The specific types of connectors aren't shown in the Traceability window. This means dependency-based connectors get lumped together as "depends on / needed by" and association-based ones become "links to / links from."

Having the option to display connector stereotypes would help a LOT. The name could be useful too, as could source/target roles and guards, but the stereotype is the important one.

In this example, A has a normal dependency to B and a trace to C:
Code: [Select]
A
    depends on
        B
        C («trace»)

Of course, it would also be nice to be able to separate the link nodes based on stereotype. We'd then get something like:
Code: [Select]
A
    depends on
        B
    depends on («trace»)
        C
But that's a change in how the window works and I'm sure not everyone would agree with me on that one.

But I am absolutely positive that everyone in the entire wide world agrees with the first suggestion.

Right?


/Uffe

247
Suggestions and Requests / Traceability: show stereotypes
« on: May 25, 2012, 10:42:25 pm »
Hi!

The traceability window is a very handy little tool but it uses its own connector labels, which can be confusing and sometimes downright misleading.

Consider for instance two components, where one has a «use» and the other an «abstraction» connector to the same interface.
Both these relationships will be reported as "needed by", since they are stereotyped dependencies. In the «use» case this might be permissible, but «abstraction» is quite a different kettle of barramundi.

This would be resolved if the connector stereotypes were shown, as in "needed by («use»)" and "needed by («abstraction»)". This solution will also work for third-party profiles, which an effort to come up with separate descriptions for all UML connector types would not.

Any takers?

Cheers,


/Uffe

248
Suggestions and Requests / Link Note to connector note
« on: May 05, 2012, 12:58:04 am »
Hey hi ho,

I can create a Note and link it to an Element Note.
I can create a Note and link it to a Connector Tag.
Is there a particular reason why I can't create a Note and link it to a Connector Note?

Only it'd be really really useful.
As I'm sure you'll all agree....... Right? :)


/Uffe

249
Suggestions and Requests / Float diagrams from project browser
« on: March 30, 2012, 04:55:05 pm »
Hi all,


With today's panta rei EA it'd be really nice to be able to open a new floating diagram directly from the project browser with drag-and-drop.

The scenario is this:
I've got the project browser floating on its own, with the EA main window somewhere on a different screen. I want to open a diagram, so I double-click it.
The diagram opens, but in the main window. I have to find that and drag the diagram off from there to get it to where I'm working.

What I'd like is to be able to drag the diagram off the project browser, drop it on the desktop and have it float there - same as the behaviour when dragging it from the main window diagram area.

Any takers?

Cheers,


/Uffe

250
Suggestions and Requests / Project name in floating windows
« on: March 30, 2012, 04:59:43 pm »
Helluuurrrr,

If you're combining floating windows with multiple EA sessions you get headaches, especially if you don't have enough 30" screens.

Could we get an option to display the EA project name in the title bars of floating windows? Exactly the same as in the main window, in other words.

Who's with me?


/Uffe

251
... please?

/Uffe

252
Suggestions and Requests / Separate toolbars for floating diagrams
« on: March 13, 2012, 01:45:34 am »
Hi all,

It would be really useful if the diagram toolbar (not the toolbox) could be included in each floating diagram.
At present, you have to click inside the diagram to give it focus and then click the toolbar button, which may be far away on the desktop.

An option in the Customize menu to control whether the diagram toolbar should be per-diagram or not would be acceptable, but I'd be just as happy with having the toolbar moved to the individual diagrams.

Thoughts?


/Uffe

253
Suggestions and Requests / Request: EA_OnPreChange events
« on: January 13, 2012, 03:16:00 am »
Hi!

In an Add-In, to stop the modeller from modelling incorrectly, you can catch EA_OnPreNew and EA_OnPreDelete events.
At the moment, however, there are no EA_OnPreChange events. These are also needed if the Add-In is to have a fighting chance to maintain model integrity.

Looking at the existing EA_OnPre events, I would rank the change events in order of priority thus:
EA_OnPreChangeElement
EA_OnPreChangeConnector
EA_OnPreChangePackage
EA_OnPreChangeAttribute
EA_OnPreChangeMethod
EA_OnPreChangeDiagram
EA_OnPreChangeDiagramObject
EA_OnPreChangeGlossaryTerm

Anyone else?

Cheers,


/Uffe

254
Suggestions and Requests / Diagram / Baseline Compare: Connectors
« on: January 05, 2012, 01:39:57 am »
Hey hi there,

The new diagram / baseline compare is beautiful, but it only shows changes to elements.
I would like to be able to see changes to connectors as well; added, removed and rerouted.

Anyone else?

Cheers,

/Uffe

255
Hello everybody,


When working with a Project Glossary I come up against a limitation which I find a little bit annoying: I can't create two entries for the same term.
This is by design: the term is highlighted whenever it appears in a Note, and Ctrl-click takes you to its definition. Fine so far - except sometimes you would like to create alternative definitions for the same term, if for instance you are working with several disciplines (eg analysis and design) in the same project.

Each glossary entry has a Type, which could be used to achieve this. However, the type column in the t_glossary table is non-key.
If the type column was instead made key, the unique identifier would be the combination of term and type.
This would require some behaviour changes when there was an ambiguous definition: EA would have to indicate this in the tooltip, and the Ctrl-click would need to show a list of possible definitions.

I think it would be worth it in larger projects, and I don't think it would negatively affect current usage as a single-definition term would continue to evoke the same EA behaviour.

Comments?


Cheers,

/Uffe

Pages: 1 ... 15 16 [17] 18 19 ... 27