UML Plugin

Hello Alexander,

This is only some basic stub with no real functionality yet. We don't currently
know how much functionality we'll be able to implement before the Diana release.
We'll obviously start with class diagrams, but even for this we can't promise
that the features will be stable and finished enough to be included in the
release.

I recently saw there is a UML plugin bundled with Diana buids
(plugins\Uml\lib\uml-support.jar). I can't seem to find any interface
element linked to it.

Does anyone knows what's with it?
Does this mean we will have UML support in Diana? At least class
diagrams?
My wish would come true:
http://www.jetbrains.net/jira/browse/IDEA-18576

P.S. Sequence diagrams are also helpfull, but class diagrams for
starters would be very cool.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

Oooooohhhhh! A nice, lean class diagram editor would be nice:
Here's what I would like to do most:

• Start with a single class - just one node in the diagram

• Initially show all fields of the Java class as attributes in the diagram

• Also show superclass and implemented interfaces in the class node itself

• Have an easy way to toggle that "inline" display for individual parts, so that you can easily switch the representation from attribute to association to another class node or from inline super class name display to UML inheritance notation.

• Have a command to add all sub-classes of a class to the diagram.

• Tight integration with the source code editor

• PERSISTENT diagrams (unlike the ER diagram where all graphical edits are lost as soon as you close the diagram)

That way you would be able to interactively explore the class structure visualizing the result as you go.
OTOH you would be able to get exactly those diagrams for documentation of certain parts of your app that you really need.

Sorry, I know it's very early, but I wished for such a feature for a long time now.

I am looking for such uml plugin.I need that functionality very much.

Totally agree with Stephen.

Plus :

- only do class diagrams, the other diagrams are useless, so don't lose time on them (yes even the sequence one, which i hate).
- this must only work by doing something like add this class to diagram or "synchronize from code" (like in Together)
- don't let people create a class from the diagram that would generates code...ever. This is just...bad.
- Don't forget to add non-generic collection support via javadoc (like in Together

Gilles

Don't you want real annotations instead of comment tags?


Randall Schulz

Ah, my favorite most hated subject...UML ;)

Oooooohhhhh! A nice, lean class diagram editor would be nice:

If it's really lean, there might be some value in it..

• Start with a single class - just one node in the diagram

• Initially show all fields of the Java class as attributes in the diagram

I'm pretty sure I disagree...I've just see too many class diagrams showing all 40 boolean/integer/String attributes, filling half an A4 page with just one class node already. I would say that a required feature (for me) is to hide most of the low-level mess. Just show me the relations to other classes.

It does not need to be hidden by default, but I'd really like a toggle that I can set once, and that is remembered from that point on.

• Also show superclass and implemented interfaces in the class node itself

• Have an easy way to toggle that "inline" display for individual parts, so that you can easily switch the representation from attribute to association to another class node or from inline super class name display to UML inheritance notation.

Strongly +1 (in addition to having an option to hide all dumb scalar attributes, as mentioned above).

• Have a command to add all sub-classes of a class to the diagram.

• Tight integration with the source code editor

Details please...we're talking about regular reference actions, right (Ctrl-B, Shift-F6, Ctrl-Alt-F7, etc)?

• PERSISTENT diagrams (unlike the ER diagram where all graphical edits are lost as soon as you close the diagram)

I'm pretty sure I disagree, let me explain why:

• it's mostly needed for larger diagrams - which kind of conflicts with the simple & lean motto.

• I'd prefer some work to go into making the generated diagrams better as a start - there's a log of low hanging fruit here:

http://www.jetbrains.net/jira/browse/IDEA-18849
http://www.jetbrains.net/jira/browse/IDEA-18790
http://www.jetbrains.net/jira/browse/IDEA-18789

Taras

Unfortunately, not everybody can use JDK1.5+ :(

JDK 1.4 is completes its end-of-life transition as of October 30th of this year. If you haven't transitioned to 1.5 or 1.6 by now, you are taking quite a risk. I can't imagine any tool vendor doing any work targeting it at this stage.

--Dave Griffith

I'd like to agree with you, but some editors (eg IBM) are still using 1.4 in some of their most highlighted products (eg Websphere Portal)

Personally, a strong -1

I want something that can show a simple diagram easily, not a tool that will modify source (even if only inserting javadoc/javadoc-like tags).

I would agree with Taras on his point. The tool shouldn't alter the source code.

I never said it would generate code. I said so implicitely in my post about not letting people create classes from diagram. In fact, don't alter the code at all.
But for people using jdk1.4 without annotations & generics, the only way to express a one-to-many relationship (with Collection not arrays) is javadoc.

Hi Dmitry,

Is there a way to access even rough functionality on UML Plugin?

Thanks,
Jon

not that it would be hidden :)

position cursor on package statement
press CTRLSHIFTA (GotoAction)
enter "*uml" and choose "Show Uml Class Diagram"