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 ... 18 19 [20] 21 22 ... 30
286
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

287
Suggestions and Requests / Search results to diagram
« on: January 05, 2012, 01:51:15 am »
Hi again!


This would be very useful in many situations:
Add to the Model Search result context menu "Add Selected to Diagram."
This would bring up a browser, allowing you to select an existing diagram, or specify a location and a diagram type for EA to create a new one.

EA would then add all selected search results to the diagram.
Availability should follow the same rules as the Find menu items, ie it should be available when EA can determine the element type and identity.

Whacha think - useful?


Cheers,

/Uffe

288
Suggestions and Requests / Project Hyperlinks
« on: January 04, 2012, 08:29:27 pm »
Hey guys,


Well maybe I'm a complete idiot, but:

In medium-to-large EA deployments I usually recommend my clients to set up links between related projects, and typically to establish one central project whose sole purpose is to link to all the others (kind of like a home page).

The way we do this is by creating Hyperlinks to files which are .EAP shortcuts (which in turn are simply text files containing an EAConnectString).
The problem with these is that they only work if you have access to the file (server) where they are located, which in larger installations is not always the case even if you have access to the database holding the project. Think WANs, think intranets, think external consultants, you know the tune.

Now you can also create an EA Command Hyperlink which holds a FileOpen command - but that only pops up the Open dialog, it doesn't allow you to specify an EAConnectString.

That, simply put, is what I would like: the ability to create EAConnectString hyperlinks.
They should ideally be proper model elements rather than just diagram objects, like linked documents, but I'll take them as Hyperlinks if that's all I can get.  ;)

Or am I in fact an idiot and is there already a simple, one-click procedure to achieve this without going through an external file?

Cheers,


/Uffe

289
Suggestions and Requests / Diagram Filters: Filter on Tagged Value
« on: April 07, 2010, 07:29:36 pm »
Hi!


Diagram Filters - sooo cool!

Now can I get the option to filter based on tag and value please?
Ie, tag named X contains/equals/etc value Y.
I'd accept a "hacky" way of entering it into the Diagram Filter dialog, eg "NAME=X,VAL=Y" in the dialog's Value column. Initially. ;)

I would also like filters for
  • Lock Status (Locked/Unlocked; disabled if security not enabled)
  • Baseline Version (contains/equals/etc)
  • Version Control Status (controlled/not controlled/checked-in/etc
Thanks!


/Uffe

290
Suggestions and Requests / Search Results to Excel
« on: April 27, 2010, 05:51:55 pm »
Hi!

I'd like the option of shifting the results of a Model Search to Excel, either by exporting them as a CSV file, or by copying them into the clipboard in CSV format.

Cheers,

/Uffe

291
Suggestions and Requests / Edit: Copy Name
« on: April 09, 2010, 06:16:27 pm »
Hi!


I'd like an item added to the Edit Menu: Copy Name. This copies the name of the selected element (or connector, or feature) into the clipboard.
Normally, you can do this by F2 - Ctrl-C - Esc (edit name, copy, cancel edit); however, if the element is locked editing is prohibited.

And please don't tell me not to use such long element names that I can't type them in somewhere else. *I* know that. It's these other bozos... ;D

Cheers,


/Uffe

292
Suggestions and Requests / New Baseline: Set Package Version
« on: April 09, 2010, 06:36:37 pm »
Hi!


When I create a new Baseline, I would really really REALLY like the option of automatically setting the package's Version to whatever version identity I select for the new baseline.

Cheers,


/Uffe

293
Suggestions and Requests / Diagram: Find in Project Browser
« on: April 09, 2010, 05:54:09 pm »
Hi!


I can select an element in a diagram and via its context menu (or by pressing Alt-G) Find it in the Project Browser.
I'd like to be able to do that with the diagram itself, through its context menu or by pressing Alt-G when nothing in the diagram is selected.
Helpful when modelling in several different branches of a large model. Plus it'd take you guys like five minutes to implement. :)

Cheers,


/Uffe

294
Suggestions and Requests / Feature Visibility: Version
« on: March 29, 2010, 07:01:19 pm »
Hi!


I'd really like to see the option of switching on a "Version" compartment for elements in diagrams. Or perhaps even "Details," which would show version and author (similar to Diagram Details).

Cheers,


/Uffe

295
Suggestions and Requests / GUI Feature: Select Connected
« on: March 18, 2010, 08:37:43 pm »
Hi!

Here's a GUI feature I'd like: select one or more elements in a diagram, right-click, choose "Select Connected."
This causes the GUI to add to the current selection all (previously non-selected) elements in the diagram which are connected to one of the elements in the original selection.
Great for moving things around in a complex diagram with hand-drawn layout.
Cheers,

/Uffe

296
Suggestions and Requests / Code Template Framework: add @sort to %list%
« on: December 09, 2009, 07:44:01 pm »
Hi!


The code generation control macro %list% could use a @sort argument. Things often need to appear in a resulting file in a strict order, defined by the contents of the elements.

The argument should be the name of a macro to be applied in context when the %list% is executed. Examples:
%list="Class" @sort="className"%
%list="Operation" @sort="opAlias"%
%list="Attribute" @sort="attInitial"%
%list="Namespace" @sort="packageTag:%qt%MyTag%qt%"%

It should also be possible to specify a reverse sort by adding an additional argument @reverse="True".

Not specifying a @sort argument results in the model default order (which can still be reversed).

This functionality would be immensely useful for some of the stuff we do over here.

Cheers,


/Uffe

297
Suggestions and Requests / Model Transform: Optional Diagram Creation
« on: November 18, 2009, 07:02:12 pm »
Hi!


I work with MDA Transforms a lot, and while the auto-generated diagrams are often useful, other times they are not.

Since diagram creation and layout accounts for a significant proportion of resource usage during a transform, I'd like a "Create Logical Diagrams" tickbox in the Model Transformation dialog.

Cheers,


/Uffe

298
Suggestions and Requests / Element Properties: Link End
« on: August 19, 2009, 10:16:40 pm »
Hi!

The Link tab of the Properties dialog could do with an indication of which end of the link the element is at, source or target.

/Uffe

299
Hi!


The Code Template Framework allows access to Class constraints only, but Attributes, Connectors and Packages can all have constraints too.

I suggest the following:
  • Rename the macros constraint* -> classConstraint*
  • Add attConstraint*
  • Add connectorConstraint*
  • Add packageConstraint*
  • Remove connectorSourceConstraint and connectorDestConstraint (connectorSourceElem* and connectorDestElem* should take care of those)
To me personally, the attConstraint* ones are the highest priority.

Cheers,


/Uffe

300
Suggestions and Requests / Package: Set As Namespace Leaf
« on: August 06, 2009, 06:08:23 pm »
Hi!


This feature is intended to improve the display of foreign elements (ie elements from a different package) in a diagram, primarily within large models with recurring package structures.


Let's say you have a model along these lines:
+-- Software Modules
|   +-- Blarg (*)
|   |   +-- Actors
|   |   +-- Use Cases
|   +-- Honk (*)
|   |   +-- Actors
|   |   +-- Use Cases

Ignore the (*) for now.
Let's say in one of my Honk use cases I wish to include a use case from Blarg.
When presented in Honk's diagram, this use case will be labelled "(From Use Cases)".
Since I am using a recurring package structure, this label isn't very helpful: EA displays only the immediate parent package of the foreign element, and that package name occurs in dozens or hundreds of different software modules.

I propose adding an option "Set As Namespace Leaf" to a package. In the structure above, assume I have applied this flag to the (*) packages.

When displaying a use case symbol from Blarg - Use Cases in a diagram in Honk - Use Cases, EA would then label it "(From Blarg)".
In other words, EA searches upwards in the package hierarchy and uses the name of the first package it finds with the "Namespace Leaf" flag set.
If the search hits the root node with no "Namespace Leaf" package found, EA uses the name of the element's immediate parent package (ie today's behaviour).
 
In a use case diagram in Honk - Use Cases, an actor from Honk - Use Cases should be labelled "(From Actors)".
This is achieved by EA performing the "Namespace Leaf" package search twice, once from the element and once from the diagram.
If the first hit in both searches is the same package, ie the element and diagram have the same nearest "Namespace Leaf" package, the immediate parent package name is displayed (again, as today).

This way, Honk actors will be labelled "(From Actors)" in the Honk use case diagrams.
In the same Honk use case diagrams, use cases from Blarg - Use Cases will be labelled "(From Blarg)".
Let's say that one of my Honk actors generalizes a Blarg actor. In the Honk actor diagram the Blarg actor will be labelled "(From Blarg"), while in a Blarg use case diagram, the same actor will be labelled "(From Actors)".

The package symbol in the project browser should be different when the package is a "Namespace Leaf."
Finally, "Namespace Root" is a code engineering concept, while "Namespace Leaf" is a purely visual one. Therefore the option shouldn't go in the same place as "Set As Namespace Root," and perhaps the name "Namespace Leaf" is a bad one.


Cheers,


/Uffe

Pages: 1 ... 18 19 [20] 21 22 ... 30