<p dir="ltr">Just from a pure user standpoint, I am certainly interested in something like this. Looks cool!</p>
<div class="gmail_quote">On Feb 4, 2015 9:33 AM, "Cedric GESTES" <<a href="mailto:cedric.gestes@gmail.com">cedric.gestes@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for your advices.<div><br></div><div>I made an IPython notebook extension out of my hack.</div><div><br></div><div>I started by applying some of your comments. Each dock now has a cell. The input part of the cell can be toggled to only display output. (ie widgets)</div><div><br></div><div>The code can be found here:</div><div><a href="https://github.com/kwikteam/ipython-nbdock" target="_blank">https://github.com/kwikteam/ipython-nbdock</a><br></div><div><br></div><div>I plan to use bootstrap and FA as advertised.</div><div><br></div><div>I have an issue with cells, they do not belong to the main notebook.</div><div><br></div><div>I wonder if it is better to use cell directly, or to use a full notebook in each dock?</div><div>Issues are: saving/reloading/cell focus/...</div><div><br></div><div>a screenshot is attached.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 30, 2015 at 11:30 AM, Matthias Bussonnier <span dir="ltr"><<a href="mailto:bussonniermatthias@gmail.com" target="_blank">bussonniermatthias@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Hi, </div><div><br></div>To add to what Nicholas said, <div>After IPython 3.0 we will split the widget in a separate repository. </div><div>It will be easier to contribute/discuss than just before 3.0 release</div><div>or while widget are still tightly entangled with IPython code. </div><span><font color="#888888"><div>-- </div><div>M</div></font></span><div><span><font color="#888888"><div><br></div></font></span><div><span><font color="#888888"><br></font></span><div><span><font color="#888888"><div>Le 29 janv. 2015 à 19:32, Nicholas Bollweg <<a href="mailto:nick.bollweg@gmail.com" target="_blank">nick.bollweg@gmail.com</a>> a écrit :</div></font></span><div><div><br><blockquote type="cite"><div dir="ltr"><div><div>cedric:<br><br></div>this looks very cool: as the "ipython is not a platform" party line softens, ideas like this are important for pushing what "interactive computing" can be like. My immediate concern would be in not knowing which cell a particular widget came from. Additionally, from a purely stylistic sense, try
using bootstrap panels and fontawesome to make it flow more seamlessly
with the notebook UI.<br></div><div><br>I think several folks have been looking for this in the past, especially with creating such controls at notebook load time:<br><a href="http://python.6.x6.nabble.com/How-To-create-persistent-interactive-UI-elements-outside-cells-td5079080.html#a5079562" target="_blank">http://python.6.x6.nabble.com/How-To-create-persistent-interactive-UI-elements-outside-cells-td5079080.html#a5079562</a><br><br>I'd say near-term, see if you can repackage this into an nbextension that someone can optionally add at profile config/run-time. If it can be made into pure javascript that stores its data in the notebook/cell metadata, that lowers the barrier to entry... and makes it more feasible to use with other kernels.<br><br>Otherwise, if you need the python part, there is the approach taken by <a href="https://github.com/takluyver/cite2c" target="_blank">cite2c</a>. Specifically, allowing the configuration of the web app (not the kernel) to include <a href="https://github.com/takluyver/cite2c/blob/master/install.py#L11" target="_blank">loading custom extensions</a>.</div><div><br>i have been interested in alternate editable layouts for some time: of them i think <a href="https://github.com/damianavila/live_reveal" target="_blank">live_reveal</a>, while still a little fiddly to install, has the most potential for becoming something that would make sense to ship with the notebook experience, especially as it is cell-based, (really) front-end only and its metadata is already integrated into nvconvert and (soon, hopefully!) nbviewer. If your widgets could survive nbviewer (either with or without help from a custom converter) that would be really cool... once static widgets are supported.<br></div><div><br>i have a bit of python widget code that will populate widgets on top of SVG regions (as defined by layers in inkscape): this makes it easy to build up full-screen capable dashboards without requiring a lot of CSS/JS knowledge.<br><br></div><div><span style="font-family:monospace,monospace">SVGLayout(svg="dashboard.svg",<br> children={"chart": SomeChartWidget()})</span><br></div><div><br></div><div>i want to refactor it into pure javascript as well.<br><br></div><div>keep the list posted!<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 29, 2015 at 11:57 AM, cedric gestes <span dir="ltr"><<a href="mailto:ctaf42@gmail.com" target="_blank">ctaf42@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I hacked a prototype of dockable widgets using DockSpawn.<br>
<br>
see<br>
<a href="http://www.hostingpics.net/viewer.php?id=990121201501291741191600x900scrot.png" target="_blank">http://www.hostingpics.net/viewer.php?id=990121201501291741191600x900scrot.png</a><br>
for a screenshot.<br>
<br>
Before going further I would like to take your advice on the subject.<br>
<br>
Is that something wanted in IPython?<br>
<br>
We can imagine having cells and widgets in docks.<br>
<br>
The prototype is hackish and just a proof of concept.<br>
<br>
You can find it github on the branch dockspawn of:<br>
<a href="http://github.com/ctaf42/ipython" target="_blank">github.com/ctaf42/ipython</a> and <a href="http://github.com/ctaf42/ipython-components" target="_blank">github.com/ctaf42/ipython-components</a><br>
<br>
just checkout, run IPython and open a notebook like this one:<br>
<a href="http://nbviewer.ipython.org/gist/ctaf42/e029c475b08bdfe43f6a" target="_blank">http://nbviewer.ipython.org/gist/ctaf42/e029c475b08bdfe43f6a</a><br>
<br>
Cedric<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://python.6.x6.nabble.com/Dockable-widgets-for-IPython-tp5084622.html" target="_blank">http://python.6.x6.nabble.com/Dockable-widgets-for-IPython-tp5084622.html</a><br>
Sent from the IPython - Development mailing list archive at <a href="http://Nabble.com" target="_blank">Nabble.com</a>.<br>
_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
</blockquote></div><br></div>
_______________________________________________<br>IPython-dev mailing list<br><a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br><a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br></blockquote></div></div></div><br></div></div></div><br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div>