RE: [SM-CVS] CVS: squirrelmail/plugins/calendar calendar.php,1.13,1.14 calendar_data.php,1.8,1.9 event_edit.php,1.14,1.15

[p d. t. <pdo...@an...>]

> Update of /cvsroot/squirrelmail/squirrelmail/plugins/calendar
> In directory sc8-pr-cvs1:/tmp/cvs-serv27657
> 
> Modified Files:
> 	calendar.php calendar_data.php event_edit.php
> Log Message:
> In month view, sort events on a day by starttime so that an event that
> starts at 9 is not displayed below one that starts at 17. Include the
> time in the tooltips. Remove some E_ALL notices. This whole
calendarcode
> needs some serious maintentance, but that's for later.

All/Thijs,

  I wondered aloud a while back on the devel list (no response) about
replacing the calendar plugin with the shared calendar plugin, since I
have been maintaining the shared calendar plugin, which uses 90% of the
standard calendar code.  I have tried to keep some of the more important
fixes backported into the core calendar plugin, but not everything has
made its way back (the E_ALL fixes you made here, for example, were
already fixed in shared calendar.... and there is a bug in the tool tip
text where you added the time (not a bug of your creation) that is fixed
in the shared calendar, etc).  The shared calendar has also been getting
more user feedback and patches - for example, it now has a yearly
view...

  It just seems a shame to duplicate effort like this and a real pain in
the a** to keep the two in synch, although if we take on the shared
calendar plugin, the shared functionality does add a new level of
complexity that we'd be committing to as the SM team.  It'd be nice to
see the whole damn thing re-written or at least extensively revamped so
that it could support data export, palm synch, v-calendar, database
backends, email notification, event conflict management, blah blah blah.
But then again, we're starting to talk about a feature set that is a
great deal apart from email!

Thoughts?

   - Paul