Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: appendChild & cloneNode

From: RobG <robgbne@-----.--->
To: NULL
Date: 6/2/2009 6:01:00 PM
On Jun 3, 6:36=A0am, Jorge <jo...@jorgechamorro.com> wrote:
> On Jun 2, 10:11=A0pm, David Mark <dmark.cins...@gmail.com> wrote:
>
>
>
> > (...) Use innerHTML or JSON.
>
> JSON ? What's JSON ?
>
> Oh well, I'll see it in the good old great cljs FAQ :-)
>
> http://www.google.com/search?&q=3Dsite:jibbering.com/faq/+json
>
> Ooops:
>
> "Your search - site:jibbering.com/faq/ json - did not match any
> documents."

Not surprising, there aren't any frequently asked questions about JSON
here.


> Pathetic, pitiful...

Not at all, quite reasonable in fact.  An FAQ is for *frequently*
asked questions, I don't see frequent questions about JSON here.  If
the purpose of the clj FAQ was general javascript topics, it would be
perhaps 50 times larger that it is, at least.

In any case, if you think an item on JSON is required, write one and
post it here for review and possible inclusion in the FAQ.


--
Rob


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent