All controls make heavy use of javascript functions to do any additional functionality (example NavigationEvent1.fire() ). Might increase the learning curve with tool. Just want to know why you went this route vs. having most of the common functions as configuration options.
SPARK Support
All of these methods and extra capabilities exist as development efficiency enablers which are typically much simpler to use than the “vanilla” Coach NG equivalent. In fact one can use SPARK as they would basic Coah NG without exploiting any efficiency enabler. It would work perfectly fine but would clearly forgo a key benefit of the toolkit. It should also be noted that even the SPARK development team relies on the 3 foundational principles of SPARK: Know how to use controls with events, methods, and properties. Once those 3 basic aspects are generically understood, one only needs to consult the online methods/events/properties documentation for each control to understand how to fully exploit it. This is consistent with what any other UI library would require the developer to do in order to fully utilize its benefits.
