Robert Cummings wrote:
On Wed, 2008-05-28 at 16:47 -0400, Robert Cummings wrote:
Out of curiosity.. have you thought about reworking your premise? Using
prev, current, and next is extremely sloppy IMHO. Additionally, it
prevents bookmarking a specific calendar date. Why don't you have a date
par
Robert Cummings wrote:
Out of curiosity.. have you thought about reworking your premise? Using
prev, current, and next is extremely sloppy IMHO. Additionally, it
prevents bookmarking a specific calendar date. Why don't you have a date
parameter that indicates the year and month? If no such field
On Wed, 2008-05-28 at 16:47 -0400, Robert Cummings wrote:
> Out of curiosity.. have you thought about reworking your premise? Using
> prev, current, and next is extremely sloppy IMHO. Additionally, it
> prevents bookmarking a specific calendar date. Why don't you have a date
> parameter that indic
Out of curiosity.. have you thought about reworking your premise? Using
prev, current, and next is extremely sloppy IMHO. Additionally, it
prevents bookmarking a specific calendar date. Why don't you have a date
parameter that indicates the year and month? If no such field exists
then you fallback
Mark Weaver wrote:
Hi all,
I've put this off as long as possible, however I think I've reached an
impasse.
I've got an application that I've been writing. One of the modules for
this app is an event calendar. I've got the calendar to the place where
it displays the current month as well as
5 matches
Mail list logo
