Sparx Systems Forum

Enterprise Architect => Suggestions and Requests => Topic started by: Uffe on August 04, 2020, 09:09:02 pm

Title: Specialize: remember pattern settings
Post by: Uffe on August 04, 2020, 09:09:02 pm
Hey everybody,


If you publish a package or diagram as a profile, the details of that publication (profile name, file name, etc) are stored in the repository and retrieved next time you publish the same pacakge/diagram.

This is useful.

However, patterns, which are published from the same menu and which are included in an MDG technology in the same manner (a directory with a number of individually selectable files) have no similar memory. If you need to make a minor change to an old pattern, you have to reconstruct the settings from the pattern XMI file if you've still got it or the technology XML file if you don't.

This is annoying.

Could we please have the publication settings stored for patterns like they are for profiles?

The function is in fact more useful for patterns than for profiles, since there's more metadata in a pattern which can't be easily stored in the package / diagram itself.


/Uffe
Title: Re: Specialize: remember pattern settings
Post by: Paolo F Cantoni on August 04, 2020, 11:35:32 pm
Wot 'e sed!

We're about to get into patterns and this would be required.

Paolo
Title: Re: Specialize: remember pattern settings
Post by: Uffe on August 05, 2020, 12:20:02 am
Feature requested.

/U
Title: Re: Specialize: remember pattern settings
Post by: Uffe on August 05, 2020, 12:20:52 am
Also, good luck with the patterns. They don't work all that great.
Title: Re: Specialize: remember pattern settings
Post by: Paolo F Cantoni on August 05, 2020, 08:04:52 am
Also, good luck with the patterns. They don't work all that great.
Hi Uffe,
As you might guess, we're going to implement "patterns" in our own way.  If you're interested, we can have an online (or offline) discussion on how patterns could/should be implemented in a modelling context.  I'd be keen to understand as much as necessary to enable us to come up with a viable implementation.

Paolo