Hi Dan:
I think my 'reluctance' to look at qForms is because...well, frankly I enjoy
writing js. I'm hesitant to give up that 'control' as it were.
I will look at it tho...if for no other reason that simple curiosity. I
think it's pretty amazing that, as I said below, I've never heard anything
but rave reviews of it. I don't believe I've ever heard anybody say they
don't like it...or even anybody who says they could take it or leave it.
Everybody I know who's used it absolutely LOVES it. So there's gotta be
something there :)
I appreciate your response. I'm responding publically only because there
may be others who feel the same way I do ("if i can write js, why do i need
qForms"), who may find this interesting.
thanks :)
charlie
----- Original Message -----
From: "Dan G. Switzer, II" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Tuesday, July 22, 2003 8:04 AM
Subject: RE: CFForm madness. 0_0
> Charlie,
>
> > If you don't want to dive right into the Qforms API, i put a short
> > 'tutorial' online to show some js form field validation (a couple that I
> > don't believe can be accomplished thru cfform...but i could be wrong
> > there).
> >
> > It's at http://charlie.griefer.com/js_validation.html (view source).
> >
> > As far as Qforms...I've not used it myself, but I have yet to hear
> > anything
> > but rave reviews from people who have.
>
> To give you an idea how easy qForms is to implement, here's the entire
block
> of code needed to reproduce your example template:
>
> <script language="JavaScript" src="/lib/qforms.js"></script>
> <script language="JavaScript">
> <!--//
> qFormAPI.setLibraryPath("/lib/");
> qFormAPI.include("*");
>
> // load this function during the body "onload" event
> function init(){
> oForm = new qForm("myForm");
> // require the following fields
>
> oForm.required("textInput1,textInput2,mySelectInput,sex,myTextarea");
> // make sure the textInput2 field contains at least 10 characters
> oForm.textInput2.validateLengthGT(9);
> }
> //-->
> </script>
>
>
> Most of the code you can store in a snippet--since the odds are it doesn't
> change much (maybe the path to the qForms will from project to project,
but
> on a single site, you always point to the same location so that you get
the
> benefit of the code being cached.)
>
> Since qForms treats all forms alike--i.e. the getValue() method will
return
> the value for a radio, checkbox, select, text, hidden, textbox, etc
element,
> all you need to do is mark a field required and qForms handles the rest
for
> you.
>
> -Dan
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community.
http://www.fusionauthority.com/ads.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
