MiG InfoCom MiG Calendar JavaBeans Guide User Manual
Page 13
MiG InfoCom AB
theme though, this has to be set manually if the default look
doesn’t fulfills the requirements. It is easy to tweak and build
in functionality but at the expense of extensibility.
JavaBean Approach (Preferred from v6.0)
This approach is what this guide is about. It means using
special wrapper JavaBeans that are delivered with the
component and visually configure these using your favorite
GUI tool, just like is commonly done in Visual Basic, Delphi or
Visual C++. Examples of such tools are:
netBeans –
JFormDesigner –
JDeveloper –
JBuilder –
Eclipse with Swing-Designer –
and
This is the leanest of the different approaches when it comes
to the developer experience level. It is easy to get started
and still as flexible. It is still possible to get to the core
classes and configure and tweak those.
The wrapper layer introduced by the JavaBeans is extremely
thin and does not affect runtime speed or memory
requirements.
This approach is the preferred one from v6.0 and is the
interface that will get most updates in future releases.
How the Java Bean Classes Relate to the
Core Component
The JavaBean classes wrap the core classes and present a
new surface that is optimized to act as visual JavaBean
components that can reside in a GUI tool’s component
palette. This makes it a lot like the Themed approach.
There is also a core level in the component that is accessible
to the developer. It is more code-centric and more flexible
since the JavaBean framework imposes some, but not many,
limitations. This core level is still accessible if the JavaBean
MiG Calendar JavaBeans Guide
Page 13 / 45