Charlie,
> 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 don't look at it is giving up control--I think that's the cool part about
it. The way I view it, is it gives a solid footprint in which to build off
of.
While for most people, qForms probably does everything they need it to
do--but obviously there are times when you want to do more. That's when
customizing the API (overriding default methods or simply adding new
methods) comes in handy.
Since you enjoy writing JS, you'll know doubt know that there are
frustrations with it to. For example, a client decided they want a select
element to handle certain functionality, so you wrote your JS around
interacting w/a select box.
Well, now they call you up and want it changed to a series of radio buttons.
Instead of this taking you like a minute to do, you've got to re-write your
JS to handling dealing w/radio buttons. Even if you already have code in
place to handle radio buttons, you're probably still going to have to make
changes.
However, w/qForms the odds are you don't have to make changes to your code
at all! You just need to change the elements. If you've stuck to using the
getValue() and setValue() methods for any of the custom hooks you've
written, your functions don't have to change. You use the same code.
I see this as a huge gain.
> 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 :)
Glad to hear the word on the street is a good one. :) I'm actually working
on v2--which will be much more flexible and expandable.
> 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.
I you'll find qForms doesn't diminish what you're doing w/JS, it just makes
what you're trying to do easier. I still write a ton of custom JS hooks into
my application, but the amount of code I write is considerable less now.
I can now focus on defining behavior and improving the UI, instead of
spending time re-creating code/procedures I've done in the past.
-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
Get the mailserver that powers this list at
http://www.coolfusion.com
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
