[julien]

I have started to use the omondo UML plug-in for Eclipse ( 1.1.8 ). I am having a problem with auto-layout. Whenever I open a UCD file containing a class diagram, it is subjected to an auto-layout which is beyond my control. The result of the auto-layout action is a virtually illegible diagram which I have to layout manually - and of course I lose that when I close the diagram. I have searched docs and google, but can't find a solution to this problem. All I want to do is disable auto-layout. Is there a way of doing this?

Cheers,
Tim

[julien]

I think you have created a diagram without a package context. This diagram is a root diagram designed to overview all packages in the project. It is updated and layouted automatically when you open it. In the next build, it is possible to show the dependency bewteen packages in this diagram if it is activated in the Preferences.

In general, for you application model, you should create a package in the root diagram and open it with the context menu of the package: open -> .ucd ou double click on the pakcage figure. This new diagram (or package diagram) is not updated and layouted automatically once it is created.

julien
omondo

[jean-eric]

[quote="julien"]I think you have created a diagram without a package context. This diagram is a root diagram designed to overview all packages in the project. It is updated and layouted automatically when you open it. In the next build, it is possible to show the dependency bewteen packages in this diagram if it is activated in the Preferences.

In general, for you application model, you should create a package in the root diagram and open it with the context menu of the package: open -> .ucd ou double click on the pakcage figure. This new diagram (or package diagram) is not updated and layouted automatically once it is created.

julien
omondo[/quote]

Hi Julien,

I'm actually reverse-engineering a framework composed of quite a few packages drawing a complex dependency network between them. In such a context, several class (package actually) diagrams are needed to break down the rendering of the dependency graph into viewable parts. HOW DO TO IT ?!...

I tried to use your "trick" :
1> In the root class/package diagram (which takes a few minutes to load and layout, cause of the numerous packages and classes....), I created a "dummy" package".
2> I created a first ucd diagram in the "context" of this dummy package, which I populated with a few ones from the project.
3> I resized the boxes and reorganised the display of the links in the diagram. Saved the diagram, quit it's editor, and reloaded the diagram.

Guess it :
* The system does not recursively load a whole bunch of classes in the project for just displaying the diagram. (Cool : that's a lot of time saved !...).
* BUT boxes resizing and links reorganization is just wasted. Rhaaa !...

So, I may have been wrong somewhere in the process of applying your "trick" (tell me where...). However :
1> why "root diagrams" (should) overview ALL packages in the project ? (so, whatever how many "root" diagrams per project, they will all display the whole bunch of packages in the project !...)
2> are updated and re-layouted automatically when opened, EVEN when there is NO NEED to do so (: no updates !...) ?

Point 1 does not make sense to me. And point 2 indicates clearly that something is wrong . Package diagrams should behave the same way and afford the same ease of use that class diagrams. They just don't. Any hope that they will in a near future ?