Add style name to Style

[Paolo F Cantoni]

We're starting to be more serious about the use of styles for our diagrams.  It would be very useful if we could have the actual style name (not just the resultant rendering attributes) in the ObjectStyle field of the DiagramObject or Style field of the DiagramLink.

In fact, true support for styles would abstract the rendering attributes from the DiagramObject or DiagramLink and use the current values specified in the style definition.   This would allow easy changes to rendering (in the way of a theme) and, indeed, could be added to the "Theme and Appearance Options".

Heaven forbid, they could also be used to automagically tie legends to styles!

Thoughts?

Reported,
Paoloo

[qwerty]

Over year's we've learned to draw the EA-way. And it never has really changed. This likely reflects the mind of the persons responsible for developing the diagramming part. And guessing from this constant "style" I guess we won't see any change unless there's a tragic accident (which hopefully for those persons will never happen).

q.

[Eve]

If I understand you correctly, what you've been asking for is something that I've wanted to do for years.

[Paolo F Cantoni]

If I understand you correctly, what you've been asking for is something that I've wanted to do for years.

Who's the "you"?  Me or qwerty?  Or both?

Paolo

[RoyC]

Since the action that qwerty mainly talks about is the demise of a Sparxian or two, I would hope that Simon is only yearning for the feature that you (Paolo) mention.
...
...
But then again...

[Paolo F Cantoni]

[SNIP]
...
But then again...

You might well think that.  I couldn't possibly say that...   

Paolo

[Eve]

To be clear...

I was describing that I have wanted to see named styles (sets of display options) being defined at a model level, and the diagram objects referencing these instead of copying the settings to themselves.

In my dreams I'd like to assign one of these styles to diagrams, elements and packages too and have inheritance from up a chain for unspecified values, and be able to directly override individual elements of the style without complete override. Then I dream about similar ways of handling other sets of options (eg. code generation) in the same way. 

I don't think something like that would require a tragic accident, and I'm not saying that I don't sometimes want tragic accidents...

[qwerty]

 

[Glassboy]

Since the action that qwerty mainly talks about is the demise of a Sparxian or two, I would hope that Simon is only yearning for the feature that you (Paolo) mention.

He said tragic accident, which could be being served a VB when you'd asked for a beer :-)