And to answer my own questions:
* Consistent handling of sys-prefix, system and user options
- Which is default?
- Which has priority?
- How are they combined into the final config
* Make it easy to disable or uninstall all extensions for system/sys-prefix/user
Cheers,
Brian
On Thu, Dec
Hi all,
We have just released notebook 4.3.1 and are starting to look towards
a notebook 5.0 release. We have a number of small issues related to
the installation and enabling of nextensions and serverextensions in
the 4.x release series and 5.0/master.
Because the notebook 5.0 will likely be
Hi Sylvain,
Je vois... So the best approach, for now, would be to hide the 'X' button
and add a 'close' button to our widgets layout triggering the appropriate
'thread exit' code on python side. Ok, it doesn't cover the 'cell closed'
case but could help.
Thanks.
N.
Le jeudi 22 décembre 2016
alright bro
On Thursday, December 22, 2016 at 9:02:34 PM UTC+5:30, Vinayak Patankar
wrote:
>
> i realised i used np.loadtext instead of np.loadtxt but still i have error
> :(
> On Thursday, December 22, 2016 at 8:49:19 PM UTC+5:30, Vinayak Patankar
> wrote:
>>
>> Hi takeowl,
>> i have sent the
Hi Brian,
Thank you for the advice.
It sounds like we should first see how far we can go with ipywidgets.
Is there a way of monitoring progress on this front to see what
developments and API changes take place?
Would it be appropriate to request a certain widget type if we foresee that
it
Hi Nicholas,
Thank you very much for the detailed explanation. It is greatly appreciated.
FYI, our application will be something that scientists (not necessarily
experienced programmers) will use to conduct simulations and data analyses.
The users will interact with a browser-based UI, but
Hi Nicolas,
I think that this would be a good think to do to handle the case when a
widget (model) is completely closed from the front-end. However, is it more
subtle than it sounds.
Widgets implement a MVC pattern. The Widget object on the Python side is
synchronized with a Javascript "Model".
