The beautiful thing about using a data, event driven architecture is that you generally don't ever actually need to interact with the components that consume that data, only the data itself. You have a couple of options here, but the goal is to make the scope can.Map within an accessible scope. This can be done by passing can.Map instances as attributes, or during scope setup.
Example:
- var foo = can.Map.extend({
- a: 5,
- b: 10,
- sum: can.compute(function() {
- return this.attr('a') + this.attr('b');
- })
- });
- var bar = new foo();
- can.Component.extend({
- tag: 'test',
- scope: function(attr, parentScope, element) {
- attr.bar = bar;
- return attr;
- })
- });
- bar.attr('a', 20);
Anyway, you get the idea.