Browse by category:
|| | ||
Why JViews graphic objects do not derive from java.awt.Component or javax.swing.JComponentclasses?
JComponent classes are designed for standard GUI (buttons, list, and so on).
They are designed for this purpose, and are far too heavy in memory to display a basic representation like a rectangle. Although it is possible to base a toolkit on these classes, it will be impossible to obtain the same performances (speed and memory) that we have in JViews. Also, these classes do not provide the ability to display and interact at several zoom levels in several views. Nearly all the toolkits in the market today are following the same path.
Note that it is possible to generate a
JComponent from a
Prototype and that it is possible to create a graphic object from a
|Internationalization in Composer sample||Notification when a subnetwork is collapsed or expanded|