2009年6月8日星期一

Re: [fw-mvc] Best practice for default module directory

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkotpv8ACgkQ7bkAtAithusBzACgws/19rBCzIU5zv4N3sTxzT/6
yUYAn0pAirCC3tM90dDqbRfhHoCJjZZ/
=5dc7
-----END PGP SIGNATURE-----
Matthew Weier O'Phinney wrote:
> -- Brenton Alker <brenton@tekerson.com> wrote
> (on Monday, 08 June 2009, 10:42 PM +1000):
>> Is the "correct" location for the default module directly in the
>> application directory, or in the modules/default directory?
>>
>> I think I read that the initial intention was for it to go in the
>> application directory but general usage was in modules/default. Given
>> Zend_Tool creating a non-modular layout by default, I am currently
>> leaning towards the application directory but am wondering if there is
>> either a general consensus or an "official" recommendation.
>
> Actually, Zend_Tool now has module support (as of 1.8.2). When you
> create a module, it places it in application/modules/<modulename>, and
> creates the appropriate directory structure.

Yes, am aware of Zend_Tool module support, I just meant that before you
`zf.sh create module foo`, the application is non-modular (ie, the
default is directly under application/)

> The default module is assumed to be directly under application/, and
> this is how Zend_Tool was written. The idea is that your default module
> is typically non-reusable, and very site-specific, and as such falls
> outside of your other modules (which should typically be re-usable).

This is what I thought, just wanted to verify before going any further.
Thanks.

--

Brenton Alker
PHP Developer - Brisbane, Australia

http://blog.tekerson.com/

没有评论: