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.

Messages - fwoolz

Pages: 1 ... 3 4 [5] 6 7 ... 29
Suggestions and Requests / Re: "Nesting" Compartment
« on: August 11, 2009, 07:29:28 am »
Two thumbs up!!  :D

Suggestions and Requests / Run scripts from context menu
« on: May 27, 2009, 04:53:41 am »
I have recently written several scripts in EA that work with the current context object (via the GetContextObject, GetTreeSelectedPackage methods), and it struck me that EA doesn't seem to have an option in its context menus to run a script. Such an option would be ideal for scripts working with the current context item; simply right click the item and run the appropriate script from the context menu. Would Sparx consider adding this feature?

Fred Woolsey

Suggestions and Requests / Another script request
« on: May 27, 2009, 10:48:49 am »
How about making it possible to launch a script from a hyperlink? (EA Command: RunScript ?)

Suggestions and Requests / Re: Tracking changes to connectors
« on: May 26, 2009, 09:23:10 pm »

I was thinking out loud about what Sparx might do in future to accommodate requests like this. :)

Suggestions and Requests / Re: Tracking changes to connectors
« on: May 26, 2009, 06:37:21 am »
The EA schema already has a number of "hacks" (e.g. fields holding multiple key-value pairs as a delimited list), so it would seem possible to add the requested fields to t_connector w/o changing the schema. Another alternative might be to store them as custom properties but display them in the connector properties dialog as they are displayed in the element equivalent.

Speaking of the EA schema, it may make sense at some point in future for Sparx to rework the entire schema (shades of Mac switching to Intel!), with perhaps a "conflated" database interface that handles both the old and new schemas to eliminate the "hacks" and provide better consistency in relationships between tables. The need to unpack and parse delimited data, follow Xref chains, etc. must carry some performance penalty, and as EA gets bigger, the penalty will grow with it. Consistent PK-FK relationships, normalization, etc. and indexing should speed things up. Also, the need for inconsistent handling of different bits of otherwise similar data must be a maintenance headache and a source of bugs.

I chip in my tuppence in support of Rich Text notes...

Suggestions and Requests / Requirement stereotypes
« on: October 03, 2006, 11:03:37 am »

I have a profile that defines the same requirement stereotypes as the EA SysML package (I like my graphic symbols better, so I use them instead of the add-in elements). When adding a new element in the Project view, the "Stereotype" combo box lists all of the profile-defined values; however, when using the Property dialog, only the stereotypes defined in the database table t_requiretypes are listed. Behavior ought to be consistent (and should include the profile stereotypes in both contexts).


Bug reported...

I think I found the culprit:

I added two new elements with the stereotype "requirement", and these showed no signs of the earlier problem. I then did some database snooping and found another table, t_xref, that stores tag & stereotype info. THIS table retained the old 'Requirement' stereotype. Changing the embedded string in the 'Description' field to 'requirement' corrected the problem for all elements.

Apparently this table tracks links between tags and stereotypes to something else in the model, but I'm not yet sure what. However, I would expect this table to update whenever the stereotype for an element is changed. Could this update check be where the case-insensitivity arises?


Suggestions and Requests / Profiles, case sensitivity, and stereotypes
« on: October 03, 2006, 09:12:55 am »

I encountered an odd glitch when doing direct database manipulation of stereotypes in an EAP file. I changed the stereotype field for custom Requirement elements from 'Requirement' to 'requirement' to match the SysML usage. The update was successful. I then revised the corresponding profile, renaming the 'Requirement' stereoype element (extending the existing 'Requirement' metaclass) to 'requirement'. Profile created & imported successfully. I then took a look at the diagrams containing the elements, and their images had reverted to the native shape for the 'Requirement' element. I then checked the element properties in EA and saw that the stereotype was still 'Requirement' (capital 'R') even though direct examination of the database (EAP file) showed the stereotype as 'requirement' (lower-case 'r'). It required a manual edit of the sterotype field from 'Requirement' to 'requirement' to get the image to change to the associated stereotype ShapeScript image defined in the profile.

This points to a problem somewhere with case sensitivity, it appears.


Suggestions and Requests / Run-by connector
« on: September 16, 2006, 07:41:21 am »

Some diagramming programs have a feature that I will call a "run-by" connector, where a number of blocks in a row can be connected to another block (or to each other) with a single connector placement. Such a feature would be very useful in structural diagrams where tree-style connectors link many blocks to one (e.g. generalization, nesting).

I run across this often in Requirements diagrams, where it's often necessary to link many sub-requirements to a higher level requirement. Having a "run-by" option would be a big time-saver.


Suggestions and Requests / Nesting link ignores tree style default
« on: September 16, 2006, 12:23:15 pm »
Or so it seems...

With the default link style set in Options->Links to "Tree(H)", Nesting links are drawn with "Custom" style and must be set manually to Tree style. I'm running EA 6.5.797.


Suggestions and Requests / Design Master Crashes EA
« on: September 16, 2006, 01:52:39 pm »
If EA doesn't have exclusive access to the EAP file (e.g., if the EAP file is also open in Access or Microsoft Query) and an attempt is made to make the EAP file a Design Master, EA displays an "Operation Failed" error dialog (that's all the info it gives) followed by an inescapable loop where the user is repeatedly prompted to select a DSN. Once the other applicationis closed, it works fine.


Suggestions and Requests / Sorting in Project View and Relationship Matrix
« on: September 16, 2006, 11:28:06 am »

Another "nice to have" is the ability to sort axes in the relationship matrix and elements in the Project view by properties other than the element name. Sorting by "Alias," for example, is another option that would be very useful (to me at least!). In requirements diagrams, I use the Name as the short description for the requirement (full text is in the Notes field) and the Alias as the unique requirement ID. In some cases the ID is mapped one-to-one to the requirements hierarchy, and organizing diagrams after CSV import would be considerably simpler if the requirements were listed in hierarchical order (albeit without parent-child relationships).


Suggestions and Requests / Re: Additional Profile Woes
« on: August 30, 2006, 06:05:02 am »
Thanks for the tips...I wasn't using the entire drawing area...correcting the numbers resulted in the image taking up the entire drawing area. However, when the stereotyped Event is dropped on the diagram, it appears for an instant at the preferred height and width set in the script, but then expands to the same fixed height and width (much too tall) regardless of the script settings. The same thing happens, by the way, to an unadorned "Event" image (redefined in the profile without an alternative image) when blows up to twice the height (more or less) of the standard "Receive" or "Send" images.

Here's the script:

shape main
preferredHeight = 50;
preferredWidth = 150;
layouttype = "border";

shape name
h_align = "CENTER";

shape padding



Pages: 1 ... 3 4 [5] 6 7 ... 29