And applying two naming conventions to similar things is kind of
silly. The issues of camelcase folders was discussed on the cakephp-
core list and the general consensus there was to camelcase folders.
This meant the eventual namespace names would be cased the same as
classnames.
-Mark
On Nov
Having been a long-time user of CakePHP 1.3, I was wondering why file and
folder names are now CamelCased rather than just being lowercase and
underscored?
Personally, I'm a fan of using lowercase and underscores in filenames (then
CamelCase in my actual class declarations) so this change is
You miss the announcement or fail to read it?
Third bullet point
http://bakery.cakephp.org/articles/lorenzo/2011/10/16/cakephp_2_0_released
--
Larry E. Masters
On Thu, Nov 3, 2011 at 2:02 PM, Martin Bean mar...@mcbwebdesign.co.ukwrote:
Having been a long-time user of CakePHP 1.3, I was
http://book.cakephp.org/2.0/en/appendices/2-0-migration-guide.html
File and Folder
naminghttp://book.cakephp.org/2.0/en/appendices/2-0-migration-guide.html#file-and-folder-naming
In CakePHP 2.0 we rethought the way we are structuring our files and
folders. Given that PHP 5.3 is supporting
Camel cased file names for PHP classes are the best approach and helps
for simple 1 to 1 autoloading. It's based off of Javas packaging and
naming architecture.
However, camel cased folders are evil.
On Nov 3, 1:16 pm, Thiago Belem cont...@thiagobelem.net wrote:
