WebDNA FAQ or FAQs -- was "weird problem"
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 56710
interpreted = N
texte = Sounds like we need a FAQ for posting to the Talk List. I think Ken's detailed message explains what to expect here and seems to mirror what I do when debugging my own code before posting here. Here's some free advice for those new here: Strip down to bare WebDNA. Are you seeing the right text where it needs to be? Use some sort of debugging code to see what variables have been used and what the values are. This let's you spot when things don't happen as you've planned. Strip down to bare HTML using hardcoded values, i.e. no WebDNA variables. Then roll in CSS a bit at a time. If everything "appears" right, then roll in Javascript to see if it behaves right. This should be standard practice for coders when trying to track something down, although I welcome other debugging tips (such as re-using working code libraries). You should be able to isolate the problem to either a WebDNA issue or an HTML/CSS/JS issue. If it's a WebDNA issue, check the archives to see if it's been solved before. As you might imagine, it's not productive to post questions that have been answered before, particularly recent ones. If the archives don't help, feel free to post here the WebDNA code that is not working. Without the code, it's impossible to spot the problem so you'll only get help, if any, in the form of educated guesses. When you have an HTML/CSS/JS (or any non-WebDNA) issue, put OT: (Off Topic) at the beginning of the subject line so others know that it's not a WebDNA issue. That way people can skip it quickly if they don't want to deal with OT issues. I think captures what most of us have been doing and expect. Bill -----Original Message----- From: Terry Wilson
Sent: Thu, 11 Mar 2004 10:22:58 -0500 To: (WebDNA Talk) Subject: Re: FW: weird problem If I might chime in here... When I have a problem, I find that in the process extracting the essential code into an email, I usually discover the answer on my own. So there's more than one benefit for keeping postings concise. Terry >My suggestion for posting your original webdna code is even simpler: > >1- Remove all the HTML and javascript, then post ONLY the webdna >code. If we need to see your html we will ask for it, but 99 times >out of 100 we will not need to see it, and posting it (or >javascript) just discourages us from trying to help. ------------------------------------------------------------- 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:
Sounds like we need a FAQ for posting to the Talk List. I think Ken's detailed message explains what to expect here and seems to mirror what I do when debugging my own code before posting here. Here's some free advice for those new here: Strip down to bare WebDNA. Are you seeing the right text where it needs to be? Use some sort of debugging code to see what variables have been used and what the values are. This let's you spot when things don't happen as you've planned. Strip down to bare HTML using hardcoded values, i.e. no WebDNA variables. Then roll in CSS a bit at a time. If everything "appears" right, then roll in Javascript to see if it behaves right. This should be standard practice for coders when trying to track something down, although I welcome other debugging tips (such as re-using working code libraries). You should be able to isolate the problem to either a WebDNA issue or an HTML/CSS/JS issue. If it's a WebDNA issue, check the archives to see if it's been solved before. As you might imagine, it's not productive to post questions that have been answered before, particularly recent ones. If the archives don't help, feel free to post here the WebDNA code that is not working. Without the code, it's impossible to spot the problem so you'll only get help, if any, in the form of educated guesses. When you have an HTML/CSS/JS (or any non-WebDNA) issue, put OT: (Off Topic) at the beginning of the subject line so others know that it's not a WebDNA issue. That way people can skip it quickly if they don't want to deal with OT issues. I think captures what most of us have been doing and expect. Bill -----Original Message----- From: Terry Wilson Sent: Thu, 11 Mar 2004 10:22:58 -0500 To: (WebDNA Talk) Subject: Re: FW: weird problem If I might chime in here... When I have a problem, I find that in the process extracting the essential code into an email, I usually discover the answer on my own. So there's more than one benefit for keeping postings concise. Terry >My suggestion for posting your original webdna code is even simpler: > >1- Remove all the HTML and javascript, then post ONLY the webdna >code. If we need to see your html we will ask for it, but 99 times >out of 100 we will not need to see it, and posting it (or >javascript) just discourages us from trying to help. ------------------------------------------------------------- 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/
devaulw@onebox.com
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:
emailer (1997)
WebCatalog stalls (1998)
RAM to disk - well correction. (2002)
Practice runs ? (1997)
Separate SSL Server (1997)
Some Questions (1997)
ExpireDate Zero or Greater than Today (2006)
suffix mapping for NT? (1997)
mail test (1997)
Reselecting popup menu (2002)
RE:It just Does't add up!!! (1997)
Major problem (1999)
Smith Micro - no competition (2000)
Shopping problems with 2.1b3 acgi (1997)
really wierd browser truncating (1997)
Customer - again (1998)
SiteEdit Pro, DataBase Helper and Europe (2000)
FEW QUESTIONS (1997)
Looking up two prices in database? (1997)
RE: protect tag not working (1998)