Comments on: Directory Structures (again!) http://akrabat.com/2006/09/15/directory-structures-again/ Developing PHP and XUL Software in the Real World Thu, 21 Aug 2008 23:00:44 +0000 http://wordpress.org/?v=2.5.1 By: Rob... http://akrabat.com/2006/09/15/directory-structures-again/#comment-5983 Rob... Wed, 25 Oct 2006 13:13:03 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5983 Hi JMF, We're on CVS :) If we moved to SVN, we'd use externals. Though we'd probably create a bash script that set up the correct externals on project creation. Rob... Hi JMF,

We're on CVS :)

If we moved to SVN, we'd use externals. Though we'd probably create a bash script that set up the correct externals on project creation.

Rob…

]]> By: JMF http://akrabat.com/2006/09/15/directory-structures-again/#comment-5980 JMF Wed, 25 Oct 2006 10:44:48 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5980 >I have a bash script that allows me to check out my main project and all its dependent libraries from one command. With Subversion you could use the property svn:external to do this automatically. (see http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html) >I have a bash script that allows me to check out my main project and all its dependent libraries from one command.

With Subversion you could use the property svn:external to do this automatically. (see http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html)

]]> By: pcdinh http://akrabat.com/2006/09/15/directory-structures-again/#comment-5607 pcdinh Wed, 27 Sep 2006 14:51:45 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5607 That is a very good idea, Rob. I think of a structure like this layouts/ ------template1 ------template2 It should be more flexible for us to have switchable, separated, distributable templates system which can see in Wordpress, Joomla, Drupal and many popular CMSs or forums. What do your think about it? That is a very good idea, Rob.
I think of a structure like this

layouts/
——template1
——template2

It should be more flexible for us to have switchable, separated, distributable templates system which can see in Wordpress, Joomla, Drupal and many popular CMSs or forums.

What do your think about it?

]]> By: Rob... http://akrabat.com/2006/09/15/directory-structures-again/#comment-5577 Rob... Mon, 25 Sep 2006 08:22:28 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5577 Certainly, all the theming I've done to date has been CSS based. Certainly, all the theming I've done to date has been CSS based.

]]> By: sch http://akrabat.com/2006/09/15/directory-structures-again/#comment-5569 sch Sat, 23 Sep 2006 15:17:14 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5569 w3c's main goal is to use CSS (not HTML) for changing skins/layots/whatsoever. it may be sometimes hard to build css layouts... but in the matters of skins... i don't see any reason why not to use css. i personally like the idea of joined controllers/views, although in a large application may get crowded. w3c's main goal is to use CSS (not HTML) for changing skins/layots/whatsoever. it may be sometimes hard to build css layouts… but in the matters of skins… i don't see any reason why not to use css.
i personally like the idea of joined controllers/views, although in a large application may get crowded.

]]> By: Rob... http://akrabat.com/2006/09/15/directory-structures-again/#comment-5467 Rob... Sun, 17 Sep 2006 08:10:45 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5467 I have to admit that the concept of multiple skins is the main reason I can see for a separate views directory. So far, I've only ever had to have multiple themes for two sites and in both cases, the build allowed for all changes to be done by using a different CSS file. I've never risked running two customers' sites from one directory, so can't comment on that :) All interesting stuff, isn't it ?! I have to admit that the concept of multiple skins is the main reason I can see for a separate views directory. So far, I've only ever had to have multiple themes for two sites and in both cases, the build allowed for all changes to be done by using a different CSS file.

I've never risked running two customers' sites from one directory, so can't comment on that :)

All interesting stuff, isn't it ?!

]]> By: Nico Edtinger http://akrabat.com/2006/09/15/directory-structures-again/#comment-5450 Nico Edtinger Sun, 17 Sep 2006 00:09:47 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5450 The views need a seperate directory for an obvious reason: skins/layouts/what-ever-you-like-to-call-them. The design of a page or webapp changes more often than the code/functionality and some even need more than one - i.e. if you have a webapp runnning on your own host for different customers. It's also very common to hand off the HTML/Template stuff to someone who's better in doing "webdesign". So you could even create one very simple skin that just works and the other person copies that to the real skin and adds all that pretty stuff around it. Works very well for us. The views need a seperate directory for an obvious reason: skins/layouts/what-ever-you-like-to-call-them. The design of a page or webapp changes more often than the code/functionality and some even need more than one - i.e. if you have a webapp runnning on your own host for different customers.

It's also very common to hand off the HTML/Template stuff to someone who's better in doing "webdesign". So you could even create one very simple skin that just works and the other person copies that to the real skin and adds all that pretty stuff around it. Works very well for us.

]]> By: Rob... http://akrabat.com/2006/09/15/directory-structures-again/#comment-5439 Rob... Sat, 16 Sep 2006 13:10:49 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5439 Feel free to disagree away! It helps me learn! To me, MVC is about separation of concerns, not separation via directories. Dunno really. Will have to play with it in a real application and see what happens. Feel free to disagree away! It helps me learn!

To me, MVC is about separation of concerns, not separation via directories. Dunno really. Will have to play with it in a real application and see what happens.

]]> By: Geoffrey http://akrabat.com/2006/09/15/directory-structures-again/#comment-5434 Geoffrey Sat, 16 Sep 2006 11:24:29 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5434 Once again, I must disagree with you Rob :-) The grouping you point out is also done with views, as, in layout v1 of course, you group views actions onto a {controllerName} directory so all views related to a specific controller are finally in the same place. Now, about why I think putting views and controllers in the same directory is not a good idea, it's mainly because we are in an MVC context. As you surely know, this kind of architecture is based on layering, and by putting views and controllers in the same physical place, you break this layering. That's it. In practice, one day, you might end up with what I'd call sapi-dependant views. In this case, you'll be happy to be able to have a views/{php_sapi_name()}/ tree, which is way simpler to manage if *all* your views are in the *same* location. By the way, the same apply if you want to have a "theme-enabled" application, with views/{themeName}/. Once again, I must disagree with you Rob :-) The grouping you point out is also done with views, as, in layout v1 of course, you group views actions onto a {controllerName} directory so all views related to a specific controller are finally in the same place.

Now, about why I think putting views and controllers in the same directory is not a good idea, it's mainly because we are in an MVC context. As you surely know, this kind of architecture is based on layering, and by putting views and controllers in the same physical place, you break this layering. That's it. In practice, one day, you might end up with what I'd call sapi-dependant views. In this case, you'll be happy to be able to have a views/{php_sapi_name()}/ tree, which is way simpler to manage if *all* your views are in the *same* location. By the way, the same apply if you want to have a "theme-enabled" application, with views/{themeName}/.

]]> By: Rob... http://akrabat.com/2006/09/15/directory-structures-again/#comment-5430 Rob... Sat, 16 Sep 2006 08:07:58 +0000 http://www.akrabat.com/2006/09/15/directory-structures-again/#comment-5430 Geoffrey, I suspect that I am in a minority finding it a pain :) Out of interest, why do you think putting views and controllers in the same directory is not a good idea? In every other aspect of programming we group by logical functionality, not by type. i.e. you don't create a controller called "add" with actions of "news", "article", "user", but you create three controllers called "news", "article" and "user", each with an "add" action. This is very obvious grouping. Now, when we come our files, we don't group the news files together, we group the controllers together and the views together, rather than by what the files do. Why is that? Geoffrey,

I suspect that I am in a minority finding it a pain :)

Out of interest, why do you think putting views and controllers in the same directory is not a good idea? In every other aspect of programming we group by logical functionality, not by type. i.e. you don't create a controller called "add" with actions of "news", "article", "user", but you create three controllers called "news", "article" and "user", each with an "add" action. This is very obvious grouping.

Now, when we come our files, we don't group the news files together, we group the controllers together and the views together, rather than by what the files do. Why is that?

]]>