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 - Paolo F Cantoni

Pages: 1 ... 4 5 [6] 7 8 ... 79
76
Automation Interface, Add-Ins and Tools / ProxyConnectors - where to store?
« on: September 18, 2017, 05:19:39 pm »
We have grouped all our elements by metatype into specific branches of our repository.  We have automation to move elements around between folders when EA or our users don't put them where we need them.

EA now has t_object entries of type ProxyConnector (actually ConnectorProxy).  These are related to the end of a relationship that is NOT an element.  That is for relationships from relationships to elements and relationships between relationships.

We have folders for those items that don't end up in the browser and we manage those in a similar way behind the scenes.

My question is, where should we place these Connector Proxies.  They are placed somewhat arbitrarily as far as we can make out.  We suspect we run the risk that if we purge a folder that doesn't appear to have any objects within it we will inadvertently purge any ProxyConnectors.

Should we place them in the same folder branch as the origin object of the relationship or with the destination object of the applicable relationship?  Does it matter?

Paolo

77
Bugs and Issues / Tooltips: Consistency of display
« on: September 11, 2017, 05:04:59 pm »
EA will generate tooltips for elements and also for relationships.

One shows Metatype then Stereotype, the other the reverse.  They should be the same.  My preference is for Metatype then Stereotype, but consistency is more important than order.

If Sparx is working in the area, it would be useful to (optionally) suppress stereotypes (since these days metatypes RULE OK!)

Reported,
Paolo

78
As we refine our relationship matrices, the semantics often changes.  Accordingly, the semantically correct name (as opposed to the original name) needs to track the changed semantics.  There appears to be NO mechanism (I stand to be corrected by "Sir Roy of the C") to change the name of the Matrix Profile after the initial save of the new profile.

Reported,
Paolo

79
If a Search is specified with an "&" in the Search name, it will display incorrectly in the Source/Target display boxes, but they do display correctly in Selection drop-down to pick them in the first place!

EAUI!

Reported,
Paolo

80
There is no context menu item to allow you to add a Matrix Profile in the Resources browser.

Reported,
Paolo

81
If a relationship element is in a subpackage, the package path precedes the element name on the Relationship Matrix.  It is also sorted by the complete string.  I have already requested that the package path be, optionally, supressed.  However, if not suppressed, there should be an option to sort by the name of the element, ignoring the path.

Reported,
Paolo

82
It would be useful if the "Source" and "Target" names could be replaced with meaningful names, specific to that Relationship Matrix.  They could then appear on the printout (where even the "Source" and "Target" values are suppressed).

Reported,
Paolo

83
Bugs and Issues / Relationship Matrix: Can't always delete relationship
« on: September 07, 2017, 05:32:53 pm »
It turns out that if the Direction is set to both, the delete relationship functionality is disabled.  At a minimum, this should be mentioned in the Help.  Better still, just as one can Add Source->Target or Target->Source, the appropriate cell contents should be available for deletion.

Reported,
Paolo

84
Am I correct in understanding that there is only one relationship matrix allowed at a time?

We're only just getting into relationship matrices and it might be useful to "flip between" different matrices as one does with diagrams.

Paolo

85
Bugs and Issues / Relationship Matrix: Can't add inverse relationship
« on: September 05, 2017, 05:26:05 pm »
I mentioned elsewhere that I get why the Relationship Matrix uses directionality rather than navigability.  When you have an empty cell, you can add either the Source->Target Relationship or the Target->Source relationship.  However, once a relationship is entered, you can't add the other (via the matrix) - in order to get it in, you have to go to a diagram and create it there.  The Relationship Matrix then shows the symbol for the inverse relationships.

Reported,
Paolo

86
When you save a Relationship Matrix to a CSV file the default file name is "*.CSV",  it would be more useful if the default were the "<profile name>.CSV".

Reported,
Paolo

87
We hold all out elements in special branches, away from the diagrams.  Since we have so many, we have multi-leveled alphabetic folders to group them in.  When we display them on the Relationship Matrix (and use the "Include ... Children" option), the path to the element is rendered.  While for many use cases, this is useful, it is particularly annoying for this one.  Please make the display of the path optional for both origin and destination.

Reported,
Paolo

88
Bugs and Issues / Relationship Matrix fails with "Information Items"
« on: August 31, 2017, 05:00:00 pm »
We have our own element metatype called "Information Item" according to the following (partial) MDG definition.
Code: [Select]
<Stereotype name="InfrmtnItm" metatype="Information Item" If we try to select it from the dropdown for the Element Type, EA helpfully (It's an ironic observation, Joyce) replaces  "Information Item" with "InformationItem".  Consequently, we can't use them in a Relationship Matrix.  Pure EAUI!

Needs to be fixed!

Reported,
Paolo

89
Virtualized Connector Ends (VCEs) now honour shapescripts.  BUT it doesn't seem to provide access to all the properties used by the shapescript.  We have a decoration that will provide an indicator that the Notes field for an element is empty.
Code: [Select]
if(hasproperty("notes","")) //Notes empty...
The base object responds correctly, but the VCE does not, it ALWAYS shows the notes as empty regardless of the actuality.

Reported,
Paolo

90
Bugs and Issues / Virtualized Connector End as Diagram Object
« on: August 30, 2017, 05:24:45 pm »
I've just reported another defect in the Virtualized Connector End functionality.  I did a search and found that the only posts that mention that functionality are mine!   ::)

In quickly reviewing them, and having used the functionality from time to time, I've come to the conclusion that a significant part of the problem with the shapes and connectors tot he virtualized connector end is that there is NO corresponding Diagram Object.

With automation, one can place MORE than one instance of an object on a diagram (and AFAIK the Consistency Checker accepts it).  I guess that, at present, EA synthesises a diagram object.  My suggestion why not make that item persistent?  It can be distinguished in some way from the Base diagram object and be referenced in the virtualized connector end.  This would, it seems to me, allow the full functionality of a REAL diagram object, without significantly deviating from the concept of a virtualized connector end.  Because the VCE diagram object can be distinguished from the base object, one can finesse any appropriate functionality through to the base object.

Thoughts?
Paolo

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