in reply to Re: Need buttons on web page for retrieving database values
in thread Need buttons on web page for retrieving database values

Just as an aside--the reason I suggested the former is because, for my own purposes, I've wanted to display a row of buttons; and if I put these into separate forms, browsers generally seem to insert paragraph breaks between the forms, which thwarts any attempt at horizontal alignment. That's more of an HTML issue, of course.

In general, I'd agree w/ you about separating different pieces of functionality; though a general approach I've been taking recently is to have one main script which contains some dispatch code--upon receiving a new request, it determines the nature of the request, then hands it off to the appropriate handler, where each handler is generally stored in its own module.

  • Comment on RE: Re: Need buttons on web page for retrieving database values

Replies are listed 'Best First'.
RE: RE: Re: Need buttons on web page for retrieving database values
by plaid (Chaplain) on Mar 28, 2000 at 07:42 UTC
    I've also run across the big vertical break between submit buttons from different forms on a page. One thing I've done (which is far from optimal, but looks better than the big gap) is to stick the buttons in a table, each in its own <td>. This at least gives the illusion of a row of buttons.

    The approach of having one main script dispatching calls to various handlers sounds like a good one.. I just wanted to make sure and point out the performance benefit of not having to parse 2000 lines of code to then only execute 20. I've seen this done way too many times in beginning CGIs.