It seems also IE8 beta 2 has JSON natively.

Scripting Engine

Many enhancements have been done to the scripting engine. One feature that will bring a lot of value to the AJAX developers is the introduction of native JavaScript Object Notation (JSON). With JSON becoming the de-facto data interchange language for contemporary web applications; we have included native JSON support within the JScript engine. With this, developers can use a native JSON object to serialize and de-serialize JScript objects. This feature makes Internet Explorer 8 the first browser to support JSON natively!

We'll have to test how efficient they are compared to our, but I guess nothing would really change for whoever's going to use JSON from MooTools (except for fastness, if it really is as fast as they say). However, it's something we'll discuss on those browser's release because, as Jan already said ealrier, we don't support betas/rcs.

Good to know, though, and thanks for pointing this out eduacostam. Really appreciated.

- Djamil


Il giorno 11/ott/08, alle ore 19:46, Jan Kassens ha scritto:


We will look into this. I didnt dig into the new JSON object yet, but i'm trying to make the mootools implementation compatible with the new introduced native and probably making use of the (said to be faster) native implementation. We normally dont support betas or even earlier versions, but i'm sure the JSON native object will make it into the next release.

Thanks for the report and digging into this.

Jan, mootools core developer

On Oct 11, 2008, at 18:42, eduacostam wrote:


digging around I've found this:
http://blog.mozilla.com/meeting-notes/archives/66

ths important stuff is:
JS 1.9.1
- New global JSON object, will follow up to match ES 3.1 spec.

more info: https://wiki.mozilla.org/QA/Firefox3.1/ Native_JSON_Testplan

Now i've tested mootools without JSON and it works well, so I think
the problem is that firefox added a JSON object and when mootools
declares it's own it brakes everything.
This is a serious problem if Firefox 3.1 is going to have this.

Devs what do you think?

On Oct 11, 12:08 am, "Iván N Paz" <[EMAIL PROTECTED]> wrote:
Im afraid:

redeclaration of const JSON

Might be the issue here... if thats the problem... has JSON become a
reserved word in nightly firefox???

Personally I wouldnt bother too much with that, since nightly builds
are just like that... prone to errors here and there...

Maybe on tomorrow's nightbuild it will be gone... :-P

--
my blog: http://blog.kassens.net


Reply via email to