Schema v0.934 and ONMjs v0.0.17 ...

... Removal of encapsule-lib-console from ONMjs-lib-core has been today's mission. ONMjs now leverages Encapsule.code.lib.base.BackChannel API to route log and error messages from observers. Note that ONMjs core does not log informational messages and throws errors. The observer classes however do produce some debug telemetry and may encounter an error while operating outside of the main app's call scope (e.g. user scope - in response to a button click on a button rendered by an observer).

Schema code (and encapsule-lib*) had a huge dependency on the now deprecated Console infrastructure. This commit re-aligns Schema with the latest ONMjs and leverages a new file, schema-backchannel.js, included immediately after ONMjs and before any other Encapsule libraries. schema-backchannel.js creates a backchannel object for the schema app that is persisted in the global namespace at Encapsule.runtime.backchannel. For now, encapsule-lib* code and Schema-app-specific code has been modified to redirect all logging and error reporting to this new backchannel. Currently schema backchannel redirects all traffic to console.log and console.error (+ alert on error). Note that formerly, Console.message accepted HTML. There's a lot of ugly console spew emitted by Schema on boot currently. I'll clean this up later when I re-write all of those early libraries - they're not up to current standard and could potentially be turned into ONMjs-derived plug-ins for some as-yet-evolving app framework.