Right. But, I would have to modify that notify function to be able to add
custom enyo components.


On Fri, Apr 25, 2014 at 9:10 AM, Travis Webb <notifications@github.com>wrote:

> In enyo-client/application/source/views/list.js:
>
> >                placeholder: "_noAssignedTo".loc()}
> >            ]}
> >          ]}
> >        ]}
> >      ],
> > +    selectedModels: function () {
> > +      var that = this,
> > +        collection = this.getValue(),
> > +        models = [],
> > +        selected;
> > +      if (collection.length) {
> > +        selected = _.keys(this.getSelection().selected);
> > +        // Using the selected index keys, go grab the models and return them in an array
> > +        models.push(_.map(selected, function (index) {
> > +          return that.getModel(index);
> > +        }));
> > +      }
> > +      return models[0];
> > +    },
> > +    reassignUser: function () {
>
> Yes. The business work should be done in the model layer, and a model
> should notify the view when some view action is to occur. XM.Model has a
> notify function for this purpose.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/xtuple/xtuple/pull/1426/files#r12000726>
> .
>



-- 
Julian Carlin

(US) 612-234-4124