MiG InfoCom MiG Calendar JavaBeans Guide - Manual (Page 12)

MiG InfoCom AB
Visual Editor works with MiG Calendar. It should be noted
though that VE doesn't have the possibility to have custom
beans on its JavaBean palette. You will have to "Choose
Bean.." for every bean you want to add, for every time. This
makes Swing-Designer or JFormDesigner a better choice for
Eclipse.
Bean Builder 0.6 alpha & Bean Box 1.1
These tools are reference tools provided by Sun. They are
not being maintained anymore and are very unfinished and
buggy. MiG Calendar does work to some degree in these
tools but for instance Bean Box does not accept null property
values and that we can't work around.
Other IDEs
If they support visual JavaBeans they will support the MiG
Calendar beans as well, however they are untested.
MiG Calendar Approaches
There are three main approached to choose from when
developing with the MiG Calendar component, this JavaBean
approach is one of them. What approach to use depends on
the expected complexity of the application to be created,
developer experience level and demands on flexibility.
Normal or “Core” Approach
This involves creating for instance DefaultDateArea,
DateAreaContainer and XxxHeader classes manually in code
and configuring these using the methods on them. This is the
most flexible approach but also the most code-centric which
means that the demands on the developer’s abilities are
higher than any of the other approaches.
The core approach enables all of the build in flexibility of the
MiG Calendar component. The other approaches can also
access this core flexibility, there are noting preventing that,
but parts of the core might be preconfigured.
Themed Approach (deprecated in 6.0, but it works)
This involves using the Theme Editor to visually, much like a
normal GUI editor, build a single date area with surrounding
headers. How the activities should look can not be set in the
MiG Calendar JavaBeans Guide Page 12 / 45