in reply to Developing Web Form / Database Apps Faster, Better

I agree in theory that this would be a real timesaver. I have developed similar tools to help ease the pain of creating those pesky forms, and the CGI code to process them, but not to the degree you are trying to achieve.

However, what I have learned in the process is that there are so many options to consider for each step, that the time it takes to develop and debug a working program well exceeds the time of just cutting and pasting existing code and then going back to tweak parameters.

For instance, text input. There are the parameters of size, maxlength, value, not to mention css styles or javascript events. And then the validation stuff. Drop downs (Select/Option) are even trickier.

I couldn't figure out an elegant way to do using only Perl. So here are two examples of a table creator and element creator using HTML and Javascript that calls a Perl script. However, I've run out of steam in writing the Perl to generate the final table and form.

Maybe my problem is I'm too picky and want to create all these complicated forms, therefore increasing the workload. Maybe your way is a lot more elegant.

My advice is to write a test script to see what you're minimally up against before committing the time to it.

Best of luck!

  • Comment on Re: Developing Web Form / Database Apps Faster, Better

Replies are listed 'Best First'.
Re: Re: Developing Web Form / Database Apps Faster, Better
by chimni (Pilgrim) on Oct 14, 2003 at 06:36 UTC

    Hi brad,
    I saw your table creator and element creator forms.
    The idea is nice and i had also flirted with it once.
    I was wondering if i could have a look at the perl scripts behind those forms (hope its not proprietarty :))
    Thanks and regards, chimni

Re: Re: Developing Web Form / Database Apps Faster, Better
by hey_david (Sexton) on Oct 17, 2003 at 21:13 UTC
    Thanks for your replies.

    Enlil, I did look at CGI::Builder, and went through its tutorial. I wish I'd seen it a year ago. It's obviously a fairly mature piece of work, and the documentation is excellent.

    etcShadow and bradcathey, I take your cautionary advice to heart, and am thinking of shying away from my original plans for an all-in-one solution.

    Thanks again,

    David