Public domain JavaScript converters for numerous calendars:
http://www.fourmilab.ch/documents/calendar/

There are two type of Calendars in Muslim countries:

• Arabic Calendar (a.k.a, Islamic Calendar)
• Iranian Calendar (a.k.a., Persian Calendar or Jalali Calendar).

In Iran, we use Iranian Calendar which is completely different from
Arabic calendar.

For example, Jan 1 2008 equals to:

• Iranian/Persian Calendar: Month=Dey, Day=11, Year = 1386
• Arabic Calendar: Month=Dhu al-Hijjah, Day=21, Year = 1428

Now two requests:
Please add "class Zend_Calendar_Iranian {} ".
Please and correct the current Use Cases (1385 Dey 05 is an Iranian Date, not Arabic.)

@see: http://en.wikipedia.org/wiki/Islamic_calendar
@see: http://en.wikipedia.org/wiki/Iranian_calendar

will this be part of the Zend_Calendar features.
"Give me date of last Sunday of year 2008" or" What's the date of second Monday for Jan 2007"

is there a proposal for repeat events
What about weekly and daily views

When I read of Zend_Calendar I thought of a component capable of handling calendars, something that given some options can generate a calendar (in terms of a table with the calendar of the specified month and year).

If Zend_Calendar is a mere extension of Zend_Date for handling calendars that differs from the gregorian one, why don't just enhance Zend_Date to handle different calendars instead of creating confusion with this namespace?

Think of a programmer who wants to implement a calendar in his application, don't you think he will try to use the Zend_Calendar namespaces' classes to make a calendar? A Zend_Calendar that handle different calendars - in terms of calendar types - will likely confuse him.

I hope I explained my point.

Hi, Thomas!

In my point of view, we have two kinds of calendar.
One calendar is an object that handles events.
Of course, this calendar should be aware of locale and should have adapters to convert calendars to the right locale.
The other calendar, is the calendar related to dates.
If you want to just extend functionality from Zend_Date, you should keep it locally and create the adapters as Zend_Date_Adapter_Interface to have the conversions of the date specifically and not of the events calendar, that is a set of years, months, days, hours, minutes and seconds. Or simply creating it as Zend_Date_Calendar instead of Zend_Calendar.
Another thing is instead of having methods called toGregorian(), toIslamic(), etc, it should implement a factory method and the calendar to be converted to should be passed as parameter, like:

In the Zend_Calendar, we could use all the features of the Zend_Date, but with other perspective, and also use the Zend_Date adapters to have the correct view for the calendar also. In the Zend_Calendar, I also think it would be nice to be possible to set working days, working hours, first day in the calendar, adding holidays, events, shifts and display the calendar according to all this settings.

The Zend_Calendar interface should look like this:

These set of classes below would be supposed to handle with events:
Zend_Calendar -> it wouldn't extend Zend_Date
Zend_Calendar_Year // year object is a set of months
Zend_Calendar_Month // month object is a set of weeks
Zend_Calendar_Week // week object is a set of days
Zend_Calendar_Day // day object is a set of events that will occur at a specifically time in that day
Zend_Calendar_Event
Zend_Calendar_Exception
Zend_Calendar_Adapter // In the case of this calendar, the adapter will work as view translators, translating the calendar objects to its properly locale
Zend_Calendar_Interface
Zend_Calendar_Adapter_Arabic
Zend_Calendar_Adapter_Buddhist
Zend_Calendar_Adapter_Chinese
Zend_Calendar_Adapter_Coptic
Zend_Calendar_Adapter_Ethiopic
Zend_Calendar_Adapter_Gregorian
Zend_Calendar_Adapter_Hebrew
Zend_Calendar_Adapter_Islamic
Zend_Calendar_Adapter_IslamicCivil
Zend_Calendar_Adapter_Japanese
Zend_Calendar_Adapter_Persian
Zend_Calendar_Adapter_Interface
Zend_Calendar_Adapter_Exception

That's my opinion!

Regards,

–
Ramses Paiva
Software Consultant
SourceBits Technologies
www.sourcebits.com

Better idea:

And the components would be only:
Zend_Calendar -> it wouldn't extend Zend_Date
Zend_Calendar_Year // year object is a set of months
Zend_Calendar_Month // month object is a set of weeks
Zend_Calendar_Week // week object is a set of days
Zend_Calendar_Day // day object is a set of events that will occur at a specifically time in that day
Zend_Calendar_Event
Zend_Calendar_Exception
Zend_Calendar_Interface

And the adapters would have a different approach:
Zend_Calendar_Adapter -> instead of conversion of dates, it could be used as a database connection to retrieve events (and holidays, once the holidays is a specialization of events)
Zend_Calendar_Adapter_Interface
Zend_Calendar_Adapter_Exception
Zend_Calendar_Adapter_DbTable

Regards,

-
Ramses Paiva
Software Consultant
SourceBits Technologies
www.sourcebits.com

This proposal requires some refactoring and Thomas currently does not have the time to do it. This will be archived for resurrection later.