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

MiG InfoCom AB
MinimumPopupSize, PreferredPopupSize and
MaximumPopupSize together with the preferred size of the
DateAreaBean itself if they are are null.
You can listen for the same events as you can on a normal
DateAreaBean which includes listening for selection of dates,
activity move events and more generic interaction events.
How to add hooks for this is depending on your GUI
environment, but you usually can do this by right-clicking the
component.
The rest of the properties for DatePickerBean are pretty
straight forward and will not be reiterated here. For more info
on these properties please look at the API JavaDoc for the
bean.
Advanced Topics
The visual beans explained in this document are very flexible
but does not contain GUI properties that configures all
functionality to build a complete application. You normally
will need to do some manual coding to for instance:
• Create/update/remove activities and the category tree
to/from a backing store (e.g. a date base).
• Colour code activities for different categories.
• Add custom decorations to a date area or header.
• Add tooltips to activities in the date area.
• Set runtime user preferences for the component.
• Even more advanced things as exchanging core
component parts and logic.
Most of these tasks are trivial to do but it has to be done in
normal code and can not be configured visually in a GUI tool.
First there are a few key classes that you need to know how
to get a hold of and what they do.
DateAreaContainer – The main and most important
component in the framework together with its child
component; the DefaultDateArea. The DateAreaBean is
actually a sub class of the DateAreaContainer. It keeps
track if the DefaultDateArea and the headers around it as
well as custom JComponents in between these. It also
MiG Calendar JavaBeans Guide Page 37 / 45