Re: Call for Votes: PEAR::Calendar
| From: | hfuecks at phppatterns dot com | Date: | Sat, 25 Oct 2003 16:08:16 +0000 |
| Subject: | Re: Call for Votes: PEAR::Calendar | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-22987@lists.php.net to get a copy of this message | ||
Lorenzo,
Thanks for taking time to check it out (and glad it's been useful to you).
Regarding your suggestions;
1) last*() should be called prev*().
Good point - never occurred to me before - will do that.
2) use PEAR::Date as backend
Definately, but I'd like to avoid be the person that does the work there
though.
If anyone wants to help maintain this package, implementing a second
engine based on PEAR::Date could be a great way to get familiar with the
code.
3) follow a directory structure as every PEAR pkg does:
Calendar_Engine_Factory.php should be
Calendar/Engine/Factory.php
and follow CS like using "require_once"
No problems.
4) Alan's proposal of handling dates this way:
> $nextday = $date->make($date->year, $date->month, $date+1);
> $nextmonth = $date->make($date->year, $date->month+1, $date);
Yep - been pondering this one. Like it although there are some
difficulties to overcome (for example a week and a day use the same
argument index - $Week = & new Calendar_Week(2003,10,1); and $Day = & new
Calendar_Day(2003,10,1); - will see what I can come up with - perhaps
using constants to control behaviour?)
5) week management.
See what you mean. Weeks are the "weakest link" right now. Need to spend
some time work it out but your suggestion, using the weeks from the
previous / next month, sounds like a good way.
OK - so back to the call for votes. How about this - version 0.1 (the
first release) will include changes 1 and 3 above. The rest will be
something for version 0.2, when there's time (plus tutorials and [note to
self] unit tests). That sound acceptable?
So far the count is +1 from Lorenzo and (I think) +1 from Markus Wolff.