Re: [WebDNA] webDNA and JSON

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106649
interpreted = N
texte = This is a multi-part message in MIME format. --------------020608000600080507050301 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit its not a multi-user environment exactly - its my own vps, but I have a couple sites that me and a professional partner (and very good friend, no security threat) have co-created with both of our custom libraries. Honestly, I've never used the sandboxes or the site builder features that come out-of-the-box. I've preferred to use webDNA strictly as an interpreter for custom builds. It seems that I would behoove myself to tap into this feature... On 5/13/11 12:10 PM, Terry Wilson wrote: > 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 wrote: > 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 > > --------------------------------------------------------- > 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 > --------------------------------------------------------- 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 --------------020608000600080507050301 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable its not a multi-user environment exactly - its my own vps, but I have a couple sites that me and a professional partner (and very good friend, no security threat) have co-created with both of our custom libraries.=C2=A0

Honestly, I've never used the sandboxes or the site builder features that come out-of-the-box.=C2=A0 I've preferred to use webDNA strictly= as an interpreter for custom builds.=C2=A0 It seems that I would behoove myself to tap into this feature...

On 5/13/11 12:10 PM, Terry Wilson wrote:
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 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.=C2=A0=C2=A0I 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.=C2=A0=C2=A0In 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.=C2=A0=C2=A0This method allows to you do [grep], etc. t= o strip out unwanted
>chars, or even add in wanted chars.=C2=A0=C2=A0Like 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.=C2=A0=C2=A0Examine the evolving string of ch= aracters 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/TalkLis= tArchive/index.tpl?db=3Dwebdna-talk
>
> ---------------------------------------------------------<= br> > This message is sent to you because you are subscribed to
> the mailing list<talk@webdna.us>.
> To unsubscribe, E-mail to:<talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@web= dna.us
> Bug Reporting: support@webdna.us

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.u= s
Bug Reporting: support@webdna.us
--------------------------------------------------------- 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.u= s Bug Reporting: support@webdna.us

--------------020608000600080507050301-- 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)
This is a multi-part message in MIME format. --------------020608000600080507050301 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit its not a multi-user environment exactly - its my own vps, but I have a couple sites that me and a professional partner (and very good friend, no security threat) have co-created with both of our custom libraries. Honestly, I've never used the sandboxes or the site builder features that come out-of-the-box. I've preferred to use webDNA strictly as an interpreter for custom builds. It seems that I would behoove myself to tap into this feature... On 5/13/11 12:10 PM, Terry Wilson wrote: > 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 wrote: > 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 > > --------------------------------------------------------- > 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 > --------------------------------------------------------- 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 --------------020608000600080507050301 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable its not a multi-user environment exactly - its my own vps, but I have a couple sites that me and a professional partner (and very good friend, no security threat) have co-created with both of our custom libraries.=C2=A0

Honestly, I've never used the sandboxes or the site builder features that come out-of-the-box.=C2=A0 I've preferred to use webDNA strictly= as an interpreter for custom builds.=C2=A0 It seems that I would behoove myself to tap into this feature...

On 5/13/11 12:10 PM, Terry Wilson wrote:
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 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.=C2=A0=C2=A0I 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.=C2=A0=C2=A0In 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.=C2=A0=C2=A0This method allows to you do [grep], etc. t= o strip out unwanted
>chars, or even add in wanted chars.=C2=A0=C2=A0Like 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.=C2=A0=C2=A0Examine the evolving string of ch= aracters 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/TalkLis= tArchive/index.tpl?db=3Dwebdna-talk
>
> ---------------------------------------------------------<= br> > This message is sent to you because you are subscribed to
> the mailing list<talk@webdna.us>.
> To unsubscribe, E-mail to:<talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@web= dna.us
> Bug Reporting: support@webdna.us

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.u= s
Bug Reporting: support@webdna.us
--------------------------------------------------------- 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.u= s Bug Reporting: support@webdna.us

--------------020608000600080507050301-- 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:

Formatting a .txt file (1998) [browsername] not working? (1997) Duplicate Cart Numbers (1999) Wanted: More Math Functions (or, Can You Solve This?) (1997) WCS Newbie question (1997) Image browser / insert image (2006) File Upload Problems (HELP!) (2000) Not Authorised Adding Items (1998) 2.0 Info (1997) RE: Can't get appendfile to work (1997) using listfiles to build a database? more (2000) Remove a Field from a DB (2007) [OT] Authorize.net (2003) Pre-flight public flag (1997) Another question (1997) Paths (1998) Search for starts with and ends with? (2003) fieldType=num (1997) Harvesting invalid email addresses from bounced emails??? (2000) form data submission gets truncated (1997)