- This topic has 40 replies, 16 voices, and was last updated 18 years, 7 months ago by
.
-
Posts
-
So far I am enjoying the UML support.
The great thing I find so far is that the UML has its own repository which means
that it doesnt spray your source code with JavaDoc annotation ala Omondo.
This is a great because you cant spray arbitary JavaDoc into Jakarta Struts
source code or Expresso Framework especially if you are committer.I like the fact I could drag and drop a Java source file from the standard
Package Explorer in the UML class diagram.I did not like that the same UI approach would not work for Java packages.
I immediately wanted to Zoom Pan around the UML. So I wish there was “Porthole”
widget. May be Genuitec can write brand new SWT Outline component that will pan and zoom simultaneously (Hint Hint)I did not like that you cant double click on class in the class diagram and jump
to the source code.Overall that is good for My UML and a little competition doesn’t hurt.
Peter P
The great thing I find so far is that the UML has its own repository which means
that it doesnt spray your source code with JavaDoc annotation ala Omondo.
This is a great because you cant spray arbitary JavaDoc into Jakarta Struts
source code or Expresso Framework especially if you are committer.Excellent point.
I did not like that the same UI approach would not work for Java packages.
We know, this is on our TODO list.
I immediately wanted to Zoom Pan around the UML. So I wish there was “Porthole”
widget. May be Genuitec can write brand new SWT Outline component that will pan and zoom simultaneously (Hint Hint)Great suggestion, I’ll check with the UML team and make sure they are thinking about this.
I did not like that you cant double click on class in the class diagram and jump
to the source code.This is on our TODO list as well, but aparently isn’t as easy as it would initially seem.
Hi,
I started trying out the Use Case diagram today. I find the graphics a bit rough, but otherwise the workflow is much more usable than Microsoft Visio.
I have a suggestion: when an association is made from an actor to a use case, the line is drawn pointing towards the center of the oval. The result is awful when the line is coming in at a sharp angle. I would suggest joining the line to the perimeter point that would result in the shortest line instead. In my opinion that will be good enough for over 95% of the cases.
The same applies at the actor end. It would improve the graphics presentation quite dramatically.
Currently there is a mechanism for breaking the line in the middle, which allows me to adjust the appearance to a large extend. However the problem is that when I move the actor or the oval, the break point stays – and I usually find it easier to delete and redo the line than adjusting the break points.
Actually think of it, it would be very easy to move all the break points in the middle together with the end points. It is a simple linear interpolation; and would solve half my grievances instantly.
It is a very usable product at it is. Thanks for the great work guys.
Regards,
YeeThank you Yee, I have filed your enhancement suggestions with the UML team, management will determine down the road what will make it into our subsequent releases.
Ok my first impressions after a day of experimenting.
1) Where is the documentation? The database explorer perspective has an entire section devoted to it. Where is this for the UML? Searching for UML in the help window returns only two documents. A legal notice and the release notes which simply state that the uml feature exists.
2) Printing. When working with large disign docs like this you need fine grained control over printing. Such as what zoom level to print at, and print preview that will show how the document will be split accross pages.
3) how do you export to XMI?
Now for some good stuff.
1) Reverse Engineering seemed to pull classes accurately, and it properly represented associations.
2) The auto layout feature did a good job of laying out a useable view with a fairly complex model, 100+ classes.
Haven’t yet tried starting a project from scratch with the tool so can’t coment on useablitiy there.
@emcien wrote:
1) Where is the documentation? The database explorer perspective has an entire section devoted to it. Where is this for the UML? Searching for UML in the help window returns only two documents. A legal notice and the release notes which simply state that the uml feature exists.
There is a UML Quickstart that has already been written, however it still has several internal edits to go through before it is publishable. So, UML Documentation is on the way.
Overall I like this release very much. However, I’ve been using Omondo’s EcllipseUML for quite a while and I really like the fact that they do live synchronization between code edits and diagram edits — not generation steps required. This capability is really rare in the industry, usually costing thousands of dollars. But it’s worth it. This is important to me because it directly affects my productivity. Since MyElcipse UML seems to be based on Argo UML I’m guessing this very important capability is not on the horizon.
Since MyElcipse UML seems to be based on Argo UML I’m guessing this very important capability is not on the horizon.
Don’t jump to conclusions too soon, we are *extremely* dedicated to our UML tooling, what you are using now is our 1.0 introduction of the tool, there is a long road ahead of us full of enhancements. One of the big targets for 4.1 (if it takes too long, will get pushed to 5.0) is real-time synchronization like you are speaking of with existing models with no need to overwrite or regenerate files. Our UML team has been evaluating this addition immediately after 4.0 shipped so all the things you said you wanted, will be in MyUML eventually, our initial target is 4.1 (I don’t have an ETA for the 4.1 release yet)
Didn’t have too much time to look into UML, but what literally kills my eyes is the small & antialiased == unreadable font in the class diagam for example. Please is there any way to change the size and get rid of the fuzzy ‘feature’ which makes my eyes try refocusing constantly? Thanks a lot.
what literally kills my eyes is the small & antialiased == unreadable font in the class diagam for example.
We realize this is a problem, a good workaround (and what I prefer personally) is to bump your default text size from 8 to about 10 or 11, then everything looks nice and sharp. Additionally we are looking at adding anti aliasing paramterization controls to the UML preferences so people can control this in the future.
Please is there any way to change the size and get rid of the fuzzy ‘feature’ which makes my eyes try refocusing constantly?
I would strongly suggest you increase the size, it looks much better and is easier to read. As far as turning off the fuzzy (antialiasing) there isn’t a setting for that yet but we are hoping to add those controls soon.
Thanks, increasing size to 12 and changing font to Century Regular made it almost bearable, but I’m looking forward to be able to switch off the antialiasing, because then small fonts can be used nicely and lots of precious screen space can be saved. I’m also looking forward very much to be able to use the ‘porthole’ widget mentioned above;)
