See: Description
Package | Description |
---|---|
org.netbeans.api.visual.action |
This package contains
ActionFactory class which is factory of all built-in widget-actions provided by the library. |
org.netbeans.api.visual.anchor |
This package contains
Anchor interface which is used by ConnectionWidget for defining its source and target point. |
org.netbeans.api.visual.animator |
This package contains
SceneAnimator classes which is used for controlling animations on a scene. |
org.netbeans.api.visual.border |
This package contains
Border interface which is used for supplying a border graphics for a widget. |
org.netbeans.api.visual.export |
This package contains the class necessary to export a
Scene to an
image file and get the coordinates from the exported image to create an HTML
image map |
org.netbeans.api.visual.graph |
This package contains built-in graph-oriented models.
|
org.netbeans.api.visual.graph.layout |
This package contains built-in graph-oriented layout algorithms.
|
org.netbeans.api.visual.laf |
This package contains
LookFeel class with style definition for colors and borders. |
org.netbeans.api.visual.layout |
This package contains
Layout interface which defines a widget-layout. |
org.netbeans.api.visual.model |
This package contains
ObjectScene class which is a scene with ability to register model-objects with widgets on the scene. |
org.netbeans.api.visual.print |
This package contains a single class
ScenePrinter used to print
a Scene according to various constraints. |
org.netbeans.api.visual.router |
This package contains
Router interface which defines a router for ConnectionWidget . |
org.netbeans.api.visual.vmd |
This package contains a VMD visualization style.
|
org.netbeans.api.visual.widget |
This package contains
Widget class. |
org.netbeans.api.visual.widget.general |
This package contains general high-level widgets.
|
VisualLibraryAPI
The API provides a set of reusable pieces - widgets. By composing them you are creating a visualization. Each widget has various properties including layout, border, assigned actions, ... The library contains a set of pre-defined widgets that can be extended. All pluggable pieces are declared as interfaces or abstract classes - WidgetAction, Anchor, AnchorShape, PointShape, Animator, Border, GraphLayout, LookFeel, Layout, SceneLayout, Router, CollisionsCollector. Also they all have their built-in implementation.
The old layout was improved in a way that nodes in a subtree are vertically aligned by the center of the super nodes. Also the possibility of overlapping in the old layout was removed by adding an approach based on the envelope of the (sub)trees. The second improvement was done by adding the possibility of minimizing the gaps between nodes. If a tree was very wide, the old layout used a lot of space. To prevent this the new algorithm with the possibility of minimization of gaps is based on the envelope. Therefore subtrees move as close together as possible.
ActionFactory.createContiguousSelectAction
creates contiguous selection action.
ContiguousSelectProvider
provides logic for selection action.
ContiguousSelectEvent
is an event for ContiguousSelectProvider
.
InplaceEditorProvider.TypedEditorController
contains getEditorInvocationType()
which returns invocation type
(MOUSE
, KEY
, CODE
).
There are certain graphs which demand that the hierarchical layout be inverted (target above source). One such graph would be a UML class diagram. For this reason I propose adding a static call to the GraphLayoutFactory to allow for an "inverted" flag to be provided. The default behavior sets inverted to false. Another call to be added the the GraphLayoutFactory would include "inverted", "horizontal spacing", and "layer spacing" (vertical). The default all remain the same.
The resource table will allow for a central location for properties like font, color and paint objects. The resource table will help enforce an applications look and feel. When a property is updated in the resource table, all interested widgets will be notified of the change. The notification allows widgets to update when a resource property changes.
See documentation for complete set of use-cases.
The sources for the module are in the NetBeans Mercurial repositories.
No. Just set a normal project dependency on org.netbeans.api.visual (spec no.: 2.0) module.
Read more about the implementation in the answers to architecture questions.
Built on November 24 2014. | Portions Copyright 1997-2014 Sun Microsystems, Inc. All rights reserved.