Re: [include file=filename.inc&strip=t]
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43598
interpreted = N
texte = Coldfusion MX has this feature - set as a global preference and it is great.You select 'clean white space' and all your templates come back compressed and nicely empty of white space.And I guess by doing it as the page is returned to the server you don't have to worry about the [sendmail] tag etc as these are not returnedCool. Count my vote !> 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:
Coldfusion MX has this feature - set as a global preference and it is great.You select 'clean white space' and all your templates come back compressed and nicely empty of white space.And I guess by doing it as the page is returned to the server you don't have to worry about the [sendmail] tag etc as these are not returnedCool. Count my vote !> 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/
Alain Russell
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:
Postprocessing CCs (2000)
OT: javascript help (2003)
syntax question, not in online refernce (1997)
[listfiles] anomaly (2003)
[WebDNA] Formatting numbers - truncation instead of rounding (2011)
RE: Problems with shopping cart (1997)
2 easy questions re: [showif] and [sendmail] (1997)
How can I Add several Items into the cart at once? (1997)
Clearing orders and database help! (1997)
Moment of Thanks (1997)
Secure server question (1997)
Field name-subcategory (1997)
TABLE (2003)
(2000)
Date search - yes or no (1997)
Quit revisited (1997)
Webcatalog error, Plug-in for Webstar (1996)
Add sizes from check boxes (2002)
[WebDNA] Feature Request (2013)
[WebDNA] How to access WebDNA admin pages? (2010)