Deployment view

A deployment view may contains nodes, artifacts and deployment diagrams in any order :


The menu appearing with a right mouse click on a deployment view in the browser is something like this, supposing it is not read-only nor deleted :

Menu : edit

The stereotype of a deployment view doesn't have a special meaning for BOUML.

The editor button visible above and associated here to the description, allows to edit the description in an other window, or to call an external editor (for instance Xcoral) specified through the environment dialog. Note that this external editor have to create an own window, its parameter is the pathname of the file containing the description, its execution is done in parallel with BOUML which looks each second at the file contents to get the new definition until the dialog is closed (I do not like very much this polling but this works even QT isn't compiled with the thread support).

Menu : edit drawing settings

This dialog allows to specify how the deployment diagrams must be drawn by default.

Menu : delete

The menu entry delete is only present when the class view is not read-only.

Delete the deployment view and all its children, and all the representation of them in the opened diagrams. After that it is possible to undelete them (from the browser) until you close the project : obviously the deleted items are not saved !

Menu : mark

See mark

Menu : lock / unlock sub classes and artifacts

It is possible to put a lock on a class or an artifact. A locked element cannot be modified editing it nor roundtriped, and there is no code generation for it. When you put/unput a lock on a class it is also put/unput on its sub classes and on the associated artifact and all the other classes associated to this artifact and their sub classes. When you put/unput a lock on an artifact it is also put/unput on the associated classes and their sub classes. It is also possible to put/unput locks recursively from a package, a class view and a deployment view.

Menu : tools

The menu entry tool not present above is present in case at least a plug-out may be applied on the component view. The selected tool is called and applied on the current deployment view.

Previous : component view

Next : use case