[Solar-talk] Newbie Directory Structure Question

Michael Caplan mcaplan at labnet.net
Mon Sep 25 09:04:05 PDT 2006


Thanks Paul,
 
That was exactly what I was looking for!  Thanks for the details explanation.
 
BTW, is there a search interface to the mailing list?
 
Mucho Gracias,
 
Michael

________________________________

From: solar-talk-bounces at lists.solarphp.com on behalf of Paul M Jones
Sent: Mon 9/25/2006 10:02 AM
To: solar-talk at lists.solarphp.com
Subject: Re: [Solar-talk] Newbie Directory Structure Question



On Sep 25, 2006, at 10:43 AM, Michael Caplan wrote:

> Thanks for the response.  Yes I did go through the skeleton 
> application.  I'm not sure what is meant by Helper,

(Those are view helpers specific to that particular application.)

> but besides this, there are no recommendations that I can see on 
> vendor and vendor application libraries placement.

I think I understand what you're getting at.  Are you thinking in 
terms of having one directory tree for the application(s), and a 
separate directory tree for any libraries that the application(s) 
might need?  For example, assuming your vendor name is Caplan ...

     Caplan/
         Libname.php
        Libname/
             (etc)

     CaplanApp/
         Foo.php
         Foo/
             View/
             Locale/
             (etc)
         Bar.php
         Bar/
             View/
             Locale/
             (etc)

... yes?  If that's not what you had in mind, please correct me.

The recommendation, in general, is to keep both apps and libs in the 
same vendor tree.  Thus:

     Caplan/
         Libname.php
         Libname/
             (etc)
        App/
             Foo.php
             Foo/
                 View/
                 Locale/
                 (etc)
             Bar.php
             Bar/
                 View/
                 Locale/
                 (etc)

Strictly speaking, that's only a recommendation, not a requirement.  
You may have multiple projects that depend on libs from multiple 
other project name spaces ("vendor" spaces), and you may wish to go 
so far as to keep you apps in a separate project name space from your 
common libraries.

Hope this helps, please let me know if it does not.



--

Paul M. Jones  <http://paul-m-jones.com>

Solar: Simple Object Library and Application Repository
for PHP5.   <http://solarphp.com>

Savant: The simple, elegant, and powerful solution for
templates in PHP.   <http://phpsavant.com>


_______________________________________________
solar-talk mailing list
solar-talk at lists.solarphp.com
http://mail.killersoft.com/mailman/listinfo/solar-talk







E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message.

The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 8145 bytes
Desc: not available
Url : http://mail.killersoft.com/pipermail/solar-talk/attachments/20060925/ba398fcd/attachment-0001.bin 


More information about the solar-talk mailing list