On May 3, 9:04 pm, "Dardo Sordi Bogado" <[EMAIL PROTECTED]> wrote:
<snip>
> Yes, It sounds like a fork. Anyway, maintaining a set of changes to
> the core on top of the svn is easily done with git and quilt (as SCM
> goes) but involves too much work from programmers.
>
> I've tried to make a "thing on top of CakePHP" many times, never got
> time to make it usable. But I'll like to contribute to the effort,
> just don't like the idea of touching the core. There are many things
> you can do providing classes that lay inside the app dir taking
> precendence from the core ones. I think is better to work in a higher
> layer on top of CakePHP instead of modifying the core, the core teams
> is doing an excellent work.
I think, modifying core is necessary evil. To bend it for the
UIMS, it's extremely necessary. Another change that seems extremely
necessary is component vs model namespace confusion (You don't know
what is foo in $this->foo: if model or component). I'll try to prepare
a draft with changes and if others agree, I'll proceed. But, IMHO,
they looks necessary. May also take some ideas from orchid and fase
frameworks. And, thanks for your comments and ideas.
--
<?php echo 'Just another PHP saint'; ?>
Email: rrjanbiah-at-Y!com Blog: http://rajeshanbiah.blogspot.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
