Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

Re: avoiding excessive number of methods in CGI::Application and DBI modules

by dragonchild (Archbishop)
on May 02, 2005 at 12:46 UTC ( #453196=note: print w/replies, xml ) Need Help??


in reply to avoiding excessive number of methods in CGI::Application and DBI modules

Is there a(n easy) way to avoid this scenario ?

Yes - don't design your application in a way that sucks.

You're thinking as a DBA / programmer, not as a systems analyst. Think about how your application is going to be used. CGI::Application (and similar frameworks) provide user-level mapping to business-level concepts. I had an application that would CRUD over 40 tables. But, because there were only 7 different screens (with options), I had 7 runmodes. Now, based on those options, different things would happen.

Here's another way to look at it - to run reports, I need 2 runmodes - PickReport() and RunReport(). However, I will probably want:

  • A class for each report
  • One or more base classes for those reports
  • A class for each parameter
  • One or more base classes for those parameters
  • One or more templates for each report (We had 3 - HTML, PDF, and XLS)
  • Internationalization support
  • Database layering
  • Images for look'n'feel

In total, I think we ended up with some 250 files supporting 70 reports. Still only 2 runmodes, though ...


The Perfect is the Enemy of the Good.

  • Comment on Re: avoiding excessive number of methods in CGI::Application and DBI modules

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://453196]
help
Chatterbox?
[stevieb]: I really dislike how perlbrew doesn't list your version of perl if a newer minor version bump has happened. eg: I use 5.24.1, but 5.24.2 is available, hiding my 5.24.1. I may look at this, as I made it display correctly in berrybrew in cases like this
[stevieb]: choroba just gleaned your post about Module::Starter. I use it too, pretty much for every dist I write
[LanX]: I remeber M::S (it was dialog driven?) to be buggy
[stevieb]: As far as Dist::Zilla goes, I don't like installing that other than on systems my test platorm runs on. I find it too heavy. I prefer being able to glean a Makefile.PL
[LanX]: what's frustrating me is that a distribution has lots of dupplicated info
[stevieb]: LanX I don't know if it's dialog driven; I just use it in the simplest of terms (just run module-starter at the CLI, and the very last couple of lines are how I use it.

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (7)
As of 2017-08-18 20:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Who is your favorite scientist and why?



























    Results (310 votes). Check out past polls.

    Notices?