JViews graphic objects do not derive from java.awt.Component or javax.swing.JComponent classes

Article ID: 2179
Last updated: 28 May, 2018
Article ID: 2179
Last updated: 28 May, 2018
Revision: 3
Views: 671
Posted: 29 Dec, 2008
by Dean J.
Updated: 28 May, 2018
by Gargani A.

Question

Why JViews graphic objects do not derive from java.awt.Component or javax.swing.JComponentclasses?

Answer

Component or 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 Component or JComponent from a Prototype and that it is possible to create a graphic object from a Component or JComponent via IlvComponentGraphic and IlvJComponentGraphic.

This article was:   Helpful | Not helpful
Report an issue
Article ID: 2179
Last updated: 28 May, 2018
Revision: 3
Views: 671
Posted: 29 Dec, 2008 by Dean J.
Updated: 28 May, 2018 by Gargani A.

Others in this category