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 ... 60 61 [62] 63 64 ... 79
916
Bugs and Issues / Drag Element from Browser - Actions
« on: October 07, 2009, 04:53:59 pm »
As per the discussion in: BUG: Element Usage:

The dialog exposed when dragging an element from the browser onto a diagram needs to be refactored.

The choices should read:
(*) As Element
(  ) As Instance (Object)
(  ) As Specialization (Child)

To better indicate what is happening.

However, note the discussion regarding the implementation of Instances.  Sparx have not yet indicated whether Objects will be the SOLE mechanism for creating Instances of Classifiers.  (See previous bug reports)

In addition, note the appropriate changes required when activities are involved (as per previous bug reports)

The Element Usage dialog can then be made to conform with:
As Element and As Classifier.

Reported,
Paolo

917
Bugs and Issues / Linked Requirements are Realized Requirements
« on: October 06, 2009, 07:33:53 pm »
Since the ONLY linked requirements displayed in the Rule & Scenarios [Ctrl+Shift+3]  window are realized requirements, the folder named: Linked Requirements should be renamed appropriately:

Realized Requrements

Reported,
Paolo

918
Bugs and Issues / Object State doesn't wrap
« on: October 05, 2009, 03:10:28 pm »
Before I report this as a bug, I thought I'd canvas views.

The Object State field of the Object will not wrap on a diagram - regardless of the Set Feature Visibility... [Ctrl+Shift+Y] settings.

I think it should wrap.  Do others?

Thoughts? Votes?
Paolo

919
Bugs and Issues / Actions CAN/CAN'T have diagrams
« on: October 02, 2009, 08:16:28 pm »
I SWEAR I did NOT set this up before reviving the topic End Composite/Linked Diagram conflation.

You can create a linked diagram for an Action by using the <context menu>|Advanced>
  • Composite[/b] - so far so good.  However, I wanted to add another diagram under the Action (and link it to the first via a hyperlink).  So I go to the browser and find there's NO <context menu>|Add>Add Diagram...  menu item forf the action.

    So an Action can and can't have diagrams.

    If there's ONE UML element which CAN'T be a composite since (at least in my interpretation of the UML specification) it's an atomic only element it's an Action!

    I had to go to an activity, create the diagram then drag it down to the action...  "Not Happy, Jan!" (Reference to a famous Aussie commercial for "Yellow Pages")

    Actions need the ability to have added diagrams (in the browser).

    Reported,
    Paolo

920
Bugs and Issues / End Composite/Linked Diagram conflation
« on: October 01, 2009, 10:07:46 pm »
The time has come to finally end the Composite Structure/Linked Diagram conflation in EA.

Whether an item is an aggregate (Note: NOT just a Composite) is either a derived property (as a result of metadata in the model) or an asserted property (by the modeller - in anticipation of creating the requisite metadata in the model).

It has NOTHING to do with whether I have attached one (or more) diagrams to the item.  However, since the ONLY way to attached a diagram to an item is to mark it as composite, there's no way to distinguish the real aggregated items from the "Clayton's" ones (search the forum for the meaning  of Clayton's).

I propose the existing "composite" functionality be renamed "Link to Diagram" (and a dialog be created to locate/create the diagram).

From what I recall, the existing functionality doesn't actually mention the word composite in its implementation and there is  more than one way to specify the attached diagram (depending on the element type).

EA has already started using a normalised process for linked diagram specification (using the "Default Diagram" t_xref entry for this purpose).

So why not cut the Gordian Knot and do it properly?

Additional functionality can then be created to allow the user to assert whether the item is an Aggregate (either Composite or Shared) and that metadata be stored and rendered (preferable on the item properties dialog) separately from the diagram linkage.

Reported
Thoughts? Votes?

921
Bugs and Issues / HTML Report - more than one!
« on: October 01, 2009, 05:55:13 pm »
The HTML report specification is NOT even specific to a repository!  It's common to the machine!

With the New? (I only just "stumbled across it") Locate page by GUID functionality (look it up in the Help file under that topic) I can finally see the ability to effectively split up (what used to be a) single humongous web report into a series of related ones with linkages between them.

I'm making an assumption that I can create a hyperlink in one diagram that points to a diagram in another website (knowing the GUID) I've yet to test it out - but even if it doesn't work, it seem to me it should, so I'll report a bug.

This then leads to the requirement that a single repository may generate multiple HTML reports for different purposes.  (We already do this now, but they aren't linked such as I'm proposing.)

As we move to more enterprise scale modelling, this scenario seems increasingly likely.

My suggestion is to create an new folder in the Resources Window (named either Web Sites or HTML Reports) into which to place the specifications - similar to the RTF Document specifications therein.

Thoughts? Votes?
Submitted.

Paolo

922
Bugs and Issues / MTS Wizard should be "Sticky"
« on: October 01, 2009, 04:54:15 pm »
The MTS generation wizard should be more "sticky" - at least on a per session basis.

It should remember if you are using an MTS file or not.  If you are, it should remember the last one you used (ESPECIALLY if there's ONLY one specified!)

Lastly, as I use the Wizard, I find I'm 99% of the time pressing Next>Next>Next>Finish.  Most wizards of this type have an early Finish button - enabled after the first run of the wizard - once the values are set up.

As I'm developing the MTS technology, I sometimes go through this process several times an hour.  The clicks (and time) add up.

Reported,
Paolo

923
Bugs and Issues / FEATURE: New Dialogs - resizable and sticky
« on: October 01, 2009, 04:45:55 pm »
Some of the new dialogs (Such as Select Classifier [Ctrl+L]) are now resizable and sticky - even between sessions!   This means I can locate and size them conveniently for my particular layout.

(I presume their size and location is on a per-layout basis - can anyone [Spaxians?] confirm?)

A great improvement and makes EA easier to use...  Especially in my case as I'm doing a lot of Instance Modelling

So instead of my usual grumbles - A BIG plaudit to the Sparxians!

Well Done!

Perhaps if we users can help Sparx by finding more of these dialogs that need to be resizable, we can help them to help us...

Paolo

924
Bugs and Issues / Select Classifier includes Instances
« on: October 01, 2009, 04:10:43 pm »
As part of the Redesign for the management of Instances within EA, Sparx will need to consider the Select Classifier [Ctrl+L] dialog.  At present it also allows instances of the various types to be selected.   That is, if I "convert" an actor to an instance, I get an Actor instance.  But that Actor instance is listed in the Select Classifier dialog.

My guess is that the code is not filtering on the existence of the ClassifierID or GUID in the t_object row.

Reported,
Paolo

925
Bugs and Issues / Immovable versus Unselectable
« on: October 01, 2009, 03:51:00 pm »
EA has conflated the two concepts so that in order to make a diagram element immovable you need to make it unselectable.

I think the two concepts need to be separate but linked.

A diagram element if selectable should be designated immovable.  A diagram element designated as non-selectable is (by definition) immovable.

When you move an item, the diagram is designated as dirty.   Also, when you navigate using double-click you can accidentally move the item.  Associated relationships can get out of alignment etc..

We're going to be experimenting with letting end users loose on EA Lite diagrams so being able to "fix" them in place would be very useful.

Also, I thnk this concept should apply to lines as well as shapes.

Before I submit a Bug/Feature request...

Thoughts?  Votes?
Paolo

926
Bugs and Issues / Line Routing versus Styling versus Patterning
« on: October 01, 2009, 12:07:40 pm »
EA has a problem with the word style when applied to lines...

It uses it to mean BOTH the routing of the line <Line context menu>| Line Style> and for the pattern of the line in shape scripts setlinestyle(pattern);

In addition the other various appearance attributes line thickness, colour etc are aggregated together and can be specified as a "style"  Format Bar|Save as New style

Could I suggest that this conflation start to be sorted out.

It seems to me that a line style is an aggregation of:
  • Line Pattern (solid, dash, etc)
  • Line Thickness
  • Line Colour
  • Line Routing (direct, autolayout, tree etc)
[Edit: and that EA should start to standardise on such terminology.  I have already posted on the desirability of having style names more generally applicable.

Have I forgotten any other attributes that should also be aggregated into the style?

Thoughts? Votes?
Paolo

927
Bugs and Issues / Save as Profile... File Info needs to be
« on: September 25, 2009, 05:05:17 pm »
Each diagram is used to save to a different profile, but the profile dialog doesn't save the profile file with the diagram.  You, too, can overwrite one profile file with the contents destined for another.

Then you can wonder why your MTS file doesn't work...

The HTMLPath column in t_diagram seems to be unused... (hint, hint)

Reported,
Paolo

928
Bugs and Issues / QL: Actors & Objects
« on: September 30, 2009, 01:38:21 pm »
Has anyone been able to create a QuickLinker definition to go between Actors and Objects (and/or vice versa)?

I've been building a QuickLinker definition file connecting all sorts of elements to all sorts of other elements - all good until this morning when I tried to add some links between Actors and Objects (specifically ObjectFlows and Dependencies).  QuickLinker just seems to ignore these definitions.

I've got definitions between Objects and non-Actors and Actors and non-Objects that are working fine. It's just this combination that seems (that word again) inconsistent.

TIA,
Paolo

929
Bugs and Issues / New Tagged Value dialog - EAUI
« on: September 22, 2009, 02:23:02 pm »
The "New Tagged Value" dialog allows you to set the value of the tagged value - unless it's a predefined Tagged Value Type (in Settings|UML...|Tagged Value Types) and it has an entry in the Details field, in which case it's disabled (greyed out).  You have to exit the dialog and reselect the tag from the list and THEN you can set the value according to the rules.

EA should provide the same control in the dialog as is present in the list.  The additional mouse/key clicks add up!  Not to mention the inconsistency....

Reported,
Paolo

[EDIT: Oh, BTW, if the details specifies a Default value; the disabled control is populated with the default - but with NO way to change it within the dialog.  That's not my definition of default value.]

930
Bugs and Issues / Tagged Value Types - default values
« on: September 20, 2009, 02:10:32 pm »
Some Tagged Value types (such as Enum) have the ability to specify default values.

I guess all Tagged Values Types are equal, but some are more equal than others...  ;)

ALL Tagged Value Types should have the ability to specify a default value.

Reported,
Paolo

Pages: 1 ... 60 61 [62] 63 64 ... 79