James,
>Some forms of validation are completely impractical with pure client
>side JS. One good example I've seen is when a user is registering for
>a new username on a system; many systems leave this to the server, but
>I've seen systems with very slick AJAX functionality that checks for
>an exis
Some forms of validation are completely impractical with pure client
side JS. One good example I've seen is when a user is registering for
a new username on a system; many systems leave this to the server, but
I've seen systems with very slick AJAX functionality that checks for
an existing username
>Until the maintenance bill goes to the customer and they ask why the
>JS and the CF routines had to be written twice... But if you have rich
>customers, no problem.
It still confuses me on how you guys think adding pure client-side
validation is so difficult. From many of the comments on here, yo
Lucky you - mine often become experts as soon as I hand over the app.
On 5/1/07, Claude Schneegans <[EMAIL PROTECTED]> wrote:
> >>and they ask why the JS and the CF routines had to be written
> twice... But if you have rich
> customers, no problem.
>
> My customers are not rich, (my taylor is) bu
LOL!
-Original Message-
From: Claude Schneegans [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 01, 2007 8:51 AM
To: CF-Talk
Subject: Re: client side and server side validation
>>and they ask why the JS and the CF routines had to be written
twice... But if you have rich
custome
>>and they ask why the JS and the CF routines had to be written
twice... But if you have rich
customers, no problem.
My customers are not rich, (my taylor is) but they don't even know what
is JS or CF anyway ;-)
--
___
REUSE CODE! Use custom tags;
See http:
Until the maintenance bill goes to the customer and they ask why the
JS and the CF routines had to be written twice... But if you have rich
customers, no problem.
On 5/1/07, Claude Schneegans <[EMAIL PROTECTED]> wrote:
> The purpose of an application is to be user friendly, not programmer
> friend
>>This cuts down on duplication, meaning that
only one validation routine needs to be maintained.
Fine, but it is means more overhead for the server, thus less efficiency
for the user.
The purpose of an application is to be user friendly, not programmer
friendly.
And Javascript validation clie
Quite right. One benefit of using the AJAX method is that the same
server-side routine can be used via AJAX before posting (for the
client's benefit) and also server-side after posting (for the
application's benefit). This cuts down on duplication, meaning that
only one validation routine needs to
client side to trigger it.
-Original Message-
From: Les Mizzell [mailto:[EMAIL PROTECTED]
Sent: Monday, April 30, 2007 1:14 PM
To: CF-Talk
Subject: Re: client side and server side validation
>>> What if the user has javascript turned off?
>> Furthermore: what if he does not
>>> What if the user has javascript turned off?
>> Furthermore: what if he does not have Internet? Hmmm?
> or a computer
Well, snide remarks aside - it *is* an issue.
I have a particular application running where I've found that almost 35%
of the folks using it do not have javascript ena
or a computer
-Original Message-
From: Claude Schneegans [mailto:[EMAIL PROTECTED]
Sent: Monday, April 30, 2007 9:15 AM
To: CF-Talk
Subject: Re: client side and server side validation
>>What if the user has javascript turned off?
Furthermore: what if he does not have In
>>What if the user has javascript turned off?
Furthermore: what if he does not have Internet? Hmmm?
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to this address: [EMAIL PROTECTED])
Than
validation
Good question - so what do you recommend?
P
-Original Message-
From: Les Mizzell [mailto:[EMAIL PROTECTED]
Sent: Monday, 30 April 2007 11:59 AM
To: CF-Talk
Subject: Re: client side and server side validation
> Where you have...
> onsubmit="return validate
Good question - so what do you recommend?
P
-Original Message-
From: Les Mizzell [mailto:[EMAIL PROTECTED]
Sent: Monday, 30 April 2007 11:59 AM
To: CF-Talk
Subject: Re: client side and server side validation
> Where you have...
> onsubmit="return validateFields(this);&qu
> Where you have...
> onsubmit="return validateFields(this);"
and I'll throw the monkey wrench in.
What if the user has javascript turned off?
Have you planned for that?
~|
Create robust enterprise, web RIAs.
Upgrade & i
Where you have...
onsubmit="return validateFields(this);"
remove that and put this on the submit button for the form.
Onclick="validateFields()"
Your function also always returns true. You need an else...
Here it is all together...
function validateFields()
{
if (document.virtucalc
17 matches
Mail list logo
