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

Pages: [1] 2 3 ... 6
1
Suggestions and Requests / Re: Fix the feature screen
« on: June 09, 2018, 06:22:21 pm »
Also, I submitted a feature request, not a support request, nor a bug request. Because the new functionality works, as designed, but just in a much less focussed manner. And I get normally people would suggest new features, not the return of old features. But if suggest feature isn't the correct route to highlight what is IMO a bit of faux pas, then Iĺl gladly send it into another process chain.Whatever gets it some serious consideration and not a 5 sec glance over with a 'naah, let's not'. Or perhaps I am missing a new super approach that is more efficient and need some explanation. But one fact remains, what was pretty slick in -13.5, has since 14, become a clunky way of working. It reminds me of RSA in a way, the same, it works, but not in a nice way feeling. I am not alone in thinking this...... But EA can be used for many things in many different ways and the finding applies really only to one of EA core functions, class and data modelling.

2
Suggestions and Requests / Re: Fix the feature screen
« on: June 09, 2018, 06:06:49 pm »
I did that, even got a mail as confirmation:

Quote
The following feature request was submitted by Chris xxxxxxxx (mailto:chrisxxxxxxxxxxxxxx)

FEATURE DETAILS

Subject:
EA14 Feature screen

Details:

lots of details trimmed....


The form submittal said someone would be in touch, but perhaps I misread and it only applies to support requests, not feature requests. I used the form. It would have been nice to have some feedback. Either 'not going to happen', so I know 13.5 is my last version, or some kind of timeline. As it is essentially a plea to reinstate s former UI path, or to expand the new UI path to work more ergonomically, it is not really a trivial thing, it relates directly to EA's practical usability. A feature which I have used with some success to promote EA in my client's workplace, where there is a natural tendency to go for more expensive and less useful tools. Anyway.... we shall see.

3
Suggestions and Requests / Re: Fix the feature screen
« on: June 06, 2018, 10:33:20 pm »
After following the correct procedure, which informs me that someone from Sparx will contact me, it has gone quiet. Not sure what that means....Of course, there´s no mention of timelines, so this might be part of the process.

4
Suggestions and Requests / Re: Fix the feature screen
« on: May 31, 2018, 02:53:47 am »
I have  :)

5
Suggestions and Requests / Fix the feature screen
« on: May 24, 2018, 07:35:57 pm »
In EA 14, the feature screen makes entering a series of attributes  / operations a pain. Unfortunately, I do quite a bit of both. In 13.5, you work on a dialog that contains all three bits, the notes, the extra settings and the name, type, visibility etc... This is helpful and efficient.

In EA 14, there's a feature screen and 2 tabes of the property screen required to enter the same information. This makes entering attributes / operations a lot more work and it takes significantly more time.

I can suggest two possible solutions, or any other that allows me to enter an attribute / operation in full from a single screen:
1. Make the feature screen optionally look like the old dialog, if you want the feature screen to remain dockable, that's fine.
2. Allow the feature screen to have custom sets of fields, so the ones I use a lot are on a single line. Note that this set differs per type of feature, so for this to work well, it should have either a labelling system or other form of memory. Everything that is there on the EA 13.5 screen should be selectable.

Although I love many improvements I see in EA 14, time is money and this slowdown is enough to prevent me from moving to 14.

6
They can make it look it any way they like, but the requirement should and must be that you can define the attribute / operation wholly from one screen, not 2 screens and 2 tabs. The old dialog does that, and I like that because of it. But I'm not hung on the dialog, If they allowed you to added the relevant feature items to the line, might also work, if the setting sticks. But I cannot afford the slow down. Which is a shame, because I love the guidlines when placing elements on a diagram, that's a time saver.

7
I couldn't find the previous build, and I keep all versions already, so moving down to 13.5 was simple and effective, but not desirable. I'd just like the old dialogue, much easier when you add say 10 or 20 attributes at once. Which for database stuff, is a common operation..... The new screen is not bad, just cumbersome now, because the old screen combined 3 bits that you go through. Name, type and visibility. Then mark things like id, cardinality and finally I enter a description. In the new set up I have to type name and type in the attributes screen, then go to the property screen, tab 1 to set the other stuff, and finally tab to the description (notes) for that attribute. It's just a lot of clicking.

Now I'm back to EA13.5, I notice that the property window I have doesn't leave the class/table when I am working with the attributes, so I have slightly more relevant info I can see. I would have preferred that the old screen would be simply dockable, and/or you can select those parts. Anyway.....

8
General Board / Re: Attributes
« on: May 24, 2018, 12:20:21 am »
For now, I have gone back to 13.5, and have the dialog back again. But still, not entirely satisfactory. I really like some of the other 14 improvements. But not at the cost of losing the dialog....

9
Hmm, I didn't notice it until build 1420. But editing attributes is likewise clumsy. Where I had one screen, which was easy to tab around, I now have 2 windows, one window 2 tabs, to enter the same. It is more than clunky. I hope there is a way to also reinstate the older screen, pity I forgot to keep 1419, as I can't download it anymore....

10
General Board / Attributes
« on: May 23, 2018, 11:31:43 pm »
I am not sure if it is me, or something EA changed with the latest incarnation of EA 14, but entering attributes has become somewhat of a hassle. Before I would get a dialog, where I could simply type name, type and visibility. Now I get a window below the diagram for name and type, but visibility has to be entered in the property box (which I normally also keep to the side.

I want the old dialog back, is that a setting somewhere? I haven't played around with the windows, themes, perspecitives, workspaces.... I can't rule out it was me, accidentally clicking on something in the ribbon, but it isn't apparent what I've done, or perhaps it's not me. 

11
General Board / Re: How to report cascading deletes?
« on: May 17, 2018, 01:30:28 am »
Thanks a tonne!

My query was no where as robust as your example, nor as complicated. I used PGAdmin's query ability to find what I needed and then applied a few things I saw in your example to add it into the fragment. It works like a charm. Yet another way to tweak reports, this one seems quite useful. Fragments, Virtual documents I have used before, but this SQL stuff is quite easy and very effective for certain tricks (like reporting cascading delete's). In the end, as there are only two tags, I opted to exclude the tag with the value property, so the result should work fine with all the options you can set on the FK. No doubt it will be improved at some point, but at least now I can send the document including this particular bit of info.

12
General Board / Re: How to report cascading deletes?
« on: May 16, 2018, 11:31:21 pm »
Time to learn that then.... I've got some idea on the query, but wonder on the starting point. Right now, my fragment is called from a Foreign Key fragment, called from a Database Table fragment. It's called on the Element level, where I've added the method and method tag sections.

I'm guessing that I would need a query that returns the stuff I want (method name, tag name, tag value) and the where you select only those tag names that are 'Delete' or 'Create'. But for the element at large, how do I add that into the query?

13
General Board / Re: How to report cascading deletes?
« on: May 16, 2018, 10:30:31 pm »
With a separate fragment I can filter the methods so that only those that have a OnDelete, OnCreate set are reported, but I am not able to ignore the 'property' tag and just report the Delete tag.. What I am not doing right?

14
General Board / Re: How to report cascading deletes?
« on: May 16, 2018, 08:57:46 pm »
Yes, that worked. I added the method and tag sections on the table fragment.  I now get

(name)=(value)
Delete=Cascade
property=Delete Cascade=1;


And would like to have only one (the first looks more report friendly. I've forgotten how to do that, could I pick your mind one more time?

15
General Board / Re: How to report cascading deletes?
« on: May 16, 2018, 06:56:00 am »
Can't see it there either. In the Foreign key template, I can add the section element->connector->constraint  but it doesn't allow me to insert a field that seems to make sense

Pages: [1] 2 3 ... 6