Closed (fixed)
Project:
Calendar Systems
Version:
6.x-1.2
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Jun 2010 at 06:10 UTC
Updated:
18 Jan 2013 at 11:43 UTC
hi,
have u requested drupal developers to move the required path into core?
i think a hook through the date rendering is missing in drupal and they would do that.
Comments
Comment #1
sinasalek commentedIf you mean the required patch, yes a long time ago. Getting patches into the core needs lots of time. A luxury that i don't have.
I created this module to facilitate that. If it has enough community support behind it, we can push it to core, Otherwise that would be a complete waste of time.
Comment #2
sinasalek commentedComment #3
klonosIn #1 you mention that you've filed an issue for this. Can you point us to it? Perhaps if we make some noise we'll get heard.
Comment #4
klonos... I mean, modules are not supposed to require core patching for them to work. If they do not work out of the box, it repels new (not-so-drupal-savvy) users. Have you thought that this might be the reason why despite the fact this module if really useful and deals with an issue that IMHO should be dealt with in core, it still has really low usage stats?
Comment #5
sinasalek commentedThere are two reasons that Calendar Systems is not yet known properly by the community
1. The number of supported calendar systems currently is limited to Persian, Arabic other calendar systems are under development. I'm looking for a pre-written library to replace the one i developed in order to boost the development. currently there are two candidates. ICU (Which has a PHP extension) and extending PHP 5's new Date object
2. For the above reason i didn't publicly announce the project
To move this project forward i need as much as help anyone can provide. And writing about this module and talking/writing about this feature , filling feature request , etc can also help.
Why do we have long way till it gets into the core ? please refer to my note at this page (How to Integrate)
http://groups.drupal.org/node/10607
http://drupal.org/node/205500
Comment #6
klonosI can see why the whole module's implementation & API would get a really looong time till they get in core, but I don't see why not provide a 'hook' (am I using this drupal term correctly?) for our module since it has great potential and aims to implement something that should have been in core from the start.
I guess it's the same reasons as why SimpleTest also requires patching core and is not in yet: #582942: Add latest SimpleTest backport directly to core
Comment #7
sinasalek commentedWe may have a chance for Drupal 8. However a simple hook only fixes the representation problem and even that produces some incompatibilities with other modules, As it has already been reported on calendar systems issue queue. With this condition core maintainers would never accept such a patch and they have a good reason for that.
The usage and amount of contributions to this project shows the importance of this feature and facilitates the porting to core pretty much and that's exactly why i started Calendar Systems.
Comment #8
sinasalek commentedMarked
Comment #9
sinasalek commentedA core patch is proposed
#1811912: Add pluggable calendar backend to core and centralize date translation
Comment #10
sinasalek commented#1178342: Allow contributed modules to alter the format_date() function result.