I'd like our structure to be something like:
./lib/
./lib/MyApp.pm
./lib/MyApp/Model
./lib/MyApp/Model/DB.pm
./lib/MyApp/View
./lib/MyApp/View/TT.pm
./lib/MyApp/Controller
./lib/MyApp/Controller/Auth
./lib/MyApp/Controller/User
./lib/MyApp/Controller/...
./lib/MyApp/Schema/...
./lib/MyApp/Form/Auth/Login.pm
./lib/MyApp/Form/Auth/Register.pm
./lib/MyApp/Form/...
Hi,
I prefer instead of
catalyst.pl MyApp
run
catalyst.pl MyApp::Catalyst
and keep my model, helpers, or other application
modules below MyApp::Catalyst, leaving MyApp::Catalyst for
web interface modules.
using DBIC::Schema i create it under MyApp::Schema
later building model in MyApp::Model and importing
it into Catalyst Model using Catalyst::Model::Adaptor
Co catalyst is rather a big dispatcher and converter
which on input maps web parameters to model parameters and
model data to web methods specifications and renders it to
html or JSON on output.
--
regards
piotr
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
