Proper I18N:
@@ -48,9 +51,33 @@
- The calendar needs to be printable (at least for where I work)
-
+
+ Data Model suggestions.
+
+
+ Don:
+Calendar items should map arbitrary objects (perhaps only content items) to a
+given calendar and given acs-events. We shouldn't have to derive special
+types from cal item type in order to attach it to a calendar (nor should we
+have to duplicate content to attach it to two calendars as we do now)
+
+If we restricted the mapping to content items (i.e. calendar info some sort of
+content type) we could use the CR's ability to map a template to a given
+content type or item to make it possible for the calendar package to display
+calendar item details using that facility, giving the package adding
+something to the calendar control over how it is displayed. Much more
+general.
+
+
+
Thanks to
+
+ - Raad Al-Rawi from Cambridge University for calendar.css and all of the
+ layout.
+
+
+
This is old stuff and will probably disappear in the near
future. (June-2003)
Index: openacs-4/packages/calendar/www/ics/index.vuh
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/calendar/www/ics/index.vuh,v
diff -u -r1.2 -r1.3
--- openacs-4/packages/calendar/www/ics/index.vuh 10 Jul 2002 14:58:25 -0000 1.2
+++ openacs-4/packages/calendar/www/ics/index.vuh 21 Jul 2003 19:21:36 -0000 1.3
@@ -19,8 +19,7 @@
ad_script_abort
}
-# Permission (FIXME: ben)
-# ad_require_permission $cal_item_id read
+ad_require_permission $cal_item_id read
set ics_stuff [calendar::outlook::format_item -cal_item_id $cal_item_id -all_occurences_p $all_occurences_p]