There is no feature to hide stereotypes. Have you created an issue to add a diagram description to the PGML via the diagram property panel?
Bob On 31 August 2011 20:53, Mark Fortner <[email protected]> wrote: > There's a potential workaround for this that I've been experimenting with. > I added a comment to the diagram, and in the Properties panel, entered the > Body of the comment. This doesn't appear in the diagram, but can be > extracted by ArgoPrint for documentation. I was looking for some way to > distinguish these types of diagram descriptions from ordinary comments, and > the only way I found to do this is to create a "Diagram Description" > stereotype. Unfortunately, there doesn't seem to be a way to turn off > stereotype visualization for model elements. Which means that my small, > discrete little hack, looks big and ugly on the diagram. > Is there some other workaround for this that I'm not aware of? > Mark > > > On Fri, Aug 5, 2011 at 11:50 AM, Bob Tarling <[email protected]> wrote: >> >> Hi Laurant/Mark >> >> To be honest I really don't have time to dig into the diagram >> interchange stuff for UML2 together with all the other stuff that we >> need to complete for UML2 diagram presentation and modelling. That >> will have to follow later. There is some doubt as to whether this >> format will survive anyway so maybe we save ourselves some effort. >> >> For pgml vs .argo I would say to save in the pgml as this is diagram >> level data rather than project level. >> >> Bob >> >> On 5 August 2011 19:21, Laurent BRAUD <[email protected]> wrote: >> > Hi, >> > Bob you are true, if we do this, we need to do it first with PGML rather >> > than XMI. >> > >> > But, if some "standard" tag documentation exists (shortDescription, >> > author, date, ...), use the same and show them to user even if we store not >> > in "standard". >> > And When we will start UML DI, even if there is a long time, it will be >> > easier. >> > >> > However, I haven't find a such "standard" tag . >> > So which one can we add to have usefull tool. Of course, user can uses >> > others. >> > >> > What I found: >> > a) http://www.omg.org/spec/UMLDI/1.0/PDF/ >> > >> > There is a class Diagram and a XSD for diagram >> > >> > In "8.5 Properties": Non-standard properties could be added but are not >> > part of any standardization. Properties provide an extension >> > mechanism for adding non-standardized elements to the diagram >> > interchange metamodel. >> > >> > >> > => If I have well understand, we can add all properties we want. But >> > there aren't standard. Could be a choice. >> > >> > >> > b)I try TopCased: >> > <diagrams xmi:id="_2PG_gK1HEeC3fKGlWAkmOg" position="0,0" >> > size="100,100" name="StateMachine" viewport="0,0"> >> > <eAnnotations xmi:id="_ssPV4L-BEeCUNbPIxj8eBQ" >> > source="http://www.topcased.org/documentation"> >> > <details xmi:id="_ssUOYL-BEeCUNbPIxj8eBQ" key="documentation" >> > value="HERE DIAGRAM COMMENT"/> >> > </eAnnotations> >> > <property xmi:id="_2PahgK1HEeC3fKGlWAkmOg" key="pageFormatName" >> > value="A4"/> >> > ... >> > => I don't see yet where "eAnnotations" is defined in UML-DI (in XSD). >> > >> > >> > Mark, you ask for paragraph (and I agree): If we find something (in >> > norm), it must be an XML element, not an attribute. So what I found isn't >> > enought. I keep your idea in my mind. >> > >> > I don't know if what you asked Bob is possible. >> > >> > Regards, >> > >> > ------------------------------------------------------ >> > >> > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2809762 >> > >> > To unsubscribe from this discussion, e-mail: >> > [[email protected]]. >> > >> >> ------------------------------------------------------ >> >> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2809768 >> >> To unsubscribe from this discussion, e-mail: >> [[email protected]]. > > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2833428 To unsubscribe from this discussion, e-mail: [[email protected]].
