Re: [WebDNA] webDNA and JSON

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106648
interpreted = N
texte =
Surely you aren't sharing a globals folder with another user
With sandboxes, you get your= own globals





On Fri, 13 May 2011 12:02:48 -0400 Aaron Michael Kaczmarek <aaronmichaelmusic@gmail.com> wrote:
Thanks g= uys,

I've been using those very practices you mentioned, and it = just
occurred to me where the extra whitespace is coming from...Globals. <= br> 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 dom= ain-by-domain
basis?

I think I already know the answer, but = what the heck...


On 5/13/11 8:41 AM, Govinda wrote:
>>&= gt; I noticed that the webDNA tags themselves are creating
>>>= ; whitespace when returning back data.
>> If this is a problem, wh= y 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 cod= ing 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 appea= rs in your source doc.
>
> As a result of this situation, old-sc= hool webdna code used a ton of
>comments to trim whitespace,
&g= t; ...like [!]
> [/!] so.
>
> You can also use [function]= s which only [return] what you say to
>return...
>
> Y= ou 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 [tex= t]
>var.  This method allows to you do [grep], etc. to s= trip out unwanted
>chars, or even add in wanted chars.  Like = you can replace all actual
>carriage return/line feed chars with<nothing>, and replace all
>instances of "someCRLFflag" = with a real CR/LF char, when/where needed,
>for one example.
>
> Play with it.  Examine the evolving st= ring 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 talklis= t archives:
> http://dev.webdna.us/TalkListArchive/index.tpl?db=3Dweb= dna-talk
>
> ------------------------------------------------= ---------
> This message is sent to you because you are subscribed to
> the mai= ling list<talk@webdna.us>.
> To unsubscribe, E-mail to:<talk-leave@webdna.us>
> archives: http://mail.webdna.us/l= ist/talk@webdna.us
> Bug Reporting: support@webdna.us

---------------------------------------------------------
This messag= e is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@web= dna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bu= g Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] webDNA and JSON (Govinda 2011)
  2. Re: [WebDNA] webDNA and JSON (Aaron Michael Kaczmarek 2011)
  3. Re: [WebDNA] webDNA and JSON ("Terry Wilson" 2011)
  4. Re: [WebDNA] webDNA and JSON (Aaron Michael Kaczmarek 2011)
  5. Re: [WebDNA] webDNA and JSON (Govinda 2011)
  6. Re: [WebDNA] webDNA and JSON (Kenneth Grome 2011)
  7. [WebDNA] webDNA and JSON (Aaron Michael Kaczmarek 2011)
Surely you aren't sharing a globals folder with another user
With sandboxes, you get your= own globals





On Fri, 13 May 2011 12:02:48 -0400 Aaron Michael Kaczmarek <aaronmichaelmusic@gmail.com> wrote:
Thanks g= uys,

I've been using those very practices you mentioned, and it = just
occurred to me where the extra whitespace is coming from...Globals. <= br> 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 dom= ain-by-domain
basis?

I think I already know the answer, but = what the heck...


On 5/13/11 8:41 AM, Govinda wrote:
>>&= gt; I noticed that the webDNA tags themselves are creating
>>>= ; whitespace when returning back data.
>> If this is a problem, wh= y 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 cod= ing 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 appea= rs in your source doc.
>
> As a result of this situation, old-sc= hool webdna code used a ton of
>comments to trim whitespace,
&g= t; ...like [!]
> [/!] so.
>
> You can also use [function]= s which only [return] what you say to
>return...
>
> Y= ou 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 [tex= t]
>var.  This method allows to you do [grep], etc. to s= trip out unwanted
>chars, or even add in wanted chars.  Like = you can replace all actual
>carriage return/line feed chars with<nothing>, and replace all
>instances of "someCRLFflag" = with a real CR/LF char, when/where needed,
>for one example.
>
> Play with it.  Examine the evolving st= ring 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 talklis= t archives:
> http://dev.webdna.us/TalkListArchive/index.tpl?db=3Dweb= dna-talk
>
> ------------------------------------------------= ---------
> This message is sent to you because you are subscribed to
> the mai= ling list<talk@webdna.us>.
> To unsubscribe, E-mail to:<talk-leave@webdna.us>
> archives: http://mail.webdna.us/l= ist/talk@webdna.us
> Bug Reporting: support@webdna.us

---------------------------------------------------------
This messag= e is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@web= dna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bu= g Reporting: support@webdna.us
"Terry Wilson"

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:

WC2b15 File Corruption (1997) 2.01 upgrade problems (1997) Mac v. NT (1998) WebCatalog for guestbook ? (1997) No spaces allowed in text variable names ... ? (2002) What does this error mean? (2000) WebDNA-Talk Digests (1997) BR (1997) Crazy FROM Email Address with Orders, FIXED! (2004) [WebDNA] WebDNA on Facebook (2009) Hierarchy of form/text/math variables (renamed thread) (2000) same products but different (1998) Textarea Breaks (2000) Copyright ? (1997) Grep and removing text (2002) Email within tmpl ? (1997) Follow-Up to: Removing [showif] makes a big difference in speed (1997) 2nd WebCatalog2 Feature Request (1996) WYSIWYG Editor? (2006) New Command prefs ... (1997)