Re: Re: Diagram Descriptions in ArgoUML
Mark Fortner <[email protected]> Wed, 31 Aug 2011 16:21:57 -0700
| Newsgroups | gmane.comp.lang.uml.argouml.user |
|---|---|
| Message-ID | <CAOwy01t7m2C1cgeoU2f1dpsR965+Gon0vnnRBH6odLdCvSKNgw@mail.gmail.com> |
------=_Part_15853_1361157322.1314832920864 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Bob, Thanks for the info. I've created an issue for diagram descriptions: http://argouml.tigris.org/issues/show_bug.cgi?id=6360 I looked into GEF and it seems that Diagrams have comments which could be used, but there's no support in ArgoDiagram for it. Regards, Mark On Wed, Aug 31, 2011 at 3:32 PM, Bob Tarling <[email protected]> wrote: > 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]]. > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2833435 To unsubscribe from this discussion, e-mail: [[email protected]]. ------=_Part_15853_1361157322.1314832920864 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <br clear=3D"all"><div>Hi Bob,</div><div>Thanks for the info. =A0I've c= reated an issue for diagram descriptions:=A0<a href=3D"http://argouml.tigri= s.org/issues/show_bug.cgi?id=3D6360">http://argouml.tigris.org/issues/show_= bug.cgi?id=3D6360</a></div> <div><br></div><div>I looked into GEF and it seems that Diagrams have comme= nts which could be used, but there's no support in ArgoDiagram for it.<= /div><div><br></div><div>Regards,</div><div><br></div><div>Mark</div> <br><br><div class=3D"gmail_quote">On Wed, Aug 31, 2011 at 3:32 PM, Bob Tar= ling <span dir=3D"ltr"><<a href=3D"mailto:[email protected]">bob.tar= [email protected]</a>></span> wrote:<br><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> There is no feature to hide stereotypes.<br> <br> Have you created an issue to add a diagram description to the PGML via<br> the diagram property panel?<br> <br> Bob<br> <div><div></div><div class=3D"h5"><br> On 31 August 2011 20:53, Mark Fortner <<a href=3D"mailto:phidias51@gmail= .com">[email protected]</a>> wrote:<br> > There's a potential workaround for this that I've been experim= enting with.<br> > =A0I added a comment to the diagram, and in the Properties panel, ente= red the<br> > Body of the comment. This doesn't appear in the diagram, but can b= e<br> > extracted by ArgoPrint for documentation. =A0I was looking for some wa= y to<br> > distinguish these types of diagram descriptions from ordinary comments= , and<br> > the only way I found to do this is to create a "Diagram Descripti= on"<br> > stereotype. =A0Unfortunately, there doesn't seem to be a way to tu= rn off<br> > stereotype visualization for model elements. =A0Which means that my sm= all,<br> > discrete little hack, looks big and ugly on the diagram.<br> > Is there some other workaround for this that I'm not aware of?<br> > Mark<br> ><br> ><br> > On Fri, Aug 5, 2011 at 11:50 AM, Bob Tarling <<a href=3D"mailto:bob= [email protected]">[email protected]</a>> wrote:<br> >><br> >> Hi Laurant/Mark<br> >><br> >> To be honest I really don't have time to dig into the diagram<= br> >> interchange stuff for UML2 together with all the other stuff that = we<br> >> need to complete for UML2 diagram presentation and modelling. That= <br> >> will have to follow later. There is some doubt as to whether this<= br> >> format will survive anyway so maybe we save ourselves some effort.= <br> >><br> >> For pgml vs .argo I would say to save in the pgml as this is diagr= am<br> >> level data rather than project level.<br> >><br> >> Bob<br> >><br> >> On 5 August 2011 19:21, Laurent BRAUD <<a href=3D"mailto:bd1664= @yahoo.fr">[email protected]</a>> wrote:<br> >> > Hi,<br> >> > Bob you are true, if we do this, we need to do it first with = PGML rather<br> >> > than XMI.<br> >> ><br> >> > But, if some "standard" tag documentation exists (s= hortDescription,<br> >> > author, date, ...), use the same and show them to user even i= f we store not<br> >> > in "standard".<br> >> > And When we will start UML DI, even if there is a long time, = it will be<br> >> > easier.<br> >> ><br> >> > However, I haven't find a such "standard" tag .= <br> >> > So which one can we add to have usefull tool. Of course, user= can uses<br> >> > others.<br> >> ><br> >> > What I found:<br> >> > a) <a href=3D"http://www.omg.org/spec/UMLDI/1.0/PDF/" target= =3D"_blank">http://www.omg.org/spec/UMLDI/1.0/PDF/</a><br> >> ><br> >> > There is a class Diagram and a XSD for diagram<br> >> ><br> >> > In "8.5 Properties": Non-standard properties could = be added but are not<br> >> > part of any standardization. Properties provide an extension<= br> >> > mechanism for adding non-standardized elements to the diagram= <br> >> > interchange metamodel.<br> >> ><br> >> ><br> >> > =3D> If I have well understand, we can add all properties = we want. But<br> >> > there aren't standard. Could be a choice.<br> >> ><br> >> ><br> >> > b)I try TopCased:<br> >> > =A0<diagrams xmi:id=3D"_2PG_gK1HEeC3fKGlWAkmOg" = position=3D"0,0"<br> >> > size=3D"100,100" name=3D"StateMachine" vi= ewport=3D"0,0"><br> >> > =A0 =A0 =A0 =A0<eAnnotations xmi:id=3D"_ssPV4L-BEeCUN= bPIxj8eBQ"<br> >> > source=3D"<a href=3D"http://www.topcased.org/documentati= on" target=3D"_blank">http://www.topcased.org/documentation</a>"><b= r> >> > =A0 =A0 =A0 =A0 =A0 =A0<details xmi:id=3D"_ssUOYL-BEe= CUNbPIxj8eBQ" key=3D"documentation"<br> >> > value=3D"HERE DIAGRAM COMMENT"/><br> >> > =A0 =A0 =A0 =A0</eAnnotations><br> >> > =A0 =A0 =A0 =A0 <property xmi:id=3D"_2PahgK1HEeC3fKGl= WAkmOg" key=3D"pageFormatName"<br> >> > value=3D"A4"/><br> >> > =A0 =A0 =A0 =A0...<br> >> > =3D> I don't see yet where "eAnnotations" is= defined in UML-DI (in XSD).<br> >> ><br> >> ><br> >> > Mark, you ask for paragraph (and I agree): If we find somethi= ng (in<br> >> > norm), it must be an XML element, not an attribute. So what I= found isn't<br> >> > enought. I keep your idea in my mind.<br> >> ><br> >> > I don't know if what you asked Bob is possible.<br> >> ><br> >> > Regards,<br> >> ><br> >> > ------------------------------------------------------<br> >> ><br> >> > <a href=3D"http://argouml.tigris.org/ds/viewMessage.do?dsForu= mId=3D449&dsMessageId=3D2809762" target=3D"_blank">http://argouml.tigri= s.org/ds/viewMessage.do?dsForumId=3D449&dsMessageId=3D2809762</a><br> >> ><br> >> > To unsubscribe from this discussion, e-mail:<br> >> > [<a href=3D"mailto:[email protected]">user= [email protected]</a>].<br> >> ><br> >><br> >> ------------------------------------------------------<br> >><br> >> <a href=3D"http://argouml.tigris.org/ds/viewMessage.do?dsForumId= =3D449&dsMessageId=3D2809768" target=3D"_blank">http://argouml.tigris.o= rg/ds/viewMessage.do?dsForumId=3D449&dsMessageId=3D2809768</a><br> >><br> >> To unsubscribe from this discussion, e-mail:<br> >> [<a href=3D"mailto:[email protected]">users-uns= [email protected]</a>].<br> ><br> ><br> <br> ------------------------------------------------------<br> </div></div><a href=3D"http://argouml.tigris.org/ds/viewMessage.do?dsForumI= d=3D449&dsMessageId=3D2833428" target=3D"_blank">http://argouml.tigris.= org/ds/viewMessage.do?dsForumId=3D449&dsMessageId=3D2833428</a><br> <div><div></div><div class=3D"h5"><br> To unsubscribe from this discussion, e-mail: [<a href=3D"mailto:users-unsub= [email protected]">[email protected]</a>].<br> </div></div></blockquote></div><br> ------=_Part_15853_1361157322.1314832920864--