Merge efforts
| Project: | Themer |
| Version: | 6.x-2.0 |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Hi there,
I am writing a coupld of theme utility modules to assist in theming views and imagecache images in Drupal 6 and think that they would be a good companion to themer module in a themer package. Actually I was going to contribute them under 'themer' but you've already got the namespace, but they make sense to ship togeth anyway.
svn checkout https://svn.civicactions.net/repos/bevan/trunk/sites/feriana.co.nz/modul... to see my work. It's very alpha at the moment, needs admin UIs a realy settings API, testing and documentation. I plan to be developing these extensively this month (december), and probably continuing to use them in the future.
What do you think about merging our efforts into one package? Could you give me CVS access so I can commit my work regularly and to facilitate testing by others?
Cheers,
Bevan/
#1
Certainly, I will allow CVS access. Its a small library so it could use some beef
#2
Thanks! I committed the files to CVS HEAD already. I forgot to change to the DRUPAL-6 branch before committing. Given the very alpha state of this code, that's probably more appropriate anyway.
I didn't commit a couple of changes I made to themer module – I wanted to see what your thoughts were on this feature; rebuild theme registry on every page request if devel module is enabled.
Perhaps this is better in another module, or with a more explicit user-enabled checkbox? What do you think?
#3
Probably belongs in Devel to be honest, but I am not sure if they are backporting anything to 6 really, I submitted a patch to devel and he wanted it in 7 only, so im not sure.