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 ... 4 5 [6] 7 8 ... 18
Suggestions and Requests / Improvements to navigation by first letter
« on: January 21, 2016, 01:27:53 am »
Hi all,

In the project browser, and various treeview-style dialogs, you can search for / jump to the next item which begins with the letter 'X' by hitting the 'X' key on your keyboard. Very useful.

But if an element which begins with 'X' happens to have a stereotype, it is missed in the search. You jump right past it. So I think stereotypes should be ignored when jumping this way.

Secondly, instance elements without names should be jumped to as if they had the name of their classifier. In other words, an object ': X' should be jumped to if I hit the 'X' key. With the current function, only the actual name is considered.

Actually, you can jump to instances by hitting ':', which causes me to believe that the same would hold true if there was a '' key I could hit: that would take me to the next stereotyped element. In other words, the function considers the displayed string exactly as it appears.

But in these cases, both ':' and '' are parts of the UML syntax, not part of the items' names, and should therefore not be considered.

This would be a small but substantial GUI improvement.



Hi all,

When using Insert Related Elements, association classes are excluded. The association connector and the element at the other end are included just fine, but the association class doesn't appear.

There should be a checkbox "Include association classes" to control this. Plenty of space between the Clear and Refresh buttons.

In addition to being included in the diagram when the appropriate associations are selected, association classes can themselves have connectors, so they should be included in the search for related elements if the box is ticked.



Suggestions and Requests / Locale-based sorting
« on: October 12, 2015, 09:11:07 pm »
Hi all,

Unicode support is coming along and that's nice. So let's make it even nicer and add locale support too.

A problem with the Unicode table is that outside of the 26 characters of the rather impoverished English alphabet, the characters have just been dumped in likely-looking piles. And fair enough, really, because the additional characters are treated differently in different languages; sometimes they're proper letters in their own right, sometimes they're just diacritic variations.

But that should be taken into consideration when sorting things in EA's project browser, search results, etc. Right now, everything's sorted in Unicode order, and that's not the same as alphabetical order which is what people expect.

There are two issues here. The first is that letters with diacritical marks (accents etc) should be sorted with the unmarked letters. Right now, they all end up after Z because that's where they are in the Unicode table.

The other is that proper letters should be sorted into their correct alphabetical positions.

Scandinavian languages have more letters than English, appearing at the end of the alphabet. These are proper letters, not umlauts as in German. There are two main Scandinavian alphabets, Danish/Norwegian and Swedish, and just for fun, the characters are not identical in the two, nor are they sorted in the same order.

The Danish/Norwegian alphabet ends with Z , the Swedish with Z . EA will sort everything by Univode number, and the following table shows you how that clashes with expectations.

With Finnish I'm not entirely sure, but I think you can treat it the same as Swedish. "" (197/229) isn't part of Finnish proper, but there is a Swedish-speaking minority in Finland and Swedish is an official language there.

So what it all boils down to is that the same Unicode character has different meanings in different locales (in some a proper letter with its own alphabetical position, and in others a mere diacritic variation), and the sorting should take that into consideration. The current implementation is simple enough, but not good enough.

I'm sure you'll be pleased to know that Unicode recently published the 32nd revision to its Unicode Collation Algorithm. So if EA simply implements that, we should be OK. :)


Hey hey!

Hedging my bets in case no one likes my relevant-glossary idea. :)

When using the DocumentGenerator, it would be very useful if the various methods would return not booleans (worked / didn't work) but collections containing the package and object IDs for which templates were called, ie every package and object whose IDs were in context as #PACKAGEID# / #OBJECTID# during the generation.

Since templates can call other templates, and follow all sorts of relationships in addition to the package / element hierarchy, this information is non-trivial to retrieve beforehand, but should be easy-peasy to pick up as the generator goes along.

Ideally, the templates that were used should be indicated as well.



Suggestions and Requests / Document generation: relevant glossary
« on: June 02, 2015, 01:26:05 am »

It would be useful to be able to specify, either in a template or with a an option in the document generation dialog, that any model glossary section should contain only those terms that are used in the document.

By "used in document" I mean those terms that are present in any Notes fields that gets output (ie same rules that govern the highlighting).

This is essentially what's being requested in

I'd be perfectly satisfied if the solution only worked when placing the glossary in an appendix.



Suggestions and Requests / Repository hyperlinks
« on: January 08, 2015, 02:47:33 am »

I'd like to be able to create repository hyperlinks. This would be another type of hyperlink in addition to the current ones, with the following particulars:
  • The hyperlink contains a connection string, similar to the contents of a "shortcut" .EAP file.
  • Double-clicking the hyperlink closes the current project, then opens the specified repository. In other words, the current session is replaced and no new EA instance is started. (If you want to get fancy, the current project should only be closed after the linked project has been successfully opened.)
  • It should also be possible to open the linked repository in a new instance instead of closing the current project, perhaps by middle-clicking or selecting a context menu item.
You can almost achieve this today using a File hyperlink to a shortcut .EAP file, but following the link forces the creation of a new EA instance and that's what I want to avoid.
The use case for this new hyperlink type is mid-to-large deployments with a mid-to-large number of repositories. These links would allow for more convenient navigation between repositories.



Suggestions and Requests / Diagram: duplicate layout
« on: December 16, 2013, 11:41:55 pm »

Here's a nifty little feature suggestion for you: duplicate diagram layout.
When invoked, this opens up a selector dialog that allows you to select a diagram.
It then runs through the current diagram and, for each element and connector that is present in both the current and the selected diagram, copies the layout.

Useful in situations where you want to show a subset (possibly annotated) of a diagram.
Yes, a selective copy/paste will do this - but only once. This feature would allow you to copy the layout at a later date, after the original diagram has changed.


Suggestions and Requests / Connector: Locate Source/Target
« on: December 18, 2013, 07:33:31 pm »

Finding your way around large or complicated diagrams can be tricky.
A helpful tool would be a popup menu item (well, two really) on connectors allowing you to Locate Source/Target. This would select the source/target element in the diagram and, if it is off-screen, recenter the diagram on it.



Suggestions and Requests / Attribute Length / Precision & Scale in the GUI
« on: November 16, 2013, 12:44:02 am »
Hey hey hey,

Defining your own language and primitive datatypes allows you to specify size properties, either Length or Precision & Scale.
But they're absent from the attribute properties dialog, and they're not shown in diagrams. Unless you're dealing with a database table / columns.

However, plenty of languages include a decimal type, and fixed-length strings, well fuggeddaboudit.

So how's about adding Length / Precision & Scale to the element properties dialog (Detail page, there's space) and show them in the diagrams as well?

They should only be enabled / shown when the datatype has the corresponding size property, of course.



Suggestions and Requests / Add-In commands in toolbar
« on: December 17, 2013, 03:47:06 am »
In Tools - Customize, you can add a new toolbar and drop commands into it. Cool.

I'd like an AddIn-specific toolbar, in one of two ways. Either

1) Add to the Commands - Categories list the currently loaded Add-Ins, and for each such category add its currently available menu items to the Commands list, then automatically enable/disable the toolbar when the corresponding Add-In is enabled/disabled using some black magic, or

2) Add a new profile category "toolbar" to the MDG Technology thingy, which lets the MDG Technician specify an icon, a tooltip and an Add-In function to be called using some other black magic. Just simple buttons, no fancy dropdowns or such.

Actually, the second one doesn't sound all that black now that I think about it. It's pretty much on a par with the rest of the MDG Techsorcery.

What do you other high priests of the dark MDG circle say?

Suggestions and Requests / Skip GUI customization on first start
« on: November 27, 2013, 07:03:12 pm »
Hi all,

The first time EA is started, before you get to pick a project, it invites you to customize the GUI.
While well-intentioned, this actually tends to cause newbies more problems than it solves because they'll pick something that sounds simple and then poof, something they need is missing from the menus and there is not hint as to why.
We've seen several posts on this forum related to this issue, and for someone in my role (providing support to a large organization) it's something that has to be dealt with every time there's a batch of new users (yes the information is on the Intranet but who has time to read that? I wanna get stuck in!)

SO - I suggest you skip the first-start non-optional GUI customization popup, and replace it with a prominent button on the start page.

This way, new users will still get the option very quickly, but they will at least have a chance to look at the GUI they're customizing first.



Suggestions and Requests / Unlock button in Select <Item> dialog
« on: November 22, 2013, 09:04:32 pm »
Hi there!

The Select <Item> dialog, aka Construct Picker in the API, allows you to select a specific type/stereotype element or create a new one.

What it doesn't do is allow you to lock the package you need in order to create the element in the right place. If you try and the package is locked, EA flashes a "You do not have the required permissions to perform this operation" message.

So, either a button to unlock (there's space) or an option to unlock from the message box would be nice.



Suggestions and Requests / Model Validation: Fix
« on: November 14, 2013, 09:17:51 pm »
Hej hullo hi,

An option to right-click a model validation output line and select Fix would be very useful for easily-remedied validation failures.

This could be implemented as a set of broadcasts similar to EA_OnRun*Rule(), except they would include the identity of the rule which triggered the output, and return a boolean stating whether or not a fix was applied.

For extra brownie points, a Suggest option could also be included, which would trigger a similar broadcast which would return a string with the suggested fix, which EA would then display in a dialog along with buttons to Apply and Skip.



Suggestions and Requests / Hierararchical Manage Locks for the love of...
« on: October 24, 2013, 05:48:43 pm »

- EA Support, Uffe.
- Yes, hello, so-and-so is off sick today. Could you unlock such-and-such a package?
- I can release all so-and-so's locks, is that OK?
- No, just package such-and-such please.
- OK, give me a couple of hours.

Could we please get either a tree view in the Manage Locks dialog, or a button Unlock Recursive, or a pop-up "Do you wish to unlock child elements as well?"

I mean OK, fine, I'm a consultant, I get paid by the hour. But I'd rather be developing custom profiles or a cool Add-In than unravelling a flattened-out package hierarchy to unlock stuff selectively.
Hell, I'd rather be battling with the RTF template editor...!

Suggestions and Requests / Custom metatypes in Audit Settings
« on: November 13, 2013, 10:21:05 pm »

It would be very helpful to be able to select custom (MDG) metatypes in addition to the standard UML ones in the Audit Settings - Audit Options - Customize - Types dialog.

This way, you could choose to audit changes to classes in, say, a domain model without drowning in changes to implementation classes, or system-level but not subsystem-level use cases.



Pages: 1 ... 4 5 [6] 7 8 ... 18