Re: [include file=filename.inc&strip=t]
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43600
interpreted = N
texte = Maybe this is too simplistic but I could get by pretty well with a new context that essentially did what the special convertchars db did that was posted earlier. It could be placed anywhere in the code to tighten up the output html and would only be used where we wanted or needed it. It would just trim all leading and trailing white space and EOL characters. That way it would leave anything we actually wanted to keep in there. So instead of: I could do: [collapse] [/collapse]I could really use something like this right now on my site!Larry Goodhew> > One idea that comes to mind is the introduction of a post-parse action. > This action could take the form of a WebDNA code block, which could be > persisted in the admin prefs. This code block would then be applied to all > parsed results, just before being returned to the webserver. It would then be > simple matter to define a WebDNA post-parse block of code to strip out EOL's (or > whatever), and this would be applied to every template processed. Any feedback? > > > -----Original Message----- > > From: WebCatalog Talk > > [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf > > Of John Peacock > > Sent: Thursday, September 19, 2002 10:21 AM > > To: WebCatalog Talk > > Subject: RFE: [include file=filename.inc&strip=t] > > > > > > Working with the two include files I just posted, I was again > > reminded how > > stupid WebDNA is with regard to extraneous whitespace like > > EOL characters. > > Sure, when displayed to a HTML browser, multiple EOL's or > > spaces will be > > supressed. However, just looking at the maze of [!][/!] > > contexts I had to put > > in that file emphasizes that this is poorly designed behavior. > > > > I have long argued that only a handful of contexts require > > maintaining the EOL > > characters ([sendmail] and [writefile] being the two most > > obvious). Every > > single other context could easily strip EOL's without > > interfering in the coding > > in the slightest. Grant shot me down, I think because it > > would mean branching > > the parser to know when to strip and when not to strip, based > > on context. > > > > Hence, my suggestion that the [include] context at the very > > least include a > > strip=t option (defaults to F) so that it would be much > > easier to write user > > defined functions. I want to return only the text I want to > > return, without > > extraneous EOL characters, and without having to load up my > > source code with an > > unreadable mass of [!][/!] contexts. > > > > In fact, if the parser were altered to support this for all > > contexts, defaulting > > to F, I could reduce the size of my pages by a significant > > percentage, just by > > supressing those stupid EOL's. > > > > When writing CGI code in Perl, I usually turn off the extra > > EOL's after I have > > debugged the code. It makes view source less useful, but it > > has a definite > > impact on how fast the page loads to have all of the HTML on > > basically a couple > > of lines. > > > > Thanks > > > > John > > > > -- > > John Peacock > > Director of Information Research and Technology > > Rowman & Littlefield Publishing Group > > 4720 Boston Way > > Lanham, MD 20706 > > 301-459-3366 x.5010 > > fax 301-429-5747 > > > > > > ------------------------------------------------------------- > > 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://search.smithmicro.com/ > > > ------------------------------------------------------------- > 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://search.smithmicro.com/ > ------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Maybe this is too simplistic but I could get by pretty well with a new context that essentially did what the special convertchars db did that was posted earlier. It could be placed anywhere in the code to tighten up the output html and would only be used where we wanted or needed it. It would just trim all leading and trailing white space and EOL characters. That way it would leave anything we actually wanted to keep in there. So instead of: I could do: [collapse] [/collapse]I could really use something like this right now on my site!Larry Goodhew> > One idea that comes to mind is the introduction of a post-parse action. > This action could take the form of a WebDNA code block, which could be > persisted in the admin prefs. This code block would then be applied to all > parsed results, just before being returned to the webserver. It would then be > simple matter to define a WebDNA post-parse block of code to strip out EOL's (or > whatever), and this would be applied to every template processed. Any feedback? > > > -----Original Message----- > > From: WebCatalog Talk > > [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf > > Of John Peacock > > Sent: Thursday, September 19, 2002 10:21 AM > > To: WebCatalog Talk > > Subject: RFE: [include file=filename.inc&strip=t] > > > > > > Working with the two include files I just posted, I was again > > reminded how > > stupid WebDNA is with regard to extraneous whitespace like > > EOL characters. > > Sure, when displayed to a HTML browser, multiple EOL's or > > spaces will be > > supressed. However, just looking at the maze of [!][/!] > > contexts I had to put > > in that file emphasizes that this is poorly designed behavior. > > > > I have long argued that only a handful of contexts require > > maintaining the EOL > > characters ([sendmail] and [writefile] being the two most > > obvious). Every > > single other context could easily strip EOL's without > > interfering in the coding > > in the slightest. Grant shot me down, I think because it > > would mean branching > > the parser to know when to strip and when not to strip, based > > on context. > > > > Hence, my suggestion that the [include] context at the very > > least include a > > strip=t option (defaults to F) so that it would be much > > easier to write user > > defined functions. I want to return only the text I want to > > return, without > > extraneous EOL characters, and without having to load up my > > source code with an > > unreadable mass of [!][/!] contexts. > > > > In fact, if the parser were altered to support this for all > > contexts, defaulting > > to F, I could reduce the size of my pages by a significant > > percentage, just by > > supressing those stupid EOL's. > > > > When writing CGI code in Perl, I usually turn off the extra > > EOL's after I have > > debugged the code. It makes view source less useful, but it > > has a definite > > impact on how fast the page loads to have all of the HTML on > > basically a couple > > of lines. > > > > Thanks > > > > John > > > > -- > > John Peacock > > Director of Information Research and Technology > > Rowman & Littlefield Publishing Group > > 4720 Boston Way > > Lanham, MD 20706 > > 301-459-3366 x.5010 > > fax 301-429-5747 > > > > > > ------------------------------------------------------------- > > 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://search.smithmicro.com/ > > > ------------------------------------------------------------- > 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://search.smithmicro.com/ > ------------------------------------------------------------- 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://search.smithmicro.com/
Larry Goodhew
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:
WebCat for mass emailings (1997)
RAM variables (1997)
Three new problems, maybe a fourth (1997)
RE: Credit Card Checksum (1997)
[OrderFile] being testy (2000)
Multiple fields on 1 input (1997)
how to use WebCat w. SSL & CyberCash (1998)
cart converting to scientific notation format (2001)
Command=Showcart? (2000)
WebDNA Commerce Single for MAC 6.0 (2008)
Searching multiple fields from one form field (1997)
Cold Fusion Buster (1997)
Format of Required fields error message (1997)
WebCat2 beta 11 - new prefs ... (1997)
Calculating Shipping (1997)
bugs w/! &/or bad scripting??? (1997)
Logging purchases (1997)
beta 6 on OSX wierdness (2000)
Problems passing [SKU] with $Replace in 2.0 (1997)
formula.db, adding option prices (1997)