1.1 --- a/pages/HelpOnEventAggregator Fri Oct 30 20:36:04 2009 +0100
1.2 +++ b/pages/HelpOnEventAggregator Sat Oct 31 01:24:06 2009 +0100
1.3 @@ -116,6 +116,24 @@
1.4
1.5 Without any time period, the calendar would show all events, and there would be no real need to provide navigation, since there would be no events outside the displayed period to navigate to. It is possible to omit either the `start` or the `end` parameter and still provide navigation, however.
1.6
1.7 +=== Assigning Templates and Parent Pages ===
1.8 +
1.9 +New events can be added to a calendar by following the links on each of the day numbers; this opens the form provided by the !EventAggregatorNewEvent action. For all events belonging to a particular calendar, it can be convenient to assign a default template page, so that the information provided by such events is consistent. Thus, it is possible to specify such a template page using the `template` parameter. For example:
1.10 +
1.11 +{{{
1.12 +## Specify a particular template page as the default event page template.
1.13 +<<EventAggregator(CategoryEvents,template=SpecialEventTemplate)>>
1.14 +}}}
1.15 +
1.16 +It can also be convenient to add new event pages under a common parent page. This can be achieved by specifying such a page using the `parent` parameter. For example:
1.17 +
1.18 +{{{
1.19 +## Specify a particular parent page as the default container for new events.
1.20 +<<EventAggregator(CategoryEvents,parent=Events)>>
1.21 +}}}
1.22 +
1.23 +Creating an event called '''Meeting''' under a parent called '''Events''' will make the page '''Events/Meeting''', and this will be shown as '''Meeting''' in the calendar. However, if a different parent is chosen, such as '''Meetings''', then the full path to the page will be shown in the calendar: '''Meetings » Meeting'''.
1.24 +
1.25 == Showing Event Lists and Tables ==
1.26
1.27 A more plain view of events can be displayed by specifying the `mode` parameter as follows: