The calendar component provides the features you need to implement calendar-related functions such as creating activities in daily, weekly, monthly or list view. It features a customizable toolbar that can be used for switching views. It has configurable start of the week and start of the day functions. Like other ADF Faces components, it supports skinning in order to customize its style and appearance.

You can create popups by inserting them into the calendar facets to add more functionality. You can also implement the calendar so the user can drag and drop activities from one area to another within the calendar.

The calendar uses the CalendarModel class to display the activities for a given time period. You must create your own implementation of the model class for your calendar. If your application uses the Fusion technology stack, you can create ADF Business Components over your data source that represents the activities, and the model will be created for you. You can then declaratively create the calendar, and it will automatically be bound to that model. See Using the ADF Faces Calendar Component in Developing Fusion Web Applications with Oracle Application Development Framework.

If your application does not use the Fusion technology stack, then you create your own implementation of the CalendarModel class and the associated CalendarActivity and CalendarProvider classes. The classes are abstract classes with abstract methods. You must provide the functionality behind the methods, suitable for your implementation of the calendar. See Creating the Calendar.

You may find it helpful to understand other ADF Faces features before you implement your calendar component. Additionally, once you have added a calendar component to your page, you may find that you need to add functionality such as validation and accessibility. Following are links to other functionality that calendar components can use.

• Client components: Components can be client components. To work with the components on the client, see Using ADF Faces Client-Side Architecture .

• JavaScript APIs: All components have JavaScript client APIs that you can use to set or get property values. See the JavaScript API Reference for Oracle ADF Faces.

• Events: Components fire both server-side and client-side events that you can have your application react to by executing some logic. See Handling Events.

• You can display tips and messages, as well as associate online help with a calendar component. See Displaying Tips, Messages, and Help.

• You may want other components on a page to update based on selections you make from a calendar component. See Using the Optimized Lifecycle.

• You can change the appearance using skins. See Customizing the Appearance Using Styles and Skins.

• You can make your components accessible. See Developing Accessible ADF Faces Pages.

• Instead of entering values for attributes that take strings as values, you can use property files. These files enable you to manage translation of these strings. See Internationalizing and Localizing Pages.

• You can create popups for additional functionality. For information about using these events to provide additional functionality, see Adding Functionality Using Popup Components.

• If your application uses ADF Model, then you can create automatically bound forms using data controls (whether based on ADF Business Components or other business services). See Creating a Basic Databound Page in Developing Fusion Web Applications with Oracle Application Development Framework.

The calendar component must be bound to an implementation of the CalendarModel class. The CalendarModel class contains the data for the calendar. This class is responsible for returning a collection of calendar activities, given the following set of parameters:

• Provider ID: The owner of the activities. For example, you may implement the CalendarModel class such that the calendar can return just the activities associated with the owner currently in session, or it can also return other owners' activities.

• Time range: The expanse of time for which all activities that begin within that time should be returned. A date range for a calendar is inclusive for the start time and exclusive for the end time (also known as half-open), meaning that it will return all activities that intersect that range, including those that start before the start time, but end after the start time (and before the end time).

A calendar activity represents an object on the calendar, and usually spans a certain period of time. The CalendarActivity class is an abstract class whose methods you can implement to return information about the specific activities.

Activities can be recurring, have associated reminders, and be of a specific time type (for example, TIME (with a start and end time) or ALLDAY). Activities can also have start and end dates, a location, a title, and a tag.

The CalendarProvider class represents the owner of an activity. A provider can be either enabled or disabled for a calendar.

1. In the Components window, from the Data Views panel, drag a Calendar and drop it onto the JSF page.

   Tip:

   The calendar component can be stretched by any parent component that can stretch its children. If the calendar is a child component to a component that cannot be stretched, it will use a default width and height, which cannot be stretched by the user at runtime. However, you can override the default width and height using inline style attributes. For information about the default height and width, see Configuring the Calendar Component. For information about stretching components, see Geometry Management and Component Stretching.

2. Expand the Calendar Data panel of the Properties window, and enter an EL expression for Value that resolves to the managed bean that extends the CalendarModel class.

1. In the Properties window, view the attributes for the calendar. Use the Help button to display the complete tag documentation for the calendar component.
2. With the calendar component selected, expand the Common section of the Properties window, and set the following:

   • AvailableViews: Select the available views. The value can be one of or a combination of the following:

     • all

     • day

     • week

     • month

     • list

     If you want to enter more than one value, enter the values with a space between. For example, if you want the calendar to use day and week views, you would enter the following:

     day week
     

     Note:

     If all is entered, then all views are available, regardless if one is left out of the list.

     The corresponding buttons will automatically be displayed in the toolbar, in the order they appear listed for the availableViews attribute.

     Note:

     In order to handle an overflow of tasks for a given day in the month view, if you enter month and do not also enter all, then you must also enter day.

   • View: Select the view that should be the default when the calendar is displayed. Users change this value when they click the corresponding button in the calendar's toolbar. Valid values are:

     • day

     • list

     • month

     • week

   • StartDayOfWeek: Enter the day of the week that should be shown as the starting day, at the very left in the monthly or weekly view. When not set, the default is based on the user's locale. Valid values are:

     • sun

     • mon

     • tue

     • wed

     • thu

     • fri

     • sat

   • StartHour: Enter a number that represents the hour (in 24-hour format, with 0 being midnight) that should be displayed at the top of the day and week view. While the calendar renders all 24 hours of the day, the calendar will scroll to the startHour, displaying this hour at the top of the view. The user can scroll above that time to view activities that start before the startHour value.

   • ListType: Select how you want the list view to display activities. Valid values are:

     • day: Shows activities only for the active day.

     • dayCount: Shows a number of days including the active day and after, based on the value of the listCount attribute.

     • month: Shows all the activities for the month to which the active day belongs.

     • week: Shows all the activities for the week to which the active day belongs.

   • ListCount: Enter the number of days' activities to display (used only when the listType attribute is set to dayCount).

     Figure 17-5 shows a calendar in list view with the listType set to dayCount and the listCount value set to 14.

     Figure 17-5 List View Using dayCount Type

     
3. Expand the Calendar Data section of the Properties window, and set the following:

   • ActiveDay: Set the day used to determine the date range that is displayed in the calendar. By default, the active day is today's date for the user. Do not change this if you want today's date to be the default active day when the calendar is first opened.

     Note that when the user selects another day, this becomes the value for the activeDay attribute. For example, when the user first accesses the calendar, the current date is the active day. The user can select another day to be the active day by clicking on the day link in the month view. The active day also changes when the user selects a different month or year.

   • TimeZone: Set the time zone for the calendar. If not set, the value is taken from AdfFacesContext. The valid value is a java.util.TimeZone object. By default, time is displayed based on the formatting-locale parameter in the trinidad-config.xml file. See Configuration in trinidad-config.xml.

4. Expand the Appearance section of the Properties window and set the following:

   • AllDayActivityOrder: Control the display of all-day activities by specifying a list of strings that correspond to tags on the activities. Activities will be grouped by tags and display in the order specified by allDayActivityOrder. Activities without any tags, or whose tags are not listed in allDayActivityOrder, will display together in a default group. Within each group, the calendar displays rows with the most activities first. For example, if allDayActivityOrder = holiday absence, then all-day activities will be displayed in this order:

     • Activities with the holiday tag

     • Activities with the absence tag

     • Activities with no tags

     Figure 17-6 shows a calendar with allDayActivityOrder set to holiday absence. Activities tagged holiday appear at the top, followed by activities tagged absence. The remaining activities are then displayed; rows with the most activities appear first.

     Figure 17-6 Calendar Display Using allDayActivityOrder

     

   • HourZoom: Set the zoom factor for time cells to be displayed in the calendar. The zoom factor applies to the height of the hour in day or week view. Valid values are auto or a non-zero positive number (including fractions). By default, the value is 1.

     A value greater than 1 will scale up the calendar by the specified factor. For example, a value of 2 will scale up the calendar by 200%. A value of 0.5 will scale down the calendar by 50%. When set to auto the calendar will scale by an optimal factor for best viewing, ensuring that tightly scheduled non-overlapping activities will not display overlapping each other for lack of vertical space.

   • TimeSlotsPerHour: Set the number of time slots to display per hour in day or week view. Time slots are minor divisions per hour, indicated by a dotted line splitting the hour into shorter intervals. For example, the value 4 will render four time slots per hour, measuring 15 minutes each. Valid values are auto or a non-zero positive whole number. By default, the value is auto.

     When set to auto the calendar will use the skin property -tr-time-slots-per-hour. For example, af|calendar {-tr-time-slots-per-hour: 4} will render a minor division (dotted line) at 15-minute intervals.

5. If you want the user to be able to drag and resize the calendar regions, expand the Other section of the Properties window and set the splitterCollapsed and splitterPosition attributes. The splitter separates the all-day and timed activities areas in the day and week views of the calendar ( it has no effect in month and list views). By default splitterCollapsed is false, which means that both the all-day and timed activities areas are displayed. When the splitter is collapsed (splitterCollapsed = true), the all-day activities area is hidden and the timed activities area stretches to fill all available vertical space. The splitterPosition attribute specifies the initial height in pixels of the all-day activities area; the timed activities area gets the remaining space. Valid values are auto or a non-zero positive whole number. By default, the value is auto. For information, see the tag documentation for the calendar component.
6. If you want the user to be able to drag a handle on an existing activity to expand or collapse the time period of the activity, then implement a handler for CalendarActivityDurationChangeListener. This handler should include functionality that changes the end time of the activity. If you want the user to be able to move the activity (and, therefore, change the start time as well as the end time), then implement drag and drop functionality. See Adding Drag and Drop Functionality to a Calendar.

The calendar has two events that are used in conjunction with facets to provide a way to easily implement additional functionality needed in a calendar, such as editing or adding activities. These two events are CalendarActivityEvent (invoked when an action occurs on an activity) and CalendarEvent (invoked when an action occurs on the calendar itself). For information about using these events to provide additional functionality, see Adding Functionality Using Popup Components.

The calendar also supports events that are fired when certain changes occur. The CalendarActivityDurationChangeEvent is fired when the user changes the duration of an activity by making changes to the start or end time. The CalendarDisplayChangeEvent is fired when the value of a display attribute changes. For example, if a user changes the view attribute from day to month, the calendar is rerendered automatically because the calendar component becomes a partial page rendering (PPR) target, triggering an immediate refresh.

1. In the Structure window, expand the af:calendar component node so that the calendar facets are displayed, as shown in Figure 17-7.

   Figure 17-7 Calendar Facets in the Structure Window

   
   Description of "Figure 17-7 Calendar Facets in the Structure Window"
2. Based on Table 17-1, create popup components in the facets that correspond to the user actions for which you want to provide functionality. For example, if you want users to be able to delete an activity by clicking it and pressing the Delete key, you add a popup dialog to the activityDelete facet.

   To add a popup component, right-click the facet in the Structure window and choose Insert inside facetName > Popup.

   For information about creating popup components, see Using Popup Dialogs, Menus, and Windows.

   The following example shows the JSF code for a dialog popup component used in the activityDelete facet.

   <f:facet name="activityDelete">
     <af:popup id="delete" contentDelivery="lazyUncached">
       <!-- don't render if the activity is null -->
       <af:dialog dialogListener="#{calendarBean.deleteListener}"
                  affirmativeTextAndAccessKey="Yes" cancelTextAndAccessKey="No"
                  rendered="#{calendarBean.currActivity != null}">
         <af:spacer height="20"/>
         <af:outputText value="Are you sure you want to delete this activity?"/>
         <af:panelFormLayout>
           <af:inputText label="Title" value="#{calendarBean.currActivity.title}"
                          readOnly="true"/>
           <af:inputDate label="From" value="#{calendarBean.currActivity.from}"
                         readOnly="true">
             <af:convertDateTime type="date" dateStyle="short"
                                 timeZone="#{calendarBean.timeZone}"
                              pattern="#{calendarBean.currActivity.dateTimeFormat}"/>
           </af:inputDate>
           <af:inputDate label="To" value="#{calendarBean.currActivity.to}"
                         readOnly="true">
             <af:convertDateTime type="date" dateStyle="short"
                                 timeZone="#{calendarBean.timeZone}"
                              pattern="#{calendarBean.currActivity.dateTimeFormat}"/>
           </af:inputDate>
           <af:inputText label="Location" readOnly="true"
                         rendered="#{calendarBean.currActivity.location != null}"
                         value="#{calendarBean.currActivity.location}"/>
         </af:panelFormLayout>
       </af:dialog>
     </af:popup>
   </f:facet>
   

   Figure 17-8 shows how the dialog is displayed when a user clicks an activity and presses the Delete key.

   Figure 17-8 Delete Activity Dialog

   
   Description of "Figure 17-8 Delete Activity Dialog"
3. Implement any needed logic for the calendarActivityListener. For example, if you are implementing a dialog for the activityDeleteFacet, then implement logic in the calendarActivityListener that can save-off the current activity so that when you implement the logic in the dialog listener (in the next step), you will know which activity to delete. The following example shows the calendarActivityListener for the calendar.jspx page in the ADF Faces Components Demo application.

   public void activityListener(CalendarActivityEvent ae)
     {
       CalendarActivity activity = ae.getCalendarActivity();
       if (activity == null)
       {
         // no activity with that id is found in the model
         setCurrActivity(null);
         return;
       }
    
       setCurrActivity(new DemoCalendarActivityBean((DemoCalendarActivity)activity,
            getTimeZone()))
   

4. Implement the logic for the popup component in the handler for the popup event. For example, for the delete dialog, implement a handler for the dialogListener that actually deletes the activity when the dialog is dismissed. For information about creating dialogs and other popup components, see Using Popup Dialogs, Menus, and Windows.

1. In the JSF page of the Components window, from the Layout (Core Structure) panel, drag and drop a Facet for each section of the toolbar you want to add. For example, to add the custom buttons shown in Figure 17-10, you would add four facet tags. Ensure that each facet has a unique name for the page.

   Tip:

   To ensure that there will be no conflicts with future releases of ADF Faces, start all your facet names with customToolbar. For example, the section of the toolbar that contains the alignment buttons shown in Figure 17-10 are in the customToolbarAlign facet.

2. In the ADF Faces page of the Components window, from the Menus and Toolbars panel, drag and drop a Toolbar to each facet and add toolbar buttons and configure the buttons and toolbar as needed. For information about toolbars and toolbar buttons, see Using Toolbars.
3. Select the calendar, and in the Properties window, from the dropdown menu next to the ToolboxLayout attribute, choose Edit.
4. In the Edit Property: ToolboxLayout dialog set the value for this attribute. It should be a list of the custom facet names, in the order in which you want the contents in the custom facets to appear. In addition to those facets, you can also include all, or portions of the default toolbar, using the following keywords:

   • all: Displays all the toolbar buttons and text in the default toolbar

   • dates: Displays only the previous, next, and today buttons

   • range: Displays only the string showing the current date range

   • views: Displays only the buttons that allows the user to change the view

   Note:

   If you use the all keyword, then the dates, range, and views keywords are ignored.

   For example, if you created two facets named customToolbar1 and customToolbar2, and you wanted the complete default toolbar to appear in between your custom toolbars, the value of the toolboxLayout attribute would be the following list items:

   • customToolbar1

   • all

   • customToolbar2

   You can also determine the layout of the toolbars using the following keywords:

   • newline: Places the toolbar in the next named facet (or the next keyword from the list in the toolboxLayout attribute) on a new line. For example, if you wanted the toolbar in the customToolbar2 facet to appear on a new line, the list would be:

     • customToolbar1

     • all

     • newline

     • customToolbar2

     If instead, you did not want to use all of the default toolbar, but only the views and dates sections, and you wanted those to each appear on a new line, the list would be:

     • customToolbar1

     • customToolbar2

     • newline

     • views

     • newline

     • dates

   • stretch: Adds a spacer component that stretches to fill up all available space so that the next named facet (or next keyword from the default toolbar) is displayed as right-aligned in the toolbar. The following example shows the value of the toolboxLayout attribute for the toolbar displayed in Figure 17-10, along with the toolbar placed in the customToolbarAlign facet. Note that the toolbar buttons displayed in the customToolbarBold facet are right-aligned in the toolbar because the keyword stretch is named before the facet.

   <af:calendar binding="#{editor.component}" id="calendar1"
                value="#{calendarBean.calendarModel}"
                timeZone="#{calendarBean.timeZone}"
                toolboxLayout="customToolbarAlign all customToolbarTZ stretch
                               customToolbarBold newline customToolbarCreate"
   . . .
     <f:facet name="customToolbarAlign">
       <af:toolbar>
         <af:button id="alignLeft" shortDesc="align left"
                                  icon="/images/alignleft16.png" type="radio"
                                  selected="true"/>
         <af:button id="alignCenter" shortDesc="align center"
                                  icon="/images/aligncenter16.png" type="radio"
                                  selected="false"/>
         <af:button id="alignRight" shortDesc="align right"
                                  icon="/images/alignright16.png" type="radio"
                                  selected="false"/>
       </af:toolbar>
     </f:facet>
   . . .
   </af:calendar>

The activityStyles attribute uses InstanceStyles objects to style specific instances of an activity. The InstanceStyles class is a way to provide per-instance inline styles based on skinning keys.

The most common usage of the activityStyles attribute is to display activities belonging to a specific provider using a specific color. For example, the calendar shown in Figure 17-12 shows activities belonging to three different providers. The user can change that color used to represent a provider's activities in the left panel. The activityStyles attribute is used to determine the color displayed for each activity, based on the provider with which it is associated.

Figure 17-12 Activities Styled to Display Color for Different Providers

Note that instead of using a single color, a range of a color is used in the calendar. This is called a color ramp. A color ramp is a set of colors in a color family and is used to represent the different states of activities. For example, Ted's activities use the blue color ramp. Activities whose time span is within one day are displayed in medium blue text. Activities that span across multiple days are shown in a medium blue box with white text. Darker blue is the background for the start time, while lighter blue is the background for the title. These three different blues are all part of the Blue color ramp.

The CalendarActivityRamp class is a subclass (of InstanceStyles) that supports some built-in color ramps and can take a representative color (for example, the blue chosen for Ted's activities) and return the correct color ramp to be used to display each activity in the calendar.

The activityStyles attribute must be bound to a map object. The map key is the set returned from the getTags method on an activity. The map value is an InstanceStyles object, most likely an instance of CalendarActivityRamp. This InstanceStyles object will take in skinning keys, and for each activity, styles will be returned.

Before you begin:

It may be helpful to have an understanding of calendar styles. See Styling the Calendar.

You may also find it helpful to understand functionality that can be added using other ADF Faces features. See Additional Functionality for the Calendar.

To style activities:

1. In your CalendarActivity class, have the getTags method return a string set that will be used by the activityStyles attribute to map the returned string to a specific style. For example, to use the different color ramps for the different providers shown in Figure 17-12, you must return a string for each provider. In this case, an activity belonging to the current user might return Me, an activity belonging to Mary might return MJ, and an activity belonging to Ted might return TC. For information about implementing the CalendarActivity class, see How to Create a Calendar.
2. Create a map whose key is the set returned from the getTags method, and whose value is an InstanceStyles object (for example, a CalendarActivityRamp instance).

   For example, to use the different color ramps shown in Figure 17-12, you would create a map using the values shown in Table 17-2.

   Table 17-2 Map for activityStyles Attribute

   Key (String Set)	Value (InstanceStyles Object)
   {"Me"}	CalendarActivityRamp.getActivityRamp (CalendarActivityRamp.RampKey.RED)
   {"LE"}	CalendarActivityRamp.getActivityRamp (CalendarActivityRamp.RampKey.ORANGE)
   {"TF"}	CalendarActivityRamp.getActivityRamp (CalendarActivityRamp.RampKey.BLUE)

3. In the Structure window, select the calendar component, and in the Properties window, bind the activityStyles attribute to the map.

During calendar rendering for each activity, the renderer calls the CalendarActivity.getTags method to get a string set. The string set is then passed to the map bound to the activityStyles attribute, and an InstanceStyles object is returned (which may be a CalendarActivityRamp).

Using the example:

• If the string set {"Me"} is passed in, the red CalendarActivityRamp is returned.

• If the string set {"LE"} is passed in, the orange CalendarActivityRamp is returned.

• If the string set {"TF"} is passed in, the blue CalendarActivityRamp is returned.

1. Create a subclass of the oracle.adf.view.rich.util.DateCustomizer class. This subclass should determine what to display using the following skinning keys:

   Keys passed to the DateCustomizer.format method:

   • af|calendar::day-header-row: In day view, customize the day of the week in the header. For example, replace "Thursday" with "Thu".

   • af|calendar::day-header-row-misc: In day view, customize the text beneath the day of the week in the header. For example, display "New Year's Day" on Jan 1.

   • af|calendar::list-day-of-month-link: In list view, customize the text for the day of the month link. For example, replace "Jan 1" with "New Year's Day".

   • af|calendar::list-day-of-week-column: In list view, customize the day of the week in the left list column. For example, replace "Thursday" with "Thu".

   • af|calendar::list-day-of-week-column-misc: In list view, customize the text that appears beneath the day of the week in the left list column. For example, display "New Year's Day" on Jan 1.

   • af|calendar::month-grid-cell-header-day-link: In month view, customize the date link labels in the cell header. For example, replace "5" with "-34".

   • af|calendar::month-grid-cell-header-misc: In month view, add miscellaneous text to the empty area of the cell header. For example, on Jan 1, add the text "New Year's Day".

   • af|calendar::week-header-day-link: In week view, customize the date link for each date in the header. For example, replace "Sun 1/1" with "New Year's Day".

   • af|calendar::week-header-cell-misc: In week view, customize the text that appears beneath the date in the header. For example, display "New Year's Day" on Jan 1.

   • af|calendar::toolbar-display-range:day: In day view, or in list view when listType = day, customize the date string on the toolbar.

   • af|calendar::toolbar-display-range:month: In month view, or in list view when listType = month, customize the date string on the toolbar.

   Keys passed to the DateCustomizer.formatRange method:

   • af|calendar::toolbar-display-range:week: In week view, or in list view when listType = week, customize the date string on the toolbar.

   • af|calendar::toolbar-display-range:list: In list view, or in list view when listType = list, customize the date string on the toolbar.

   Keys passed to the DateCustomizer.getInlineStyle method:

   • af|calendar::list-row: In list view, apply a CSS style to the current activity row.

   • af|calendar::month-grid-cell: In month view, apply a CSS style for the specified date.

2. In a managed bean, create an instance of the DateCustomizer class. For example:

   private DateCustomizer _dateCustomizer = new DemoDateCustomizer();
   

3. In the calendar component, bind the dateCustomizer attribute to the DateCustomizer instance created in the managed bean.

/* Date Customizer Displaying Countdown Numbers */
public class MyDateCustomizer extends DateCustomizer
{
  public String format(Date date, String key, Locale locale, TimeZone tz)
  {
 
    if ("af|calendar::month-grid-cell-header-misc".equals(key))
    {
     // return appropriate string
    }
    else if ("af|calendar::month-grid-cell-header-day-link".equals(key))
    {
      // return appropriate string
    }
  return null;
 
  }
}

/* Date Customizer Displaying Color Coded Holidays */
public class MyDateCustomizer extends DateCustomizer
{
public String getInlineStyle(Date date, String key, Locale locale, TimeZone tz)
  {
    if ("af|calendar::day-all-day-activity-area".equals (key) ||
        "af|calendar::day-timed-activity-area".equals (key) ||
        "af|calendar::week-all-day-activity-area".equals (key) ||
        "af|calendar::week-timed-activity-area".equals (key) ||
        "af|calendar::month-grid-cell".equals(key) ||
        "af|calendar::list-row".equals(key))
    {
      Calendar curCal = Calendar.getInstance (tz, locale);
      curCal.setTime (date);
 
      if (_getUSHoliday (curCal) != null)
        return "background-color: #fafaeb;";
    }
  return null;
  }
}

/* Date Customizer Displaying Color Coded Holidays with dateHeaderStamp */
<af:calendar  id="cal"  ..>
  <f:facet name="dateHeaderStamp">
    <af:image rendered="#{calendarBean.dateCustomizer.USHoliday}"
              source="/images/holidayStar_16X16.png"
              shortDesc="#{calendarBean.dateCustomizer.dateHeaderDesc}"
    ../>
  </f:facet>
</af:calendar>