[Javascript] Best Practices
Troy III Ajnej
trojani2000 at hotmail.com
Thu Apr 13 17:45:12 CDT 2006
Not that my reasoning is the best,
but my prefference, logically, would be
to kind of write a "hardcoded html" whenever
possible. That is, to write a totaly expanded
layout of fields etc., and only than, douring
the load complete event, either dissable or
hide extended elements if neccessary!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Troy III
progressive art enterprise
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>From: Triche Osborne <wdlists at triche-osborne.com>
>Reply-To: "\[JavaScript List\]" <javascript at LaTech.edu>
>To: JavaScript List <javascript at LaTech.edu>
>Subject: [Javascript] Best Practices
>Date: Thu, 13 Apr 2006 14:42:58 -0500
>
>I'm building an adaptable form for a scheduling application in which the
>answer from a 3-5 button radio group determines whether or not the JS
>generates a variable number of extra sets of compound date/time fields.
> To do this, I can either hide a single invisible template, then clone the
>template, change the field names and show the resulting fields, or I can
>generate the extra sets "from scratch."
> Is either method preferred? *
>
>Triche Osborne
>
>*Note: If it is material to the answer, the hidden field poses no
>processing problems on the server side, nor does it require extra s-s
>programming to ignore it. The remainder of the form consists of a single
>text input, a textarea, the radio group and one compound date-time field,
>so the hidden field is virtually immaterial to load time.
>
>_______________________________________________
>Javascript mailing list
>Javascript at LaTech.edu
>https://lists.LaTech.edu/mailman/listinfo/javascript
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
More information about the Javascript
mailing list