Re: SHOWIF/HIDEIF empty fields
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 61918
interpreted = N
texte = I'm in Ken's camp. On my very first site I used the convention of prefixing input form names because that's what people said to do on the list, and I didn't know squat. Now, 7 years later, I still curse when I dig into one of those pages and have to see what the hell is happening on the form input page, etc. (now I also keep most stuff on one page via includes and showifs). I now use the actual fieldnames and have no trouble at all. I will set a [thisfieldname] when I need to deal with a db fieldname vs. an incoming variable fieldname, and it's very controllable and understandable, no surprises. I dislike using getchars to wrench something back into shape; just more code to paw through. I think anyone who would have to look at my code later would find it clean and straightforward. I also reuse code to a great extent, and having the same fieldnames from site to site is an enormous timesaver. When making a new site, I can plop in a shared include from my globals folder, and lookie there, it just works! Most of my DBs share these fieldnames:, cat, lib, sec, SKU, title, desc, key, rank, vis, price, datein, dateout, imagefile, imageheight, imagewidth and so forth. Not that they're always used, or used for the apparent data, but it leaves my databases highly flexible. Just my .02 to defend Ken; he gets razzed so much here. Terry >Ahh, your probably one of those that cause me great frustration when I have >to edit someone elses code and there is a bunch of alike named varialbes... >not to mention the use of reserved variable names (but thats another >story) ;-) -- -- Terry Wilson | terry@terryfic.com | http://terryfic.com creator of: http://WhosComing.com - a simplified, affordable online reservation system http://WhosBringingWhat.com - online potluck signup sheet -------------------------------------------------------------------------- ------------------------------------------------------------- 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:
I'm in Ken's camp. On my very first site I used the convention of prefixing input form names because that's what people said to do on the list, and I didn't know squat. Now, 7 years later, I still curse when I dig into one of those pages and have to see what the hell is happening on the form input page, etc. (now I also keep most stuff on one page via includes and showifs). I now use the actual fieldnames and have no trouble at all. I will set a [thisfieldname] when I need to deal with a db fieldname vs. an incoming variable fieldname, and it's very controllable and understandable, no surprises. I dislike using getchars to wrench something back into shape; just more code to paw through. I think anyone who would have to look at my code later would find it clean and straightforward. I also reuse code to a great extent, and having the same fieldnames from site to site is an enormous timesaver. When making a new site, I can plop in a shared include from my globals folder, and lookie there, it just works! Most of my DBs share these fieldnames:, cat, lib, sec, SKU, title, desc, key, rank, vis, price, datein, dateout, imagefile, imageheight, imagewidth and so forth. Not that they're always used, or used for the apparent data, but it leaves my databases highly flexible. Just my .02 to defend Ken; he gets razzed so much here. Terry >Ahh, your probably one of those that cause me great frustration when I have >to edit someone elses code and there is a bunch of alike named varialbes... >not to mention the use of reserved variable names (but thats another >story) ;-) -- -- Terry Wilson | terry@terryfic.com | http://terryfic.com creator of: http://WhosComing.com - a simplified, affordable online reservation system http://WhosBringingWhat.com - online potluck signup sheet -------------------------------------------------------------------------- ------------------------------------------------------------- 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:
RE: E-mailer error codes (1997)
[shell] (2002)
Help (1999)
Associative lookup style? (1997)
Almost a there but..bye bye NetCloak (1997)
Running _every_ page through WebCat ? (1997)
weird convertchars behavior (2000)
post (2000)
Prevent multiple appends with Reload Button (1997)
TCPConnect strange behaviour (2004)
Variables for chat (1997)
WC Database Format (1997)
WebCatalog2 Feature Feedback (1996)
Template Cache problem -- new plugin for ya' (2000)
Ship Cost Calculated via Subtotal (1998)
WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997)
What is the syntax for MIME type on Apache server? (2000)
Uh...can someone help me out with the b10? (1997)
Trouble with carts (2000)
RE: error count with $purchase (1997)