Re: Call for Votes: PEAR::Calendar

Hi Harry, vote: +1 review: code review, some testing account: cellog When I start using the package (won't be too soon), I would like to help out. One problem that I have had trouble with in the past is handling events that span more than one day, and can overlap month or year boundaries (such as travel, vacation time, or a residency). The database representation has been a starting date plus the length of the event in days. To translate this into actual dates, I've been using date calculation through mysql, which is probably pretty slow compared to PHP, but it worked at the time. If a backend is developed that uses Date, I can use Date_Calc to handle this instead. Of course, I could use Date_Calc anyways, and might do that, but thought this problem might give some ideas :). Greg Harry Fuecks wrote:

Proposed Name: Calendar Proposed Category: Calendar (new namespace) PEAR::Calendar is an package for generating Calendars as data structures (it does not render content) allowing you to easily connect up a user interface with an underlying data store (such as MySQL). It provides a simple API to make generating a calendar much like querying a database - just pick a date then render the output with a loop. It's also extensible so should (in theory) be a foundation for generating practically any calendar you can think of (the challenge is a Chinese calendar). PEAR package: ------------- http://prdownloads.sourceforge.net/htmlsax/Calendar-0.1.tgz?download Extensive README: ----------------- http://htmlsax.sourceforge.net/calendar/ API documentation: ------------------ http://htmlsax.sourceforge.net/calendar/api/ Examples: --------- http://htmlsax.sourceforge.net/calendar/examples/ This follows the earlier package proposal: http://marc.theaimsgroup.com/?l=pear-dev&m=106045306402489&w=2 to which the issues raised have been addressed (it's now extensible and no longer tied to Unix timestamps). Also package name change on recommendation, from Date_Calendar to Calendar One thing that would be very good would be volunteers willing to help maintain the package. Timewise there's never enough. [PS: Please note I can only post on the mailing list in the evenings...] Thanks, Harry