Saturday

We discussed the agenda for today and came up with 3 goals:

1) Views

• Evaluate the various Plone calendar products (CalendarX, Booking, Calendaring) and see what templates/skins we can reuse. (fenestro)
  
• Mock up these "views":Views in Illustrator for an overall design. (kamal) Hopefully, when Limi stops by he can evaluate these views for their UI merits.
  
• Make CalViews, a simple product/skin for prototyping various views - month, week, day. (natea)
  

2) CalPlone

• Work towards getting an installable version of CalPlone. There are many XXX's which need to be looked at more closely to see whether they are necessary in the first version, or whether they can be omitted for now. (rockyburt)
  

3) Recurring events

• Kapil has offered to work on this today when he gets in. (kapil)
  

Saturday wrap up

Kapil:

• CalPlone is not associated with an i18n domain, so it is looking in the plone i18n domain. Hopes that associating it with its own i18n domain
  
• How to get events to show up. with CalZope, there is a single event storage for all the calendars in the system. But in Plone, event is a content type. Has good tools for getting events out given a certain time range, and recurrence rules. Need to find a way to have the events show up in the content hierarchy.
  

Kamal:

• now has access with the collective and increased access on wiki so he can add images
  
• added Mockups to the wiki (week, month views)
  

Drew:

• asked whether a calendar is a folder with just my events, or is it an aggregation of multiple calendars. how to control the viewing of events on a particular calendar.
  

Nate:

• got CalPlone running and able to view a calendar
  
• created CalViews product which can now associate suppl_views to ATFolder, register CSS and install action icons.