Develop extensible application architecture

[Google Code Exporter]

Building an application from several "composite widgets" seems like it
would be a common pattern. We often take a DataTable, and a Dialog, and an
TabView, and weave them together into a composite widget.

Most of the examples found in books and website tend to use global members.
Globals work well enough for trivial examples, but for applications that
use many widgets, and multiple composite widgets, using globals seems like
it would be confusing and error-prone (e.g. "evil").

Original issue reported on code.google.com by ted.husted on 22 May 2007 at 1:47

[Google Code Exporter]

NOW DONE

x Defer loading until tab clicked (load blank.html first)
x Define extended properties for each iframe with sTitle, sPath, oContent. 
x Define my.js singelton with shared properties, methods, and constructors
x Try in local application and Yazaar application
x Draft design walkthrough 

SIM TODO 

* JSDoc
* Log listener to report custom application events

Menu.thml 
 * FIXME: Need an overall iframe stylesheet
 * FIXME:  my.aFrames = window.frames; // Use it or lose it!   


Menu.js
 * FIXME: Why doesn't extending work? (or is not extending better?)
 * FIXME: Why doesn't an array of frameTiles work as a set property?
 * TODO: Extend ViewManager from OverlayManager and add the iFrame hide/show code
 * TODO: Post tab/iframe settings (nIndex, sTitle, sLocation, isLoaded) to
constructor using an arrary "ViewNode" config 

object so that tokens like "Home" are in the same file.

Notes.html
 * Review Notes widget to see if can be integrated with the Contacts widget.

Original comment by ted.husted on 22 May 2007 at 8:59