svenfuchs / adva_cms
- Source
- Commits
- Network (48)
- Issues (2)
- Downloads (9)
- Wiki (5)
- Graphs
-
Tree:
c0d9f9a
commit c0d9f9a7742d9b360fc8b3d36c460585659c5014
tree c3db977d71f64b3d818d67d1062f47a1ebc61e8f
parent 616edf10304c03c852462eec2df551258e5fe8a4
tree c3db977d71f64b3d818d67d1062f47a1ebc61e8f
parent 616edf10304c03c852462eec2df551258e5fe8a4
engines/adva_calendar/README
The calendar engine models: * Calendar which is a section * Event * Category * Location * Bookmark (A User-Event relation) A calendar has many categories A calendar has many events An event takes place at a location A bookmark belongs to a single event and user Event: Has a start and end datetime Has a title, description, keywords and host Repeating events are copied and stored for every occurrence with reference to first event Longterm events (like an exhibition with opening hours) are stored once and should use description field for opening hours. Weblinks / further inspiration: * iCalendar RFC: http://tools.ietf.org/html/rfc2445 * http://icalendar.rubyforge.org/

