Re: [include file=filename.inc&strip=t]
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43605
interpreted = N
texte = Awesome! Then I can stop writing my latest treatise on the benefits of such a context! It's always a pleasure to see examples of vendors listening to their customers.Do these functions also have something like a return context so you can specify exactly what to return, as opposed to the current discussion which is centered around what NOT to return?i.e.:[function myFunction] code more code [return [myReturnVar]] [/function]...and what's the latest on the expected 5.0 release schedule?- brian At 2:27 PM 9/19/02, Scott Anderson wrote: >I see your point. I think it would be good to do both, create a global >method and a new context, for removing extraneous white space. > >You will appreciate the new [function name=MyFunction...] context I just >finished implementing for 5.0. Instances of the 'user defined' functions >have their own parameter and variable name space. It has come in very handy >for our 5.0 template development. > >> -----Original Message----- >> From: WebCatalog Talk >> [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf >> Of John Peacock >> Sent: Thursday, September 19, 2002 1:58 PM >> To: WebCatalog Talk >> Subject: Re: [include file=filename.inc&strip=t] >> >> >> 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:
Awesome! Then I can stop writing my latest treatise on the benefits of such a context! It's always a pleasure to see examples of vendors listening to their customers.Do these functions also have something like a return context so you can specify exactly what to return, as opposed to the current discussion which is centered around what NOT to return?i.e.:[function myFunction] code more code [return [myReturnVar]] [/function]...and what's the latest on the expected 5.0 release schedule?- brian At 2:27 PM 9/19/02, Scott Anderson wrote: >I see your point. I think it would be good to do both, create a global >method and a new context, for removing extraneous white space. > >You will appreciate the new [function name=MyFunction...] context I just >finished implementing for 5.0. Instances of the 'user defined' functions >have their own parameter and variable name space. It has come in very handy >for our 5.0 template development. > >> -----Original Message----- >> From: WebCatalog Talk >> [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf >> Of John Peacock >> Sent: Thursday, September 19, 2002 1:58 PM >> To: WebCatalog Talk >> Subject: Re: [include file=filename.inc&strip=t] >> >> >> 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/
Brian Fries
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:
Summ=T Problem (1997)
Getting total number of items ordered (1997)
On a related topic (2006)
Merchant and WebCat 3.0 (1998)
WebCat2b15MacPlugin - showing [math] (1997)
[WebDNA] Store module/site (2012)
For those of you not on the WebCatalog Beta... (1997)
NT considerations (1997)
WebCat2b15MacPlugin - [protect] (1997)
Merging databases (1997)
Re:Password Authentication - request example (1998)
Word search (1997)
make updates in a temporary database (2004)
Resume Catalog ? (1997)
Register First (2000)
WebCat2b12 CGI Mac - [shownext] problem (1997)
syntax question, not in online refernce (1997)
[include] affect on filepaths for links? (1997)
Cyberstudio and WebDNA (1997)
PSC recommends what date format yr 2000??? (1997)