Comments on: Organizing your code with folders

By: CakePHP Developer Links - PRONIQUE Software

CakePHP Developer Links - PRONIQUE Software — Thu, 11 Aug 2011 00:44:10 +0000

[...] : ArticlesBrief Overview of the new EmailComponent | The Bakery, Everything CakePHP : Articlescakebaker » Organizing your code with foldersHow Easy Are Web Services in CakePHP 1.2? Really Easy! — @TheKeyboardDeprecated stuff in CakePHP [...]

By: cakebaker

cakebaker — Wed, 06 Feb 2008 16:23:17 +0000

@Peter: I think that’s the planned process. And as you already group the views by controller I don’t see the need for a more flexible way to organize views. But as I don’t know what features are planned, it is possible that such a feature will be implemented in the future. We will see :)

By: Peter Lombardo

Peter Lombardo — Tue, 05 Feb 2008 21:29:43 +0000

It’s a nice feature although a bit confusing. Usually there are many views to a single controller so grouping of views would seem higher priority if argued by pure number of files.

We’re grouping controllers as mentioned above and in those controllers we have to specifically set $this->viewPath for cake to find the correct view which is also stored in a subdirectory below views.

Maybe this is the planned process or is it just that the auto-find for views hasn’t been completed yet?

By: cakebaker

cakebaker — Fri, 04 Jan 2008 16:33:23 +0000

@Robby: No, this doesn’t work with views.

@Pravin: You can define multiple database connections in app/config/database.php and then in your model you specify with the variable $useDbConfig which connection should be used by the respective model.

By: Pravin Gundawar

Pravin Gundawar — Fri, 04 Jan 2008 09:34:34 +0000

Similarly how can we use multiple databases as we can organize models and controllers

By: Robby

Robby — Fri, 04 Jan 2008 00:22:37 +0000

I tried doing this with controllers, and it worked nicely (be interesting to see what happens with name conflicts) – but its not working with views. Is it supposed to with views?

By: cakebaker

cakebaker — Thu, 27 Dec 2007 16:57:24 +0000

@Tim: Yes, sometimes it would be really useful if you could group certain classes together. At least to a certain degree you can do that with plug-ins or by setting additional view paths, but it is not very handy in my opinion.

By: Tim Daldini

Tim Daldini — Thu, 27 Dec 2007 00:14:27 +0000

Not sure if this is what Dieter or Zonium is also saying but I think it would be useful to group certain classes, (especially views and controllers) together…maybe even in the same directory.

Sometimes I think it would be cool if controllers could be split up in that way that each action represents a file and these files could be grouped with corresponding views or something.

But then again, that really resembles the ASP.NET codebehind concept…oh well.

By: cakebaker

cakebaker — Thu, 06 Dec 2007 16:49:16 +0000

@brandon: Thanks for your answer!

Yes, you can also add behaviors to that list. I always forget them, as I don’t use them very often ;-)

2) Hm, I don’t understand what you mean with “making 3rd party classes/packages work with cake”. Usually, you don’t have any control about 3rd party classes and you cannot change them (well, you could change them, but if there is an update you have to re-apply your changes).

I would like to see a PHP5-only version of Cake, too. Unfortunately, PHP4 is still widespread…

By: brandon

brandon — Tue, 04 Dec 2007 22:54:09 +0000

@cakebaker

Beauty is in the eye of the beholder :) I see the code and my brain goes “ah, thats a component because it says component”. But I agree with you that the concepts of both helpers and components need to be refined. Actually, IMO, you can add behaviors to that list too :)

Why behaviors? Again, mainly because of naming conflicts. If you have two behaviors that have a semantically equivalent method names (which is legal in PHP) :

Behavior1::test();
Behavior2::test();
Model … $actsAs = array(‘Behavior1′, ‘Behavior2′);
Question: Which behavior does $this->Model->test() refer to?

Not sure if this issue has been looked into or fixed but you can imagine how this would be a major conflict! I have already ran into the problem where you can’t have method names that match Model’s methods: read(), create(), etc.

2. Glad you agree! I think more time should be invested into making 3rd party classes/packages work WITH cake (not along side it). The argument could be made that any class within cake can be extended — but you get into situations where sloppy programming can overwrite dependent code. I’d personally like to see cake branch off a PHP5 version and take advantage of these concepts and practices.

Also, thanks for bringing up testing. That would be so great because then new classes/packages could be run against the core tests (there is no need for developers to create redundant tests).