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 - «Midnight»

Pages: 1 ... 3 4 [5] 6 7 ... 377
Suggestions and Requests / Re: Generate HTML report
« on: September 02, 2009, 07:23:44 am »
This sounds fairly serious. Try checking the database with the Project Integrity Check dialog. Open the project and from the main menu choose Tools | Data Management | Project Integrity Check, Or use the Shift-F9 keyboard shortcut.

If things check out, or if the problem persists, send a bug report to Sparx right away. If at all possible attach a compressed copy of your project so they can see what's happening. [You will have to use the Registered Users version of the bug report to attach a file. If you cannot access that bug report version you should send an email to Sparx Support and attach the file.]

Please let us know what happens either way.


Suggestions and Requests / Re: Feature Request - Submit Button
« on: September 01, 2009, 01:53:22 am »
Sometimes all you need to do after pasting in your address is add a space at the end. You can delete the space if you want to be sure the field is faithful to what you pasted. Just changing the field should cause the validation code to run. That seems to be when the form sets the button states.

Suggestions and Requests / Re: Error Messages - Transformation Editor
« on: September 01, 2009, 01:50:04 am »
My earlier attempts to use the support page on the Sparx web site failed because there is an issue with the "Submit" button (I have raised a separate bug report on the forum)
I ran into something similar several months ago. After I sent an email to Sparx Support they got the bug report page working again pronto.

Very much so.

I've always felt this was something of an omission. It seems almost strange that it is has not found its way into the product.

High time it does!

Suggestions and Requests / Re: Allow keyboard shortcuts for addins
« on: August 25, 2009, 12:47:39 am »
Oh yes please!

This is one persistent hole in EA's extension mechanisms.

You can almost stitch something together by combining bits and pieces of functionality. But the results always fall (well) short of simply being able to specify a help file. Ideally, EA would let you set up topic references and such, but that's moot until you can set up the file itself.

I've experimented with this a bit. The results have not been encouraging. [NOTE: This does not mean you cannot do better. I just gave up when it became obvious that the best case fell well short of what was needed at the time.]

You can create an add-in that loads your technology. Or the add-in can remain dormant, listening to EA's events, until your technology is loaded. Either way, you can designate a help file when the technology loads. Note that your add-in has to keep track of this file; there is no place in EA itself to do this. You can then trap some events to look up topics in your help file.

Note that the only event (I can find) that purports to react to help requests is not what you really need. This event seems to fire only when the user presses F1 while an add-in (sub)menu pad has focus. Not very useful...

The best I was able to do was trap things like double-clicking a stereotyped element (I had to trap events for all elements and react to those that met my criteria) and 'divert' the event to a help request. There does not seem to be any way (again, that I found) to trap something like F1 when an element has focus (let alone capture information about which element it is).



PS: I did not register a feature request for this. At the time I had a large number of request open. The Sparxians did legion duty in addressing many of them (whether they implemented them or not), but it became apparent that I had saturated their tolerance at the time. The time frame of the requirement mandated using another solution (i.e. without EA). I've since moved on to other issues...

I must be missing something; a) I thought this forum was for feature requests and b) I can't see the button or link you mean to get this as a request...
Look at the very bottom of a forum page after you scroll all the way down. Under the Sparx logo near the bottom left you will see several columns of links. Beneath the Support link you will see a Feature Request link.

Click that link and you will reach the Feature Request link.

It is quite reasonable that you expected this to be the feature request mechanism. That confusion is due to the name of this forum section. I suspect (without proof) that is a legacy throwback to the early days of EA.

This is a user forum. [Though the Sparxians are certainly active participants.] This section provides us (the user community) with a place to air our suggestions and requests, and to engage in open discussion. Many times an idea will be found to have an acceptable workaround; it is very possible that another user will post it here, this solving the problem. Other times an idea becomes refined through forum interaction.

To make an 'official' request to Sparx though, you must use the Feature Request form. This guarantees that the request will at least be read. It does not mean it will be answered or fulfilled. But if a good idea comes in Sparx may well adopt it. And if enough people make a given request then a feature that otherwise might not have made the cut might develop sufficient priority.

One best practice we use is to post requests to the forum - you've already got that done - and then paste the URL of that forum thread into the feature request. That may help the Sparxians to join in the discussion, or at least gauge the level of interest by reading the responses.


I've asked for improvement of the ordering in past. No response.

Perhaps you should request this feature. Use the Feature Request near the bottom of any forum page. More requests might convince them that someone out here cares...

[edit]Changes with emphasis added in response to Frank's point.[/edit]

I agree, with the exception of the priority ranking. IMHO they are all equally important. Nor do I see this as an all-or-nothing scenario. The 'nothing' option is just plain unworkable, and since we can access class constraints we're beyond that point now.

IMHO this is a bug. It could be interpreted as a side effect of how EA implements items such as constraints and attributes; such a side effect is still a flaw. We have seen similar wrinkles in how (for example) tagged values are handled differently for elements, connectors, attributes and such. But in the case of tagged values we can usually get at the various objects and collections. We need access in the case of all constraint types as well. There are a few exceptions; these are clearly bugs in how the paradigm is implemented.

Methinks the man makes sense!

This pattern shows up in several places throughout EA. Like this case some are annoyances to a greater or lesser extent.

This seems to be associated with settings that EA stores in the repository. These become global in nature even if the intent is (or should be) otherwise. An example is the default DBMS language. If this is set to a 'new' DBMS (i.e. one that is identified in a recent update to reference data) then older projects (that do not have the new reference data) 'forget' their DBMS setting, causing chaos when updating models.

In other cases this information is embedded in seed models that are stored in hard-coded locations in the EA install path. Users might not be able to change these files; even if changes can be made they may have to be revisited after new EA builds are installed. A case in point is the Default Language for Code Generation. This setting can wreck havoc in projects where Java is not the target language.

In others the result can be meaningless settings with significant danger of catastrophe. In some cases this pattern causes EA features not to work, or to produce incorrect results. A case in point for both these observations is the most recent schema name (i.e. the target for USE statements) for DDL. This is preserved across all data model packages and diagrams in a model, rendering subsequent DDL generated for other schema to be incorrect. Worse still, the resultant code generally does not fail outright, but corrupts the target database (if the earlier USE statement had a valid target).

The above DDL setting is also preserved across models. Thus previously correct models suddenly generate code with a different USE statement; the target might be meaningless to the database involved, but if the two models target the same server instance this can result in disaster. And if two models have different DBMS language settings the USE clauses can become a major annoyance.

Yes, I've reported this to Sparx, since EA 7.0. I have received no response whatsoever.

Sigh... >:(

Suggestions and Requests / Re: Package: Set As Namespace Leaf
« on: August 11, 2009, 10:28:38 pm »
Of course we should still be able to turn this off by clearing the strict UML option...

Suggestions and Requests / Re: Package: Set As Namespace Leaf
« on: August 10, 2009, 08:27:13 pm »
Me too...

Although I think we (and possibly EA, and perhaps even - as some have suggested - UML itself) may be mixing our metaphors...

If you look at the examples the the Superstructure presents, the namespace is about identifying the root...  So when we say "From namespace" the namespace is the root.  It is self deluding to think that placing the lowest level namespace without qualification as an reference to the source would be suitable.  Uffe's example is just one that blows that idea out of the water...

Since EA allows multiple namespace roots with the same name - all is lost anyway.  Since you can't unambiguously define a source using just one level of a hierarchy, I just remove the namespace visibility from virtually all my diagrams.  As others have said, too often they just get in the way (especially for business punters).

We are mixing the notion of a namespace with the source of an item.  The two aren't the same thing...

Paolo makes a very good point here. You can have multiple namespaces with the same 'final' name, but their paths must all be unique across the entire scope of a model. Unless EA updates functionality to show the entire package (namespace) path for elements this might all be for naught.

Suggestions and Requests / Re: Package: Set As Namespace Leaf
« on: August 08, 2009, 09:21:27 pm »
And another...

Suggestions and Requests / Re: Add GIT as a supported VCS
« on: August 11, 2009, 09:06:50 pm »
Does Komodo handle GIT? If so you might be able to use Komodo as an SCC front end. You would still have to determine whether EA and Komodo would cooperate; I have no information whatsoever about that.

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