The meeting view control expects information in a specific XML format. Below is an example of this:
<SCHEDULE MODE="Single|Multiple" TYPE="User" READ_ONLY="False" DATE="2003-30-10"> <USER NAME="John Smith" ID="12345" DURATION="90"> <BUSY START="2003-30-10 10:30:00" END="2003-30-10 12:30:00"/> <BUSY START="2003-30-10 15:45:00" END="2003-30-10 16:15:00"/> </USER> <USER NAME="James Smith" ID="12346" DURATION="90"> <BUSY START="2003-30-10 12:30:00" END="2003-30-10 13:30:00"/> <BUSY START="2003-30-10 15:00:00" END="2003-30-10 18:15:00"/> </USER> </SCHEDULE>
Note that in the format above: the MODE attribute is either Single or Multiple; the DURATION attribute is in minutes; START and END attributes are date-times in the format "yyyy-MM-dd HH:mm:ss". The READ_ONLY attribute, if set to false, indicates that no time slot will be selectable as a hyperlink. The DATE attribute contains the date of the current scheduling and must be supplied. It should be in the format "yyyy-MM-dd". Finally, the TYPE attribute associates the schedule information with configuration settings which are also specified in an XML format as below:
<SCHEDULE_CONFIG> <CONFIG TYPE="User" INTERVAL="15" START="08:00" END="16:00"> <USER_HOME PAGE="PersonHome" ID_PARAM="UserID" NEW_WINDOW="True" /> <NEW_EVENT PAGE="AddNewEvent" ID_PARAM="UserID" START_PARAM="start" END_PARAM="end" /> <MULTI_SELECT PAGE="SelectedUsers" TAB_STRING_PARAM="selectedUsers" DATE_PARAM="eventDate" /> </CONFIG> </SCHEDULE_CONFIG>
Where INTERVAL is the duration in minutes of each segment of the time line. This can be 15, 30, or 60. Only these values are acceptable. The START and END attributes detail the beginning and end times of the time line. They are in the form "HH:mm". Each CONFIG element can have the following sub-elements: