|
|
Subject: RE: [argouml-dev] Profiles in ArgoUML - week #6 - msg#00056
List: db.axion.devel
> Hence, have a look at the way e.g. the visibility of the path is persisted
in FigNodeModelElement:
>
> public String classNameAndBounds() {
> return getClass().getName()
> + "[" + getX() + ", " + getY() + ", "
> + getWidth() + ", " + getHeight() + "]"
> + "pathVisible=" + isPathVisible() + ";";
> }
>
> This function builds a string that you can find back in the PGML of the
diagram.
>
> I do not remember how this is loaded back, but it works for path
visibility, so you should be able to find out...
PGMLStackParser.setStyleAttributes is where most of this work is done.
Tom
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
RE: [argouml-dev] Testing the handling of profiles that Marcos Aurelio has implemented
That looks like a great start. I wasn't able to easily review the code
because it looks like every file differs from the trunk by at least the
revision number so it was hard to identify what has actually changed. The
following comments and questions are based on a functional review.
- How are the profiles linked to the project? I didn't see anything obvious
in the XMI dump.
- Profiles appear to be organized as a flat list, but they really need to be
a hierarchy so that, for example, the Java profile can depend on the UML 1.4
profile
- There needs to be a user preference setting for the default profile(s) to
apply to newly created projects
- Be careful about commiting stuff that you didn't intend or doesn't belong
in SVN (ext directory, ArgoVersion.java, test.xmi). If test.xmi is
something useful, move it to argouml-core-tests.
- Find a better directory and better names for the default-*.xmi files. (I
know the default* naming is used now by ArgoUML, but it's not a good match
for the function it provides).
- Most Tags and all Constraints from UML 1.4 Standard Elements are missing
(see Appendix A of spec).
- There should be an ArgoUML profile with things that are ArgoUML specific
(documentation, author, version, since, etc tags from Documentation tab).
- The Java profile should include things which are used during Java Reverse
Engineering (src_path?, etc). Or perhaps the generic Java and ArgoUML Java
stuff should be kept separate? Depends on how granular we want to get. (low
proirity)
- It would be useful to have the profiles visible in the Explorer view so
that the user can browse their contents. Look at MagicDraw or some other
tools to see how linked read-only files are displayed greyed-out to show
that they can't be modified.
- Rather than having to explicitly load new profiles, I think it would be
better to have a search list of locations that are searched for profiles,
some system defined, some user specified.
- Where is the JavaBeans profile stored? I couldn't find an XMI file with a
name that looked like it would contain this.
- Is it possible to choose a default rendering other than "text" for a
stereotype? For all stereotypes in a project? I think this is another case
where a hierarchy of defaults would be useful
User<-Project<-Stereotype<-Fig
- The AndroMDA profile would make a good use case to look at. Have you
tried it? You don't want to use the flattened version of the profile that I
made, but the hierarchical version. There's a problem with the way that the
standard AndroMDA profile is saved by MagicDraw, so we'd have to see if we
can create our own version which doesn't have this problem, but is still
hierarchical. I can help with this if you want.
As I said above, it looks like a great start and I'm pleased to see progress
being made on this.
Tom
Next Message by Date:
click to view message preview
[argouml-dev] SolvingExistingIssues Report - Week #06
Done in week 6:
- Finished isssue 1308.
- Continue with issue 1288, still having some problems to implement
listeners on diagram elements that will follow font changes.
- Started with 1099. Implemented autosave, have to implement setting
of autosave interval into Edit->Properties panel
Planned for week 7:
- Finish with 1308. Will be completed by the end of this week (I hope so).
- Continue with 1288.
- Take a look at 4793 (and fix if it is not too complex).
Previous Message by Thread:
click to view message preview
Re: [argouml-dev] Profiles in ArgoUML - week #6
Hi Marcos,
* what
are the biggest challenges you are facing
2. how do I persist the stereotype view of the
FigNodeModelElement?
Well, IMHO this is something that has to be
stored with the Fig. This because if you draw a class on two different diagrams,
it may be represented as big icon on one diagram, and textual on the
other.
Hence, have a look at the way e.g. the visibility
of the path is persisted in FigNodeModelElement:
public String classNameAndBounds()
{ return
getClass().getName()
+ "[" + getX() + ", " + getY() + ",
" +
getWidth() + ", " + getHeight() +
"]" +
"pathVisible=" + isPathVisible() + ";"; }
This function builds
a string that you can find back in the PGML of the diagram.
I do not remember how this is loaded back, but it
works for path visibility, so you should be able to find out...
Regards,
Michiel
Next Message by Thread:
click to view message preview
[argouml-dev] ArgoUML Sequence - Week #6
Week #6 Report:
- FigLifeLine created.
- FigMessages created. They are dashed when a ReturnAction or a
DestroyAction is attached.
- Movements of FigMessages with a CreateAction attached relocates and
resizes the destination ClassifierRole.
--
Regards,
Christian LÃpez EspÃnola
|
|