Objects signatures changed

jQuery API to get adopted as the first level API in the Ample SDK Introduction to Ample SDK by Béla Varga (in German)February in Ample SDK November in Ample SDK Set to go Open-Source Sandbox to try code online New Tutorials section to help you get started SVG in Internet Explorer: Approached the edge Drag And Drop / Resize UI managers enhancements SMIL 3.0 in Ample SDK Getting ready for tomorrow: Ample SDK to use HTML5 doctype Introduction to the Resize Manager in Ample SDK JSON object: almost native support for older browsers Upcoming change to ::pseudo-elements / :pseudo-classes syntax Caught in development - Ample SDK plugin for Aptana IDE Oh, these confusing default namespaces in DOM Upcoming Ample SDK weekly build to run in Adobe Air Objects signatures changed Experimental support for SVG 1.2 Tiny in Ample SDK

Objects signatures changed

The classes/objects and methods implementation in Ample SDK has always been hidden from the end developer in order to not confuse him. So executing "alert(AMLNode)" would return "[AMLNode]", or executing "alert(AMLNode.prototype.appendChild)" would return "function appendChild(){[ample code]}".

Recently we found out that object signature implementation was actually wrong. That is now corrected and the object signatures in Ample SDK changed to return "function AMLNode(){[ample code]}" when executing "alert(AMLNode)", which is applicable to any object defined in Ample Runtime.

Note, while introspecting browser native objects Gecko still returns "[DOMParser]", while other browsers - "function DOMParser(){[native code]}".