Re: [include file=filename.inc&strip=t]
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43599
interpreted = N
texte = Scott Anderson wrote: > 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?No, that would also be nice but would not help me here. My issue is that the [include] context contains all of the EOL's from inside the context in addition to any text that I explicitely show. I want to have [include file=^somefile.inc¶m1]appears exactly like a new user-defined function [somefile param1]with no text (including EOL's) except that which I chose to display. If the post-parse action could apply to each enclosing context, that would be fine. If you look at what I am trying to accomplish, stripping EOL before sending would not be sufficient, since the [include] context is inside other contexts and the EOL's could wind up causing a syntax error...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/
Associated Messages, from the most recent to the oldest:
Scott Anderson wrote: > 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?No, that would also be nice but would not help me here. My issue is that the [include] context contains all of the EOL's from inside the context in addition to any text that I explicitely show. I want to have [include file=^somefile.inc¶m1]appears exactly like a new user-defined function [somefile param1]with no text (including EOL's) except that which I chose to display. If the post-parse action could apply to each enclosing context, that would be fine. If you look at what I am trying to accomplish, stripping EOL before sending would not be sufficient, since the [include] context is inside other contexts and the EOL's could wind up causing a syntax error...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/
John Peacock
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:
Beta Documentation (1997)
Additional Subtotals (1999)
[ot] Layer Help! (2002)
Cookies, checking if's enabled... (2004)
request for string functions (1998)
normal users.db calls ... (1998)
[WebDNA] Enhancements to "list" contexts ... (2015)
New Plug-in and Type 11 errors (1997)
WebCat2b15MacPlugin - showing [math] (1997)
Was code to phantom spacing -- now BBEdit [!][/!] (2001)
totals (1997)
Error Type 3 (1999)
RE: Languages (1997)
New public beta available (1997)
HELP WITH DATES (1997)
Quick ShowIf question (1997)
[WebDNA] plupload ? (2012)
Multiple Pulldowns (1997)
AGAIN: Who's Security? (2000)
Size limit for tmpl editor ? (1997)