Re: Displaying text and populating form fields

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61140
interpreted = N
texte = A few years ago, I ran some exhaustive tests as well, and my conclusions are the same as Ken's. People are free to code the way they like, but for me, [input] is the only way to wrap form fields. [url] in these fields renders spaces as %20, and so forth, which is no good for the reasons Ken states. use [input]; use [url]. Easy to remember. To Ken's excellent guidelines, I'd add that ANY form field, not just type=text and hidden. Radio buttons, checkboxes, select - they all hold the value as a quoted element, all subject to being botched by an errant quote mark. In fact, if any html element has a webDNA variable inserted (it's going to be in quotes by default), I use [input]; not just forms. For instance, alt="[some description]" in an image tag. I amended my standard conversions years ago to include the
tag with no ill effect. I also have a host of other custom convchars db for special uses, like within a javascript but I won't go into it here and now. >All I really want is to come up with a definitive set of rules for >coding in these situations. If we can work together to test every >possible situation, maybe we can actually come up with a >comprehensive set of guidelines to refer to from now on. SMSI is >not going to do this for us, so let's do it ourselves. It shouldn't >take that much effort, right? Agreed. We should be adding this stuff to the online docs. In fact, under [input], I added something like the above two years ago. Ken: if nobody else wants to play, at least I'll compare notes with you. I keep track of this stuff for my own sanity anyway, and also made a little date tester at http://terryfic3d.com/datemath.html for anyone to play with when date comparisons don't do what you think they should. One of these days I'll add a date formatting section to it. Terry >From: Kenneth Grome >Subject: Displaying text and populating form fields ... >Content-Type: text/plain; charset="us-ascii" ; format="flowed" > >My relatively good (but not guaranteed) tests confirm the following: ....etc. ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Displaying text and populating form fields (again) ( Kenneth Grome 2005)
  2. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  3. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  4. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  5. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  6. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  7. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  8. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  9. Displaying text and populating form fields (again) ( eLists 2005)
  10. Re: Displaying text and populating form fields (again) ( "eLists" 2005)
  11. Re: Displaying text and populating form fields ( eLists 2005)
  12. Re: Displaying text and populating form fields ( "eLists" 2005)
  13. Re: Displaying text and populating form fields ( John Peacock 2005)
  14. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  15. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  16. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  17. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  18. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  19. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  20. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  21. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  22. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  23. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  24. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  25. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  26. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  27. Re: Displaying text and populating form fields ( John Peacock 2005)
  28. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  29. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  30. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  31. Displaying text and populating form fields ... ( Kenneth Grome 2005)
A few years ago, I ran some exhaustive tests as well, and my conclusions are the same as Ken's. People are free to code the way they like, but for me, [input] is the only way to wrap form fields. [url] in these fields renders spaces as %20, and so forth, which is no good for the reasons Ken states. use [input]; use [url]. Easy to remember. To Ken's excellent guidelines, I'd add that ANY form field, not just type=text and hidden. Radio buttons, checkboxes, select - they all hold the value as a quoted element, all subject to being botched by an errant quote mark. In fact, if any html element has a webDNA variable inserted (it's going to be in quotes by default), I use [input]; not just forms. For instance, alt="[some description]" in an image tag. I amended my standard conversions years ago to include the
tag with no ill effect. I also have a host of other custom convchars db for special uses, like within a javascript but I won't go into it here and now. >All I really want is to come up with a definitive set of rules for >coding in these situations. If we can work together to test every >possible situation, maybe we can actually come up with a >comprehensive set of guidelines to refer to from now on. SMSI is >not going to do this for us, so let's do it ourselves. It shouldn't >take that much effort, right? Agreed. We should be adding this stuff to the online docs. In fact, under [input], I added something like the above two years ago. Ken: if nobody else wants to play, at least I'll compare notes with you. I keep track of this stuff for my own sanity anyway, and also made a little date tester at http://terryfic3d.com/datemath.html for anyone to play with when date comparisons don't do what you think they should. One of these days I'll add a date formatting section to it. Terry >From: Kenneth Grome >Subject: Displaying text and populating form fields ... >Content-Type: text/plain; charset="us-ascii" ; format="flowed" > >My relatively good (but not guaranteed) tests confirm the following: ....etc. ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Terry Wilson

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Stumpted Again (1997) [WebDNA] try/except (2015) changing boxes (2008) Word wrapping (1997) Nested tags count question (1997) passing large amount of text in post form (2005) RE: WebCatalog2 for NT Beta Request (1997) Unexpected comparison behavior change in 4.5.1 (2003) [WebDNA] WebDNA glitch, no response required ... (2009) GuestBook example (1997) Part Html part WebDNA (1997) [URL] around a [sendmail] recipient? (2000) Best Catalog Program (1998) [WriteFile] problems (1997) error (2000) Banner Ad example (Typhoon) and WebCatalog (1997) encryption madness (2003) Updating checkboxes made easy !!! (1998) Mac v. NT (1998) sort problems....bug or brain fart? (1997)