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 - qwerty

Pages: 1 2 3 [4] 5 6 ... 12
46
Suggestions and Requests / Auto-naming of composite diagrams
« on: June 23, 2015, 04:11:23 pm »
Whenever I create a composite diagram the embedded composite diagram is named after the element's auto-name (e.g. Statemachine1).  But usually I rename the element to something meaningful on creation. So when I'm done I have to do the same with the composite diagram.

I'm not asking to link both names (which would be ideal) but if the diagram name could be set to the same name as the element [highlight]after[/highlight] pressing OK on the element properties this would be a nice improvement.

q.

47
Suggestions and Requests / Where it the North Pole?
« on: February 20, 2014, 09:32:57 pm »
I wonder what happens with all the suggestions posted here. Does anyone at Sparx really care? Or do you just send them to Santa@North.Pole?

Probably it would be nice if Santa moves from North to South Pole as it it much nearer to Australia.

q.

48
Suggestions and Requests / Better diagnostics (for MDG)
« on: April 20, 2013, 02:16:09 am »
Whenever I create a MDG and make a mistake, some things simply do not work. No message. No trace. No hint. I have to start RPG (an once famous programming language; in Germany the acronym translates Rate, Probiere, Gucke - guess, experiment, look - maybe Riddle, Probe, Glance could be an equivalent acronym).

q.

(I'd wish the same for other secret things like e.g. XMI import with Duplicate Key messages, DB access errors in various circumstance. But MDG improvements would be a place to start with.)

49
Suggestions and Requests / Auto-select message upon creation
« on: May 01, 2013, 02:41:22 am »
Currently if you create a message to an object EA puts the focus on the target element, not on the created message. The way I use the tool is to create and then edit the message to assign a method name. Unfortunately again, it looks like the message is selected, but it isn't. So the Enter key following the creation will open the object properties. It would be soooo nice if this use case would be supported.

And NO, the option "edit connector on create" is not an option since I want to do this only with the minor number of messages and NOT with all the other connectors. Honestly I don't want a new option for that too unless the other options get a meaningful structure! The current one is not really prepared to win an UI design award.

q.

50
Suggestions and Requests / Delete method in API
« on: May 01, 2013, 09:38:40 pm »
Each thing (be it element, connector, package, diagram or what else) should have a Delete method to directly delete it. Rather than locating it in one of its parent collections and then deleting it from there.

q.

51
Suggestions and Requests / Checkmark in MDG selection
« on: April 20, 2013, 07:13:56 am »
If the checkmark in the MDG selection would be located left of the text it would be much easier to identify which are turned on and which will be turned on/off when clicked.

q.

52
Suggestions and Requests / Editing of class properties
« on: March 20, 2013, 04:24:24 am »
I wonder why nobody complained (loud enough) about the bad support for editing class properties, especially with attributes, methods and parameters. Right now, when you want to edit class attributes, a new window opens and the class properties go away. Instead, the attributes should show in a separate view of the properties window right hand side of the general properties. Further if you need to edit the methods, they could appear in the same view instead of the attributes. For the parameters of methods a 3rd view could open right of the first two to allow in-line editing of methods and parameters.

Thoughts?

q.

53
Suggestions and Requests / Layout for Activity diagrams
« on: March 20, 2013, 08:50:13 am »
Per default all diagrams are set to layout style "bottom up". But activity diagrams are usually top down. And often UC diagrams are left to right (or also top down).

The auto-layout is disabled for these diagrams. But you can use the "Layout selected elements". First it would make sense to enable the layout button as 1) you can do it anyway using the context menu and 2) in most cases the layout gives a good result for a first shot.

Further it would make sense to either change the default layout direction for the named diagrams (and possibly others?) or - even better - to give it a default setting in the options so you can change it globally.

Thoughts?

q.

54
Suggestions and Requests / Include issue number in release notes
« on: July 11, 2012, 07:22:21 pm »
Each time I submit a bug report Sparx assigns an issue number for it. I have quite a number of such issue numbers and never get feedback what their state is - unless I poll.

Now, when a new release comes out wouldn't it be nice to read the list of closed issues? Just the numbers. That would help me to close my open issues. And it should be no effort for Sparx.

q.

55
Suggestions and Requests / Limiting the loaded MDGs
« on: April 06, 2012, 12:17:42 am »
In order to not flood users with superfluous click-tasks we would like to automatically limit the MDGs to UML2 plus our own MDG. Currently the only way is to read the Options from the registry, manipulate the MDG_TECHNOLOGY_STATUS key and ask the user to restart if it needed to be changed (since EA already has evaluated that key when the EA_Connect is fired).

Would it make sense to ask for an API addition to limit MDGs to a certain subset?

q.

56
Suggestions and Requests / Interaction State
« on: February 23, 2012, 12:47:34 am »
When showing states in a sequence diagram you have the choice to either drag a state onto the diagram or to create InteractionStates elements. It seems obvious that there's a relation between both. You could say that InteractionState cite States verbally. You can only drag one single occurrence of a State onto a diagram. The "instance of an element" does not work. It's always copied as a link.

So my suggestion: an InteractionState is an instance of a state. When you ctrl-drag a state the "instance of an element" will create an InteractionState. For a start it would be sufficient if that element just receives the name of the state. However, it would be more logical if there's also a relation between both (a classifier) so you can trace back from the InteractionState to the State.

q.

57
Suggestions and Requests / User management
« on: January 12, 2012, 02:35:02 am »
We have several EA repositories on a SQL server where a couple of modellers work. Since we use Require Lock to Edit we have EA security enabled. The problem we have here is that all users need to be maintained individually in the single repositories. What we currently do is exporting the users as reference data, login to the other repositories and import the users. This is quite tedious. It would be much more convenient if I could tell EA to directly map the users to other repositories. (I just remember a post where Uffe wanted model elements representing EA repositories. How nicely that would fit here.)

Honestly, taking the above step it should not be difficult to have some kind of central user management. E.g. by having a master repository. Which in turn could contain Uffe's repository elements to model the deployment.

q.

58
Suggestions and Requests / Baseline merge
« on: January 20, 2012, 10:56:23 pm »
I wonder why nobody else had stomach ache with this one so far: When you compare a model to XMI and merge a single element EA starts the whole model compare from the beginning - which takes quite a while when comparing complete models. I simply ask: why? The result of the merge should be that the merged element is no longer different and can simply be removed from the list. This should take only a millisecond.

q.

59
Suggestions and Requests / Recursive baseline merge
« on: January 20, 2012, 11:19:19 pm »
Another nuisance with baseline merge is that to get a package (or a number of different changes to an element like tags and relations) you need to manually select each and everything. That is unfold the whole thing and select everything manually. Why doesn't merge do what you would expect and recursively merge everything below an element?

q.

60
Suggestions and Requests / MDG creation process
« on: December 16, 2011, 11:55:31 pm »
The current MDG creation process is quite error prone. It refers to a couple of profile XMI files located on the disk. All these files usually come from the model itself. What you do when changing the model is locating the source package or diagram and save it to disk. The position of the file is not retained (instead it refers to a last-recent-location). So it often happens you save the profile to a wrong location. Then you create the MDG anew, restart EA and find your MDG not working. An often tedious process. (I'm just looking for the profile XMI which has been clobbered by one of the last saves.)

Instead why not saving references to the source packages/diagrams inside EA and invoke the generation which uses temp saved files to create MDG?

q.

Pages: 1 2 3 [4] 5 6 ... 12