@jdfreder, @SylvainCorlay - review?

I confirm that it solves my issue. This looks good.

@jdfreder, @minrk - I think this bug fix could be a candidate for 3.0. The problem Sylvain was seeing was that if you created a widget in the same cell as displaying it, where the widget is dynamically loaded using requirejs, it often would not show up since the display message would beat the update message.

Can you show an example that fails?

You only need to use a custom model that is asynchronously loaded. For example, if you do

In /nbextensions/Foo/Bar.js

define(["widgets/js/widget"], function(Widget) {
    "use strict";
    var Bar= Widget.WidgetModel;
    return {
        Bar: Bar,
    };
});

Then we simple declare a Slider that uses this model:

from IPython.html.widgets import IntSlider
from IPython.utils.traitlets import Unicode
from IPython.display import display

class BarSlider(IntSlider):
    _model_name = Unicode('Bar', sync=True)
    _model_module = Unicode('nbextensions/Foo/Bar', sync=True)

slider = BarSlider()
display(slider)

In manager.js, the call to load_class Line 181 requires the view name and module path, which are part of the model state.

I haven't seen this problem myself with my ipython-flightwidgets repo. Is it frequent? @SylvainCorlay 's example code should work as-is.

It is because you don't overload the model in your flight widget. This only
happens with overloaded models.
On Feb 19, 2015 12:12 PM, "Jonathan Frederic" notifications@github.com
wrote:

I haven't seen this problem myself with my ipython-flightwidgets repo. Is
it frequent? @SylvainCorlay https://github.com/SylvainCorlay 's example
code should work as-is.

—
Reply to this email directly or view it on GitHub
#7801 (comment).

Oh I see, thanks.