Profile specification needs persisting to DB

[Paolo F Cantoni]

The creation of an MDG Technology using the current (855) Wizard and process is fragile at the best of times.

However, trying to keep stereotype, toolbox, QuickLinker and diagram profiles for upto three MDG technologies "on the go" becomes beyond the capability of mere humans to manage (even someone as anally rigorous and consitent as me ).

When you make an innocent mistake in the process, you may not spot the consequences immediately and trying to figure out what when wrong can be extremely time consuming.

If Sparx is going to use the Diagram as the driving force for the specification of a profile, then once the specification is set - what the name of the profile is (since it need not be the name of the diagram) and which file to save to - it should be persisted to the DB (perhaps in one of the columns of the t_diagram row).  

The user shouldn't have to respecify EVERY TIME - particularly since the "Sticky" file locator (besides being inadequately rendered as noted in: Location references insufficiently rendered) bears NO relationship (necessarily) to the file I last used for this profile diagram.

Reported,
Thoughts?
Paolo

[KP]

When you make an innocent mistake in the process, you may not spot the consequences immediately and trying to figure out what when wrong can be extremely time consuming.

Do you use merge software such as WinMerge or Araxis Merge? When I'm working with profiles and technologies, I always merge the XML files to my archive rather than copy them, and then I can see exactly what has changed since last time. If everything has changed in an XML file then I know I've made one of those innocent mistakes...

[Paolo F Cantoni]

When you make an innocent mistake in the process, you may not spot the consequences immediately and trying to figure out what when wrong can be extremely time consuming.

Do you use merge software such as WinMerge or Araxis Merge? When I'm working with profiles and technologies, I always merge the XML files to my archive rather than copy them, and then I can see exactly what has changed since last time. If everything has changed in an XML file then I know I've made one of those innocent mistakes...

Yes, I do use comparator software - but when things are not working there's no point in checking in bad code.

In any event the code ISN'T bad - it's the build process that's flawed!   The notion of forcing the user to repeat EXACTLY the same input every time (while the underlying raw data changes and may therefore have to be amended) is a design flaw surely?

The problem comes about because you CAN'T test every part of the profile EVERY time you make a minor change.  Add to that the absence of a Log File and "silent failures" - the MDG just stops working with no indication of why and...

Fix the cause not the symptom!  Even if the data is persisted to the Registry on a per profile basis that would be preferable.

Yes, I am annoyed...

Paolo

[KP]

Yes, I do use comparator software - but when things are not working there's no point in checking in bad code.

But if it's thoroughly tested then it's OK to check in bad code?

I didn't suggest checking in, just comparing. Rebuild your technology, refresh your comparison (as easy as pressing F5 in WinMerge) and get a sanity check to make sure you didn't accidentally overwrite your toolbox profile when saving your diagram profile. Prevents much hair being torn out, is all I'm saying (and I don't have so much hair that I can afford to tear out any more).

[Paolo F Cantoni]

[size=18]...[/size]
Prevents much hair being torn out, is all I'm saying (and I don't have so much hair that I can afford to tear out any more).

Point taken, but that's yet another click or three - that I shouldn't have to do...

But - like defensive driving - I'll put it in my process.  

I repeat though, if I've got a couple of MDGs "on the go" I still have to select which comparison and then refresh.

When you're trying to cut down the cycle time...  Each click adds overhead!

So, any chance it will be fixed?

Also, it's too late for me - hair wise...  

Paolo