This is an early development test page.
The test covers the following areas: Core components (TaskService, MessageService, base utilities), and UI widgets.
Neither this page, nor the code referenced by this page, are meant to be used in any environment other than development testing.
It is made available only for public commentary.
<!-- BEGIN -->
<!-- END -->
The following elements are used actively on in this test.
Design:
Low impact on global namespace.
Logical and deployment-ready package structure.
Separation of core and supplemental components.
Core Components:
Internal message service with support for "delayed reaction."
Logger (now available through message service).
DOM Event Utility.
Component management and registry.
Psuedo Object Inheritence (functional, but pretty darn freaky)
TaskService:
Implementation note: UI components are partially derived from config-based class definitions and xml-based style data. Developers must execute a task to load the configuration document, in which a handler is stipulated to continue any primary configuration- or script-based tasks. It's actually not that scary, but worthy of a note.
Bootstraps correctly processes primary and dependent tasks asynchronously, and can process synchronous bootstrap chains using by defining handlers to execute additional bootstraps.
Default config-based bootstrap executes via developer's by-page bootstrap resulting in the application_initialized event being fired after all supporting tasks are complet.
Driver:
Application Driver delegates window events via MessageService to other components.
Stores configuration data specified in the main config. All other config is by-component (eg: the component is responsible for loading and parsing it), or should be loaded with the org.cote.js.util.config utility.
UI Components:
Container - nothing special
ResultSet - add to base features, correctly implements the following: buffering, max-limit, max-rollover, auto-select, and auto-scroll.
Menu (a bit funky with sticky highlights in some cases)