If you use another none Mootools aware script like Socket.IO-client for example, it requires parse and stringify. Socket.IO-client inculdes json.js in it's package. But in my case, I use Mootools so including json.js is redundant. If Mootools had these aliases (cf. Arian's code snippet) directly in it's core, you could remove json.js and it would work out of the box (hence my "simplify integration" comment). Adding json.js separably or manually adding this compatibility layer goes against Mootools philosophy (light is right, elegant cross-browser, etc.)
Cheers, Peter On Thu, Feb 17, 2011 at 00:51, Christoph Pojer <[email protected]> wrote: > I don't want to question you but why is it important to you to "call > standard method names" if you are using a library anyway? I don't see the > point in doing this. JSON.encode and JSON.decode is perfectly fine. > Otherwise, do what arian proposed or load JSON2.js in your scripts :)
