Re: Best Practices in Directory Layout?

I prefer the second method. It allows you to look at one folder and see everything that that one process can and will do. Jim Lucas ----- Original Message ----- From: "motorpsychkill" <x@americanmotorcycle.com> To: "Php General List" <php-general@lists.php.net> Sent: Friday, May 30, 2003 12:04 PM Subject: [PHP] Best Practices in Directory Layout? > I've wanted to get some input on this for a while... I've recently been > designing PHP applications using the following directory architecture: > > main/ > master php files (e.g. addphoto.php) > > includes/ > forms/ > validation/ > process/ > > So, using the addphoto.php example, there would be a file in the forms > directory that read: addphoto_form.inc > In the validation directory, there would be: addphoto_validation.inc > And in the process directory, addphoto_process.inc > > The master php file (addphoto.php) would simply pull the form, validate it > and process it. Now the problem is, as I add more master files (currently > around 50), the forms, validation and process directories get equally large. > Would it make more sense to simply allocate each master file its own > directory like this: > > addphoto/ > addphoto_form.inc > addphoto_validate.inc > addphoto_process.inc > > And so, with each new master file (for a task or module), there would be a > new directory. > > I'm not sure which is better form, but I find that using the first method is > easier when adding new tasks for the application to execute. I've looked at > the layout of a couple big php applications and they all seem to do things > differently. Any thoughts are welcome!! > > -m > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >