After talking with Karen at the Midwest Developer Conference I am very excited to help out working on bringing the date module functionality into Drupal 8. There is a lot of work to do in order for that to happen. We need to:
- Separate the code that can become a Component from the code that needs to be Drupal specific
- Separate the code that needs to be a library (PSR-0) and the stuff that needs to be in the module directory
- Separate the code that should be put into core from the core that will live on as a community-driven module.
A good place to start that effort is to analyze how other frameworks handle this separation of tasks. How do they separate model-level logic, from helpers, from controller logic, from display logic, etc.
My this time next week, I plan to evaluate the following system’s handling of dates with that in mind:
- Frameworks
- .Net Framework
- Java
- Python
- Google Web Toolkit
- Other Database’s Native handling of Dates (with an eye towards what helpers they have)
- MSSQL
- Oracle
- Postgres
The main idea behind this effort is that I need to get up to speed on these system level-details as it will be important to have all of this my head while we’re working improving the Date module and getting Date into Drupal 8. Putting these findings here hopefully gives others who are interested on working on Date up to speed faster.
Does anyone have ideas how the study can be improved?