| About | Download | Examples | Tutorials | Reference | Support | Community |
| Ample SDK 0.9.3 ReleasedDev Update (May)Dev Update (October)Upcoming Events (Sep, Oct)Search in referenceIntroduction to Ample SDKFebruary in Ample SDKNovember in Ample SDKSet to go Open-SourceSandbox to try code onlineNew Tutorials sectionSVG in Internet ExplorerDrag&Drop and ResizeSMIL 3.0 in Ample SDKSwitching to HTML5 doctypeUsing Resize ManagerJSON object supportUpcoming changes to CSSAmple SDK plugin for AptanaDefault namespaces in DOMAmple SDK in Adobe AirObjects signatures changedSVG 1.2 Tiny in Ample SDK |
|
Objects signatures changedThe 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]}". |
