OVERVIEW.txt 
  CalendarX 0.5.3(dev)  March 26 2005
  (last modified for CalendarX 0.5.2)
by +lupa+ (lupaz on sf.net, lupa at zurven dot com)
Released under the GPL (see LICENSE.txt)

Pretty current summary of CalendarX functionality
New Feature list (0.5 branch):
* Now has links (+ sign) in each calendar view cell for members to allow them
  to add events on that day, or in that hour (depending on view).  
* XHTML valid code throughout.  
* Huge speed increase over 0.5.0, and now faster than 0.4 branch too.
* Two portlets to use as mini-calendars for your site. Both of them read 
  events from a linked, specific CalendarX instance elsewhere in your site, 
  and link to it from the Month name.  
  #1 portlet_calendarx: uses the configuration you've already set up in the
    referred CX instance, but shows the events as icons in a mini-month view in 
    a portlet from any page that you want it to show up on (via normal slots 
    and portlets usage).  Thanks to Vanessa for the initial code and idea, this
    one offers many possibilities for further customization -- it's much like 
    a mini-CalendarX instance. 
  #2 portlet_calendarxp: looks almost just like the original portlet_calendar
    that comes with Plone, a nearly plug-and-play replacement, although you 
    still need to tie it to a CalendarX instance.  Thanks to David for pushing
    for this one.
  See INSTALL.txt for details on installing, using both.
* Portlet-based options allows cleaning up the header.  All the choices are
  nicely laid out and improved for the portlet.  I've made this the default
  configuration (with a clean, blank header) for the 0.5 branch.
* Several different configurations of the header options are now available, 
  allowing different arrangements of the subject, add new event, etc. widgets.
* New user picker option for managers (or anyone, if desired).  Choose any one
  or several users and the calendar will be restricted to showing only those
  users.  TALES property controlling access to this is available through the
  property sheets!  Now you can also just restrict the listing of users to 
  a simple lines property list of Users.  Thanks Alec, this is so cool.
* Big reworking of the code for doing the getEvents queries... saner and more
  expandable and better documented.  Alec kicked this off with a patch just 
  before Christmas and I built on it (lots).  The result: you can now
  restrict your calendar events in MANY more ways than in the 0.4.0 
  branch.  For example you can restrict showing events in your /staff folder
  ONLY to those users with a Staff role, or those belonging to a "staff" 
  group, or to users fsmith, kjones and jrodriguez.  And not just paths, you 
  can restrict by Subject, review_state, Creator and Types too.  NOT by any 
  means a substitute for proper Plone security, but useful all the same.


Basic Feature list (0.4 branch):
* Provides basic calendar functionality with standard Plone content (CMFEvents,
  AT Events, custom AT events).
* Month, Week by day, Week by hour, Day views available.
* Metacalendar: Categorize your Events using the Subject attribute standard on 
  all Plone/CMF events.  Choose categories in a bar just below the View tabs.  
  Change subjects in portal_metadata tool.  Choose between ONE subject at a 
  time, or MULTIPLE subjects at one time.
* Many configuration options available through use of property sheets, including
  decoration of the calendar, decoration of events by Subject or Type, putting
  restrictions on the type, location or subject of events shown, etc. 
* Day and WeekByHour views can be easily managed to display fractional days: 
  from 8am to 6pm, for example.  Hours displayed on these can be set to 
  12 or 24 hour formats.
* Multiple calendars can be created within one Plone site.  Customized property 
  sheets for each calendar can (should) be stored within each calendar so that 
  calendar properties will be unique.  Also any python scripts, javascripts, 
  CSS files can be uniquely customized for any one calendar.
* Subcalendars - nested calendars and modifications to the Subject links
  that allow busy calendars to be subdivided beyond just Subject usage.  Good
  for school calendars, Resource scheduling (equipment reservations), etc.
* Private calendars: All your users automatically have a private calendar, if
  they so choose.  They can just add Events and set them to "private" status, 
  and then only they can see them on their calendar.
* "Add New Event" link, with customizable destination folders depending on 
  user and/or Roles.
* Customize a "calendar help" page for your newbie users.  Help appears as a
  tab, if you choose to make it available, and is customizable.
* Installs as a normal Plone Product, addable as Plone content, but also may 
  be added through the ZMI.  
* No Dependencies: Only needs Plone standard products.  Will use Dieter's 
  ManagableIndex and AdvancedQuery products if desired.  Or not.



Planned features for future branches: 
* Group calendar support through GRUF 3.0.
* Repeat events (when we get a new catalog index written for them).
* i18n support
* iCal export and import.  Does export now, sorta, if you use ATCT Events 
  (that functionality is built in to ATCT Events).


===
CalendarX builds on a proud tradition of other Zope/Plone products, and 
  gathers strength through the tremendous efforts of its users 
  (see CREDITS.txt).
===