Project Template Packages

[Scott Lurton]

I'm trying to create a cosmetic standard for my team.
* I created a package
* created a component diagram in that package
* I created elements on that diagram with my cosmetic standards. For example I created a Packaging Component with the background color I want.
* Saved the diagram.
* Went to Settings/Project Template Package...
* Pointed at the package I just created
However....
When I open a component diagram and add a packaging component it will not use the background color that I defined in the package template.

Any ideas??

[qwerty]

I never really used template packages. I recommend you look into MDG.

q.

[KP]

It appears that Project Template doesn't affect packages or packaging components. Nor connectors.

[qwerty]

It appears that Project Template doesn't affect packages or packaging components. Nor connectors.

Hm. I was sure having read a recent post that stated it worked with connectors. My memory might have deceived me, though.

BTW: Neil, your avatar points to http://www.sparxsystems.com/yabbfiles/avatars/file://Users/ncapey/Desktop/New%20folder/systems-guy.png
Unfortunately (I guess) nobody else has access to your desktop.

q.

[Glassboy]

To have a standard colour palette I use an MDG with shape script that just sets the fill colour and draws the native shape.  I find this much more reliable than other ways of assigning colour.

Code: [Select]

shape main{
      defSize(100,80);
      setfillcolor(220,198,224);
      drawnativeshape();
}


[Paolo F Cantoni]

To have a standard colour palette I use an MDG with shape script that just sets the fill colour and draws the native shape.  I find this much more reliable than other ways of assigning colour.

Code: [Select]

shape main{
      defSize(100,80);
      setfillcolor(220,198,224);
      drawnativeshape();
}


An alternate way is to define the default in the MDG:
                              <Stereotype name="Measure" metatype="Measure" notes="" bgcolor="14938876" fontcolor="16448" bordercolor="0" borderwidth="1" hideicon="0">

This, then, allows the users to better override the shapescript to emphasise some state or other of the vertex.

Paolo

[Eve]

If you're using a shape script to colour a native shape of an element, you should be aware that it overrides the default appearance (F4) of any elements. It can still be overridden using the local appearance (on the diagram toolbar)

In my opinion, a nicer thing to do for your users is set a fill colour on the stereotype. This still provides the default colour for that stereotype, but allows users to overwrite it on all diagrams or on individual diagrams.

The fill colour applied is based on this order, where each item except the first can be suppressed.
Global default -> Element Group Style -> Stereotype Color -> Default Color -> shape script setfillcolor for drawnativeshape -> Local Color -> shape script setfillcolor for explicitly drawn shapes

[Glassboy]

If you're using a shape script to colour a native shape of an element, you should be aware that it overrides the default appearance (F4) of any elements. It can still be overridden using the local appearance (on the diagram toolbar)

In my opinion, a nicer thing to do for your users is set a fill colour on the stereotype. This still provides the default colour for that stereotype, but allows users to overwrite it on all diagrams or on individual diagrams.

The fill colour applied is based on this order, where each item except the first can be suppressed.
Global default -> Element Group Style -> Stereotype Color -> Default Color -> shape script setfillcolor for drawnativeshape -> Local Color -> shape script setfillcolor for explicitly drawn shapes

Doing it that way you get the appearance of the stereotype along with the colour.  There were times I found that that problematic.  And there is also the time you accidently uncheck the box on the profile export and then spend hours trying to work out what is going wrong :-)

[qwerty]

... you accidently uncheck the box on the profile export and then spend hours trying to work out what is going wrong :-)

For that reason I wrote me a short script that assembles the single profiles in the MDG. This is faster (one command line call instead of a dozen clicks/returns) and more safe (I can check the contents of the profiles to be what they pretend to be).

q.