You know i was thinking of this exact same thing the other day.
Some ideas I had were creating each modularized class to handle database, templates/formatting, email, etc., loading them at the init of the app, and building each page from there. This would eliminate a lot of non-abstracted SQL, HTML, and even text, as well as organize everything so as to make it much more scaleable.
Instead of having to open up "WebApp.pm", search through 1000+ lines of code to change database connection settings, you could open up "WebApp::DBI.pm" and go right to the sub that handles database connections, wading through maybe 15 lines of code instead of the latter.
Just my $0.02 :-)
In reply to Re: Breaking up a CGI::Application program
by stonecolddevin
in thread Breaking up a CGI::Application program
by debiandude
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |