[Mufasa]

@yeecn wrote:

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.

…

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,
Yee

My wishes on line drawing:

Be able to delete break points
Ability to attach line end points to the attributes they reference (instead of just pointing at wherever is conveniant around the class box)

Mufasa

[Brian Janes]

Is there a stauts update on enabling the initial value to appear on the class diagram?

[Peter Pilgrim]

Hello

It is Peter Pilgrim again.

I have come back to the UML side of thing in MyEclipse 4.0.3 ( I haven’t upgrade to latest)

Using the UML Static Class diagrams. I found that there are speed problems with the
graphics on Windows XP. There is a latency (animation detail) with move a selected
bunch of classes around the canvas.

I am using the UML Static Class diagram mainly for documentation. For true work
I would like to see:

1) A speed upgrade. I dont know if SWT / FACES can get you access to accelerated
graphic driver of the native chip
2) Allow the user to changing the print resolution of output graphics e.g 72dpi is
great for the web, but 144dpi and 360dpi are required for books and large scale
prints.
3) I created lots of mini UML Static diagrams and I am really the UML Designer
allows this (thank you) to document a package that has dozens of classes and
interfaces. I created a part one with a few classes for a package foo, then
created part two and three and so on.

I noticed that if I drag interface class from the Package Explorer in to the
UML canvas, the UML reverse gen tool does not automatically at the
generalisation to the classes already in the diagram. Also I can add the
generalisation manually latter on. Instead I have to the use
“New Realization” arrow to show it. This is not right for classes
that implement interfaces? I should be able to use generalisation.

4) Please add a jump to source code link in the context menu of the UML
if you are not going to supply through double-clicking, or ALT
clicking or otherwise.

Thanks for a great product

Hopefully you a
Peter Pilgrim

http://jroller.com/page/peter_pilgrim

[Riyad Kalla]

Peter I sent your suggestions to the UML team to digest, thank you for taking the time to give us this feedback.

[Kapil Kapre]

@peter_pilgrim wrote:

I noticed that if I drag interface class from the Package Explorer in to the
UML canvas, the UML reverse gen tool does not [1] automatically at the
generalisation to the classes already in the diagram. Also I can add the
generalisation manually latter on. Instead I have to the use
“New Realization” arrow to show it. This is not right [2] for classes
that implement interfaces? I should be able to use generalisation.

#1 Could you briefly describe the class & i/f stub info so we can replicate the issue here.

#2 AFAIK, Generalization is for denoting inheritance, and realization is for implementation of i/f (UML-> Java OO). Or maybe I have misunderstood what you were trying to say.

Thanks,
Kapil

[Peter Pilgrim]

;; This buffer is for notes you don’t want to save, and for Lisp evaluation.
;; If you want to create a file, visit that file with C-x C-f,
;; then enter the text in that file’s own buffer.

The speed problem is only apparently at zoom-out levels e.g < 100%.
I notice that MyEclipse does full rendering of the UML classes when they
are being dragged around the canvas.

If you are moving a UML class at a zoomed out magnification, then the
rendering of the animation does not happen. First when you click the mouse
the canvas flickers ( a missing double buffer operation on the redraw)
and then you drag the selected UML classes around to the destination
and relase the mouse button, and then does a redraw happens.

A zoom out levels , especially when dragging around UML classes etc
you should consider outlined or wire-frame rendering instead.

Ok the other problem, suppose I have the class hierarchy

interface A { /* … */ }

class B implements A { /* … */ }

class C extends B { /* … */ }
class D extends B { /* … */ }
class E extends C { /* … */ }
class F extends E { /* … */ }
class G extends E { /* … */ }

In the package explorer if I drag B,C,D,E,F,and G on to the UML
class diagram canvas, all the classes are correctly drawn with
the generalisations in the right place and direction.

If I later decide to drag the ancestor interface A on the screen
then I never see the MyEclipse create the generalisation / realisation
automatically .

[Kapil Kapre]

Peter,
I reproduced the bug quite easily with the steps you provided. We had added support for auto-creation of realization as well as generalizations. The generalizations support should still be working. I have filed this internally and it should be rolled out with the next release.
Kapil

[Peter Pilgrim]

I downloaded MyEclipse GA 4.1 for Windows.

It would be nice in the UML static class diagram or all diagrams to see actual zoom percentage 100%.
Could you put a label widget next to zoom-in zoom-out icons or somewhere on the *.umr panel?

When I am in < 100% magnification the flickering in a lot more apparent in this version.
Must be a rendering bug in the pipeline. The graphics is doing too much work spending too time
in scaling down / up somewhere.

Strangely in zoom-in mode magnification > 100% I can drag classes around slightly slower, but
it the animation is still reasonable smooth.

[Kapil Kapre]

jeremiah,
Simply create a new object in the Coll. Diagram and right click the base list-control and create a new “base” on which the object is based. this base is not part of any diagram and you can drag this class into any Class diagram using the outline view. (package – centric). You can also create an object from an existing classifier using the “/object-name : existing-classifier-name” way of entering the objects name. Hope that helped.
Kapil

[DANTEUK]

@support-rkalla wrote:

Feature request: autogenerate accessor methods (get…, set…) as operations when creating class attributes.

It’s too late, that is already being added 😉

Was it added to the requested feature list, or was it implemented?

If it was implemented, how to use it?

Waldemar

[Kapil Kapre]

He meant added to the feature list. I’ll add your +1 to bump up the priority.

[Author]

Posts