<span style='font-family:Verdana'><span style='font-size:12px'><div>Here's hoping&nbsp;mailman picks this up into the correct thread...</div><div> </div><div>Hi Brian/Matthaias,</div><div> </div><div>Thanks for the heads up.</div><div> </div><div>I'm looking forward to superior functionality being available</div><div>in IPython, though your roadmap is unclear on whether</div><div>this will actually land late this&nbsp;year or in&nbsp;2014.</div><div> </div><div>To reiterate, The only&nbsp;IPython functionality needed&nbsp;</div><div>is the ability&nbsp;to load and view remote&nbsp;HTML pages, and that only</div><div>as a substitute to using a separate&nbsp;browser window.&nbsp;</div><div>Is that really something you're planning to disallow? &nbsp;</div><div>If so, I strongly urge you not to throw away a feature that makes&nbsp;</div><div>IPython-notebook as powerful as the web.&nbsp;</div><div> </div><div>Wouldn't an Opt-in mechanism be sufficient?</div><div> </div><div>As for&nbsp;strong assumptions, The only assumption I'm really making&nbsp;</div><div>is that there's a network connection between the front-end&nbsp;and&nbsp;</div><div>where the kernel is. Cross-origin issues are already addressed&nbsp;with</div><div>built-in JSONP and&nbsp;CORS support.</div><div>Could you elaborate on how this assumption might be violated in the future?</div><div>Surely&nbsp;a user working on his laptop on a local file, with a local kernel</div><div>should be able to access&nbsp;local urls. I'm less interested in other&nbsp;</div><div>use-cases, and frankly don't have the resources to pursue them.</div><div> </div><div>I'm trying to keep things&nbsp;generic, so hopefully&nbsp;views will&nbsp;be</div><div>easily portable to the new architecture when it arrives.&nbsp;</div><div> </div><div>I've started work on a crossfilter (<a href="http://square.github.com/crossfilter/">http://square.github.com/crossfilter/</a>)&nbsp;based&nbsp;</div><div>"lasso" UI, that allows you to graphically filter a python dataset&nbsp;by selecting&nbsp;</div><div>points across different dimensions, and pick up the filtered dataset&nbsp;back in python.</div><div>Unless I hit a wall, there should be a demo up in a couple of weeks.&nbsp;</div><div> </div><div>stay tuned,</div><div>Yoval</div><div> </div><div> </div><div> </div><div><span style="font-family: 'Times New Roman'; font-size: medium; background-color: rgb(255, 255, 255);">Matthaias Bussonnier Wrote:</span></div><div>&gt; Do you rely on display_javascript for the initial loading of javascript ? or inject &lt;script&gt; tag in a display HTML</div><div><pre>&gt; If you do , this can be problematic in the future.

</pre></div><div><span style="font-family: 'Times New Roman'; font-size: medium; background-color: rgb(255, 255, 255);">Brian Granger Wrote:</span></div><div><pre>&gt;<i> This is really cool to see work like this happening. Very nice!
</i>&gt;<i>
</i>&gt;<i> I wanted to update you on the development situation with IPython that
</i>&gt;<i> may affect your code:</i></pre><pre><span style="font-family: Verdana;">This is really cool to see work like this happening. Very nice!</span>
</pre><div><pre>I wanted to update you on the development situation with IPython that
may affect your code:

* We plan on starting to work on creating a nice architecture for
interactive JavaScript widgets, in late summer.
* This architecture will enable all of this to be done without any
additional server logic.
* Using additional server logic as you have done is not officially
supported. What I mean by this is that the notebook architecture may
change in a way that makes it impossible to do this type of thing.
The problem is that you have made some strong assumptions about where
the notebook server, kernel and your server are running. The
preferred way of getting data back and forth between python and the
browser is to use our message channels. Currently these channels are
not sufficient for what you want to do, but after are work later this
year, they will be.
* Because of security issues are are moving away from the notebook
being able to execute dynamically generated javascript code. We will
replace this with a javascript plugin system that is more secure. You
will have to rewrite things when this happens.