Views to look at:

• phpicalendar
  • day: http://rtg.ietf.org/~fenner/test/phpicalendar-2.1/day.php?cal=all_calendars_combined971&getdate=20051130
  • week: http://rtg.ietf.org/~fenner/test/phpicalendar-2.1/week.php?cal=all_calendars_combined971&getdate=20051129
  • incredibly busy week: http://rtg.ietf.org/~fenner/test/phpicalendar-2.1/week.php?cal=ietf64&getdate=20051106
  • day view of incredibly busy week: http://rtg.ietf.org/~fenner/test/phpicalendar-2.1/day.php?cal=all_calendars_combined971&getdate=20051107
• Upcoming event list
  • http://www.eastbayamigos.org/current/PloneCal/calendarAll
• Mambo
  • Month: http://www.bostonphp.org/index.php?option=com_extcalendar&Itemid=33
  • Month event list: http://www.bostonphp.org/index.php?option=com_extcalendar&Itemid=33&extmode=flat
  • Week: http://www.bostonphp.org/index.php?option=com_extcalendar&Itemid=33&extmode=week&date=2005-12-04
  • Day: http://www.bostonphp.org/index.php?option=com_extcalendar&Itemid=33&extmode=day&date=2005-12-06
• Zimbra

  Hard to do links. Pretty AJAX stuff, dragging an event around to change the start time, dragging the bottom to change the end time, dragging across empty space to quick-add a new event.

• Hula
• Booking

  (prereqs: ATCT 0.2, Plone 2.0.5)

  • week view of one object: https://rtg.ietf.org:8081/foo/booking/thing%201/booking_view?bookingdate:date=2005/12/03
• CalendarX?
  • Month view: http://www.ivtf65.org/Participants/BillFenner/calendarx/month?currentDate=2006/03/03&xmy=0&xsub=ALL
  • Week by day: http://www.ivtf65.org/Participants/BillFenner/calendarx/weekbyday?currentDate=2006/03/24&xmy=0&xsub=ALL
  • Week by hour: http://www.ivtf65.org/Participants/BillFenner/calendarx/weekbyhour?currentDate=2006/03/24&xmy=0&xsub=ALL
• Calendaring
  • Can't get svn version to import an uploaded calendar
  • http://www.ivtf65.org/Participants/BillFenner/bill-s-test-calendaring-folder/
  • Day: http://www.ivtf65.org/Participants/BillFenner/bill-s-test-calendaring-folder/day_view?cday=4&cyear=2005&cmonth=12 (note: hours by the left are in utc :-( )
  • Future month: http://www.ivtf65.org/Participants/BillFenner/bill-s-test-calendaring-folder/month_view?cyear=2006&cmonth=3
  • Month: http://www.ivtf65.org/Participants/BillFenner/bill-s-test-calendaring-folder/month_view
  • Future week: http://www.ivtf65.org/Participants/BillFenner/bill-s-test-calendaring-folder/week_view?cday=20&cyear=2006&cmonth=3

Things to steal:

• Booking's click-to-schedule

Views we want:

• Day
• Week
• Month
• Day / Week / Month / All upcoming list view (in hCalendar microformat?)
• iCalendar format (thinking about iCalendar as a view allows reuse of any filtering, etc.)

http://permalink.gmane.org/gmane.comp.web.zope.plone.calendaring/144

• (Assumption: ways to view a smart folder) Correct assumption; the primary use of these templates would be selectable views of a smart folder. Most likely, they could be reused by products for any type of container returning Event-like results.
• Jeff Kowalczyk: (adding wish-list descriptions of the views)
• (definition) Result Events: The results of the Smart Folder criteria
• (definition) When configurable is mentioned below, it refers to some mechanism for the view instance to either acquire a property set on the smart folder, or site-wide configuration of preferences for that view type.
• (definition) When for one day etc, are mentioned below, it refers to some mechanism to either dynamically alter one criteria of the smart folder (e.g. date), or the current index in some results batching mechanism. I haven't seen something like this in action yet, so I'll leave it to the experts to interpret.
• day summary: Non-grid sequential text listing of appointments for one day. Suggest configurable visual grouping of Result Events, per hour, morning/afternoon and no grouping, if possible. No space-padding or display of unused groupings, so this is not a grid.
• day-by-hour: Time grid sequence of hours for one day, the familiar day view for Evolution, etc. Configurable of day start-end hours is desirable (e.g. 9-5 offices have different display needs than 24/7 facilities). Special handling of all-day events (different from 00:00 - 23:59) is needed, some apps make a top header for all-day events.
• week summary: Non-grid sequential text listing of appointments for one week. Suggest configurable visual grouping of Result Events, per day and no grouping, if possible. No space-padding or display of unused groupings, so this is not a grid.
• week-by-day: horizontal grid sequence (columns) of day summary views. Configurable 5, 6 or 7 day display.
• week-by-day-by-hour: horizontal grid sequence (columns) of day-by-hour views. Configurable 5, 6 or 7 day display.
• month summary: Non-grid sequential text listing of appointments for one month. Suggest configurable visual grouping of Result Events, per week, per day and no grouping, if possible. No space-padding or display of unused groupings, so this is not a grid.
• month calendar: 7x5 grid of day summary views. Configurable normal, greyed or invisible days in previous or next months that fall on the grid. It is assumed that a month calendar view (even with empty results) will be CSS styled to completely fill the main slot, and in printable media, the whole page. Per date, the truncated title of matching events could be displayed. Limits on length and number of events per day must be imposed with ... to preserve uniform grid spacing.
• 3 month calendar: 1x3 grid of month calendar views. Selected month is the middle month, display previous and next. Print media results in 3 print pages.
• 12 month calendar (formerly called year): 1x12 grid of month calendar views. Selected month determines the year, and all 12 months for that year are shown in a vertical sequence. Printable media results in 12 print pages.
• year summary: Non-grid sequential text listing of appointments for one month. Suggest configurable visual grouping of Result Events, per month, per week and no grouping, if possible. No space-padding or display of unused groupings, so this is not a grid. Will potentially be a large list, leave it to the user to set sane criteria on their smart folder.
• monthly compact calendar: Similar to current portlet calendar view, this is a 7x5 grid of date numbers for one month. If there is an event matching a date, either boldface the date number, or put a single bullet (i.e. square dot) in the date square. CSS styling should ensure uniform grid size even for empty dates. Since it is about 33% width of main slot, monthly compact calendar view is rarely used by itself, instead reused by yearly views. May also come to be used in portlets, mirroring current portlet calendar functionality.
• year monthly compact calendar: 3x4 grid of monthly compact calendars. Intended to fill main slot in width and about a screenful of height. Printed media would fill 1 printed page.
• 3-year monthly compact calendar: 3x4 grid of monthly compact calendars, repeated 3 times in a vertical column. Can't say whether it would be more useful to display previous-selected-next, or selected-next-2ndnext years. Intended to fill main slot in width and several screenfuls of height. Printed media would fill 3 printed pages.

Things for views to handle:

• All-day events (e.g., at the top in phpiCalendar)
• Events outside the normal day view time (e.g., view is 0800-1800 and you have an event from 2000-2100)
• Multi-day events

Things to handle in underlying objects:

• All-day events distinct from 00:00 - 00:00

Other:

• hCalendar microformat in ATEvent? / CMFEvent? view too?