Sure, but one still has to be able to get its hands on the object to do it, and I don't see what a promise has to do with this, regardless of how/when the object created, a delegate would be interested in configuring the object once created, and that's for the rangeController to do to its delegate

On Jun 17, 2013, at 10:43 PM, Mike Czepiel <notifications@github.com> wrote:

> In core/range-controller.js:
> 
> > @@ -443,6 +443,32 @@ var RangeController = exports.RangeController = Montage.specialize( {
> >      },
> >  
> >      /**
> > +     * Creates content and adds it to the controller and its backing
> > +     * collection.  Uses `add` and `contentConstructor`.
> > +     */
> > +    addContent: {
> > +        value: function () {
> > +            this.add(new this.contentConstructor());
> Oh I should note that due to our declaration using argument-less constructors we already have that convention in place so customization takes places after construction everywhere anyway.
> 
> —
> Reply to this email directly or view it on GitHub.
>