laziness, impatience, and hubris | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
it sounds like you're off to a pretty good start. for small to medium sized projects, that's about how i usually set it up, with a core module and a bunch of smaller scripts. at the very least, try to keep any sql out of the smaller scripts. as the project gets bigger, you can refactor by identifying important classes and putting them in their own seperate modules. be careful about putting too much (any) display logic in that core module though. if you make good use of a templating engine like HTML::Template instead of having functions like 'navigation_bar','print_page_header', etc. it should be pretty easy. HTML::Template, and DBI also go quite well together. and if you're doing testing, stick with the convention and have a subdirectory 't' with your test scripts in it and use Test::Harness to bring them together. good luck with the literate programming. i haven't really found a satisfactory way to do it yet with perl. pod just doesn't cut it for literate programming. In reply to Re: How to organize a CGI project?
by thraxil
|
|