--- Matt S Trout <[EMAIL PROTECTED]> wrote: > On Tue, May 15, 2007 at 12:10:15AM -0700, mla wrote: > > But I'm thinking a better layout would be: > > > > /lib > > ./lib/Try > > ./lib/Try/Catalyst/Model > > ./lib/Try/Catalyst/Model/DB.pm > > ./lib/Try/Catalyst/View > > ./lib/Try/Catalyst/View/TT.pm > > ./lib/Try/Catalyst/Controller > > ./lib/Try/Catalyst/Controller/Root.pm > > ./lib/Try/Catalyst/Controller/Users.pm > > ./lib/Try/DB.pm > > ./lib/Try/User.pm > > ./lib/Try.pm > > > > That makes the relationship between M/V/C and > Catalyst explicit, and > > leaves the rest of the namespace available for > generic use. > > I tend to use MyApp::Web rather than ::Catalyst > since then if I need a > second web interface I can create MyApp::WebAdmin or > whatever.
MyApp::Web is also the way I do it (now) for the same reasons as above. Although sometimes I make it more project specific like MyApp::Portal and then MyApp::Services if I'm exposing an API like on my current project. Vote++ for this as a best practice. --John > > -- > Matt S Trout Need help with your > Catalyst or DBIx::Class project? > Technical Director Want a managed development > or deployment platform? > Shadowcat Systems Ltd. Contact mst (at) > shadowcatsystems.co.uk for a quote > http://chainsawblues.vox.com/ > http://www.shadowcatsystems.co.uk/ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
