Aliro Documentation : JavaScript

HomePage :: Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register

Revision [166]

Most recent edit made on 2009-06-25 04:45:14 by ChadAuld

Additions:



Deletions:





Revision [165]

Edited on 2009-06-25 04:44:47 by ChadAuld

Additions:





Revision [91]

Edited on 2009-01-19 17:55:02 by ChadAuld

Additions:



Deletions:





Revision [90]

Edited on 2009-01-19 17:54:24 by ChadAuld

Additions:
Aliro's base JavaScript architecture is built around the Yahoo! User Interface (YUI) DOM (http://developer.yahoo.com/yui/dom/) & Event (http://developer.yahoo.com/yui/event/) components. These component give Aliro a solid set of cross-browser methods for dealing with things like identifying parts of the DOM, processing DOM objects, and detecting when key DOM events have fired (ex) DOM ready, load, click, etc. The Event utility even allows for creation and firing of custom events so it would be possible to build a JavaScript event system much like one already in place for Aliro PHP based plugins. The main goals behind formalizing the JavaScript architecture are to provide a consistent interface throughout the system, a reduced dependency on external libraries, enhanced cross-browser support via the graded browser support model (http://developer.yahoo.com/yui/articles/gbs/), and just more efficient code overall.
The Aliro team is working hard to assure that all the JavaScript within the system is properly namespaced and that it follows recommended object oriented conventions. The Aliro JavaScript architecture makes use of public, private, and protected variables and functions through the use of object literals and closures (http://www.crockford.com/javascript/private.html). We feel that the CMS should not simply be a collection of a 1000 JavaScript functions scattered throughout. Namespacing is a major concern since the system declares functions as need which in turn just places those into the browsers global namespace (http://www.dustindiaz.com/namespace-your-javascript/). This is where collisions happen. All the JavaScript in Aliro shall live under the "ALIRO" namespace and thus remain isolated from all other JavaScript loaded by extensions, 3rd party JavaScript libraries, etc. We advocate the YUI Library, but there is no reason a developer can't use his or her favorite like jQuery or Prototype since the t=rest of the system has been properly namespaced.


Deletions:





Revision [71]

Edited on 2009-01-12 05:18:43 by ChadAuld

Additions:



Deletions:





Revision [53]

Edited on 2009-01-12 01:11:45 by ChadAuld

Additions:
Development Tools:




Revision [48]

Edited on 2009-01-12 00:31:18 by ChadAuld

Additions:

JavaScript Performance:


Deletions:
The Aliro team has selected The Yahoo! User Interface Library (YUI) as our JavaScript library of choice. This selection was based on YUI's functionality, large user base, attention to detail, fantastic documentation, active support forums, and graded browser support model. Does this mean as a third party developer you must utilize YUI? It most certainly does not. Developers are free to utilize whatever tool best suits their needs. That being said we would most certainly recommend YUI and developers should find working with it in Aliro to be fairly straightforward. We will do our best to expose its powerful functionality to 3rd party developers within Aliro and document it's usage here.
JavaScript Performance:




Revision [47]

Edited on 2009-01-12 00:14:02 by ChadAuld

Additions:
JavaScript Object Notation (JSON):


Deletions:
JavaScript Object Notation (JSON):




Revision [46]

Edited on 2009-01-12 00:13:20 by ChadAuld

Additions:

JavaScript Performance:


Deletions:





Revision [44]

Edited on 2009-01-12 00:11:36 by ChadAuld

Additions:
JavaScript Object Notation (JSON):
The Yahoo! User Interface Library (YUI):
The Aliro team has selected The Yahoo! User Interface Library (YUI) as our JavaScript library of choice. This selection was based on YUI's functionality, large user base, attention to detail, fantastic documentation, active support forums, and graded browser support model. Does this mean as a third party developer you must utilize YUI? It most certainly does not. Developers are free to utilize whatever tool best suits their needs. That being said we would most certainly recommend YUI and developers should find working with it in Aliro to be fairly straightforward. We will do our best to expose its powerful functionality to 3rd party developers within Aliro and document it's usage here.


Deletions:
JavaScript Object Notiation (JSON):




Revision [42]

Edited on 2009-01-11 23:51:32 by ChadAuld

Additions:



Deletions:
Understanding JavaScript (Yahoo! Video Series)
Wikapedia
JSON in JavaScript
JSON and YUI




Revision [41]

Edited on 2009-01-11 23:50:53 by ChadAuld

Additions:
Learning Resources:
JavaScript Object Notiation (JSON):
Wikapedia
JSON in JavaScript
JSON and YUI




Revision [40]

Edited on 2009-01-11 23:08:49 by ChadAuld

Additions:
Understanding JavaScript (Yahoo! Video Series)


Deletions:
Videos




Revision [37]

The oldest known version of this page was edited on 2009-01-11 22:31:31 by MartinBrampton


Videos
Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by WikkaWiki
Page was generated in 0.2114 seconds