Hey guys,
I've been toying with the idea of making a base component that includes an app wide can.Map.extend as well as a programmatic interface. The idea here is that the interface would be a singleton can.Map that would be exported, and include publicly accessible methods/states.
The goals here are to:
- Make singleton interfaces that can be synchronously exported, extended, included etc independent of the construction of can.Components.
- Have a global can.Map that all components can bind to, and that is included as the base viewScope. This might have a reference to all interfaces, that's undecided.
- Manage component scope primary through dependency injection, rather than through a crazy amount of attributes
- Avoid relying on can.Component.prototype.scope to do excessive cross binding
Basically, I'm hoping that this will create design patterns that are much more decoupled, and clearer.
It looks like extending can.Component.constructor.Control is not so straightforward unfortunately. The obvious approach was this:
- can.Component.extend({
- setup: function() {
- can.Component.setup.apply(this, arguments);
- this.Control = this.Control.extend({
- _lookup: function( options ) {
- return [options.scope, options, this.constructor.interface, this.constructor.app, window];
- }
- })
- }, {
- ...
- });
Anyway, this isn't even called, and I'm not really too sure to go from here. Any ideas?