Re: [WebDNA] webDNA and JSON
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106647
interpreted = N
texte = Thanks guys, I've been using those very practices you mentioned, and it just occurred to me where the extra whitespace is coming from...Globals. I'm sharing server space with another DNA programmer and realized he is using some pre-parse scripts that are the source of the white-space. Without having to twist his arm to clean it all up, is it possible to enable/disable pre-parse scripts on a page-by-page or domain-by-domain basis? I think I already know the answer, but what the heck... On 5/13/11 8:41 AM, Govinda wrote: >>> I noticed that the webDNA tags themselves are creating >>> whitespace when returning back data. >> If this is a problem, why not just move your WebDNA tags to >> get rid of the white space? > > Hi Aaron, > I think Ken is right. I mean - I have done lots of webdna over the years, and some coding with webdna and javascript talking to each other.. not alot.. but just enough to comment.. > > ..and anyway i am guessing that what you will have to focus on is to take total control of every character you output with webdna. In PHP you have to (get to) specify just when/where you start and stop output.. but with webdna everything but the tags themselves is output - as it appears in your source doc. > > As a result of this situation, old-school webdna code used a ton of comments to trim whitespace, > ...like [!] > [/!] so. > > You can also use [function]s which only [return] what you say to return... > > You can also do your manipulation/processing as always, but store any developing output into concatenating [text] vars.. and then finally when you are ready to actually output, then just drop in the [text] var. This method allows to you do [grep], etc. to strip out unwanted chars, or even add in wanted chars. Like you can replace all actual carriage return/line feed chars with
, and replace all instances of "someCRLFflag" with a real CR/LF char, when/where needed, for one example. > > Play with it. Examine the evolving string of characters at various steps to see what you are actually doing to the output as you generate it.. step by step. > > > - Govinda > -------------- > Old WebDNA talklist archives: > http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Thanks guys, I've been using those very practices you mentioned, and it just occurred to me where the extra whitespace is coming from...Globals. I'm sharing server space with another DNA programmer and realized he is using some pre-parse scripts that are the source of the white-space. Without having to twist his arm to clean it all up, is it possible to enable/disable pre-parse scripts on a page-by-page or domain-by-domain basis? I think I already know the answer, but what the heck... On 5/13/11 8:41 AM, Govinda wrote: >>> I noticed that the webDNA tags themselves are creating >>> whitespace when returning back data. >> If this is a problem, why not just move your WebDNA tags to >> get rid of the white space? > > Hi Aaron, > I think Ken is right. I mean - I have done lots of webdna over the years, and some coding with webdna and javascript talking to each other.. not alot.. but just enough to comment.. > > ..and anyway i am guessing that what you will have to focus on is to take total control of every character you output with webdna. In PHP you have to (get to) specify just when/where you start and stop output.. but with webdna everything but the tags themselves is output - as it appears in your source doc. > > As a result of this situation, old-school webdna code used a ton of comments to trim whitespace, > ...like [!] > [/!] so. > > You can also use [function]s which only [return] what you say to return... > > You can also do your manipulation/processing as always, but store any developing output into concatenating [text] vars.. and then finally when you are ready to actually output, then just drop in the [text] var. This method allows to you do [grep], etc. to strip out unwanted chars, or even add in wanted chars. Like you can replace all actual carriage return/line feed chars with, and replace all instances of "someCRLFflag" with a real CR/LF char, when/where needed, for one example. > > Play with it. Examine the evolving string of characters at various steps to see what you are actually doing to the output as you generate it.. step by step. > > > - Govinda > -------------- > Old WebDNA talklist archives: > http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Aaron Michael Kaczmarek
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:
WebCat2b13MacPlugIn - More limits on [include] (1997)
TCPconnect to DNS (2000)
taxTotal, grandTotal (1997)
Question about links (1999)
Cart Creation (2003)
Date Math bug (1998)
WebCat2b13MacPlugin - nested [xxx] contexts (1997)
shipcost (1997)
code to phantom spacing (2001)
Not reading code (1997)
webcat- multiple selection in input field (1997)
shownext problems (1998)
[LOOKUP] (1997)
PSC recommends what date format yr 2000??? (1997)
Progress !! WAS: Trouble with formula.db (1997)
[OT] HTML TAB CODE (2002)
[Capitalize] (1998)
[WebDNA] Test (2019)
WebCat and AppleShare 6.0 (1998)
please anybody help (2005)