Re: [jupyter] Android Native FrontEnd for Jupyter Notebook

2018-01-08 Thread Kazuma Arino
Thank you for your interested.
If connecting to kernel fail, this app is just crush without any hint.

So settieg up environment might be a little difficult now.
Goog luck!

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/9a33efc2-314d-4d52-b624-195ecc2cad5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[jupyter] Notebook Cell Events in JupyterLab

2018-01-08 Thread Thorin Tabor
Hello,

I'm beginning to look into porting the nbextensions I've developed to 
JupyterLab as labextensions, and after combing through the JupyterLab 
documentation, I have a couple questions.

1) Does JupyterLab have client-side event hooks for creating and editing 
notebook cells? For example, in Jupyter Notebook I can fire off events in 
response to creating a cell or changing the cell's mode (such as with the 
code shown below). But so far I haven't been able to find the equivalent 
functionality in JupyterLab.

$([Jupyter.events]).on('create.Cell', function(event, target) {
// Do something
});
$([Jupyter.events]).on('edit_mode.Cell', function(event, target) {
// Do something
});
$([Jupyter.events]).on('command_mode.Cell', function(event, target) 
{
// Do something
});

2) So far I've found labextension development to be somewhat slow. Part of 
that is definitely just me getting over the learning curve, but part of it 
may also be that my development process needs to be altered to better fit 
the JupyterLab environment.

a) By default, JupyterLab bundles the client-side assets in labextensions, 
but doesn't seem to provide a source map. So when I have an error in my 
labextension's Javascript, it's difficult to trace the error back to the 
offending line of code. Is there a place I'm supposed to enable source maps 
in the JupyterLab config or a command line option? (I've noticed the 
--dev-mode command line option, but so far that hasn't worked for me.)

b) In Jupyter Notebook, when developing nbextensions, I did most of my 
exploration of the available method calls and framework through the 
browser's Javascript console. I could call the top-level *Jupyter* variable 
and then use that to explore all of the available properties and methods of 
that object. So far I haven't seen an easy way to do something similar in 
JupyterLab. Is there a recommended way to explore the available methods, 
models and hooks?

Thanks for any help anyone can offer!

Thorin Tabor

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/b72adafa-ba8c-43e0-9c59-6a9f103ad5a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[jupyter] notebook 5.3.0rc1

2018-01-08 Thread Grant Nestor
We have just published a release candidate for notebook 5.3.0 on PyPI 
. This release introduces 
terminal support for Windows, support for OS trash (files deleted from the 
notebook dashboard are moved to the OS trash vs. deleted permanently), a 
new "restart and run all" button to the notebook toolbar, and quite a bit 
more 
.

Please give it a try:

pip install notebook --pre --upgrade

Note that you will need to restart the notebook server and possibly 
hard-refresh any open notebook tabs in your browser (or clear your 
browser's cache) after upgrading to ensure that you are running 5.3.0rc1.

We hope to release 5.3.0 by Thursday.

Feel free to provide feedback here or by creating an issue on Github 
.

Thanks!

Grant 

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/18c8ac5d-80d0-4cb3-8f16-d2567324fe11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [jupyter] Re: Protected Jupyter Notebooks

2018-01-08 Thread Matthias Bussonnier
For the preventing copy-past you can set some cell metadata to
`metadata.editable=false`, I think some frontend will then prevent you to
copy-past the source. It's pretty easy to get around though.

The notebook top-level metadata supports arbitrary fields. As notebook are
json you can easily add a random UUID to these. Once you have a unique UUID
per notebook, it's easier to setup a google alert that tell you whether
this UUID has been found.

Again it's relatively easy to remove, but you have to know it is there.

If you have a tiny bit more resources, then you can add a second field
which is related to the user having bought the book. Again, as notebook are
Json it's just a matter of opening the files, adding this field and writing
it back.
If you really have a lot of downloads, it can even be done really fast by
directly modifying the bytes in files. Simply set this field a first time
to a long, know string, lookup the bytes offset of this string, and now you
can do a quick raw search and replace.

And you can even be more sneaky, see for example this HN thread[1] with ZW
spaces, but you can also use Homoglyphs, to fingerprint leaks.

Preventing leaks will though I'm afraid be close to impossible.

Look at what other authors have done, like Jake van Der Plas, whose
notebook are open, but only part of the content that you get with the full
book.
-- 
M

1: https://news.ycombinator.com/item?id=16046329

On 8 January 2018 at 18:35, insearchof answers <
insearchofanswer...@gmail.com> wrote:

> Hi Matthias, anything at all that would discourage piracy and would make
> it possible to track piracy would be great. We're open to all suggestions.
>
> On 7 January 2018 at 08:12, Matthias Bussonnier <
> bussonniermatth...@gmail.com> wrote:
>
>> It also depends what you mean by "protecting content in Jupyter
>> Notebooks" does that mean making it hard to copy ? Does that mean figuring
>> out a way to finger-print the notebook in order to easily detect leaked
>> version. Or do you want a more complex tagging that would identify which
>> user have leaked the notebook ?
>>
>> Completely protecting is hard, but there are potentially soft mitigation
>> to track notebooks if this is what you are looking for.
>> --
>> M
>>
>> On 7 January 2018 at 00:14, Lawrence D’Oliveiro 
>> wrote:
>>
>>> On Sunday, January 7, 2018 at 6:41:02 AM UTC+13, insearcho...@gmail.com
>>> wrote:


 On Thursday, 4 January 2018 19:07:13 UTC-5, Lawrence D’Oliveiro wrote:

>>>

>>> On Friday, January 5, 2018 at 6:14:54 AM UTC+13, insearcho...@gmail.com
> wrote:
>

>>
> I'd like to create a Jupyter version of a textbook I am working on and
>> need to consider piracy of the content.
>>
>> Isn’t that what copyright is for?
>


>>> :-) Yes, but as an author whose content is extensively pirated
 worldwide, I know that copyright unfortunately does not mean anything to a
 many people.

>>>
>>> If law doesn’t help, technical measures aren’t going to matter either.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Project Jupyter" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jupyter+unsubscr...@googlegroups.com.
>>> To post to this group, send email to jupyter@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jupyter/1cc6c804-1346-485b-843d-96bdf011b776%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Project Jupyter" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/jupyter/IRd3QSqWFUE/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jupyter/CANJQusX0SqpdV2Q3SJfgz-62Fb7KB%3DRigkmYYN1EE3PR08-zeQ%40mail.
>> gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jupyter/CA%2Bsg3DXY%3DreFBLRwSj7E0Xsd9-e3xBsOfnogFOWRAJDqNn4jMA%
> 

Re: [jupyter] Re: Protected Jupyter Notebooks

2018-01-08 Thread insearchof answers
Hi Matthias, anything at all that would discourage piracy and would make it
possible to track piracy would be great. We're open to all suggestions.

On 7 January 2018 at 08:12, Matthias Bussonnier <
bussonniermatth...@gmail.com> wrote:

> It also depends what you mean by "protecting content in Jupyter
> Notebooks" does that mean making it hard to copy ? Does that mean figuring
> out a way to finger-print the notebook in order to easily detect leaked
> version. Or do you want a more complex tagging that would identify which
> user have leaked the notebook ?
>
> Completely protecting is hard, but there are potentially soft mitigation
> to track notebooks if this is what you are looking for.
> --
> M
>
> On 7 January 2018 at 00:14, Lawrence D’Oliveiro 
> wrote:
>
>> On Sunday, January 7, 2018 at 6:41:02 AM UTC+13, insearcho...@gmail.com
>> wrote:
>>>
>>>
>>> On Thursday, 4 January 2018 19:07:13 UTC-5, Lawrence D’Oliveiro wrote:
>>>
>>
>>>
>> On Friday, January 5, 2018 at 6:14:54 AM UTC+13, insearcho...@gmail.com
 wrote:

>>>
>
 I'd like to create a Jupyter version of a textbook I am working on and
> need to consider piracy of the content.
>
> Isn’t that what copyright is for?

>>>
>>>
>> :-) Yes, but as an author whose content is extensively pirated worldwide,
>>> I know that copyright unfortunately does not mean anything to a many people.
>>>
>>
>> If law doesn’t help, technical measures aren’t going to matter either.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Project Jupyter" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jupyter+unsubscr...@googlegroups.com.
>> To post to this group, send email to jupyter@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jupyter/1cc6c804-1346-485b-843d-96bdf011b776%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Project Jupyter" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jupyter/IRd3QSqWFUE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jupyter/CANJQusX0SqpdV2Q3SJfgz-62Fb7KB%3DRigkmYYN1EE3PR08-
> zeQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CA%2Bsg3DXY%3DreFBLRwSj7E0Xsd9-e3xBsOfnogFOWRAJDqNn4jMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [jupyter] Android Native FrontEnd for Jupyter Notebook

2018-01-08 Thread Thomas Kluyver
Cool, I'm definitely going to play with this on my tablet when I'm back
home. Thanks Kazuma!

On 8 January 2018 at 03:21, Kazuma Arino  wrote:

> Hi, I'm creating native android Notebook frontend.
>
> It's still alpha stage, but now basic functionality working and I can
> start using for my daily work (though still unstable).
> Here is the basic demo of how it looks like:
>
> https://www.youtube.com/watch?v=nZtCSpGnVzk
>
> PR is welcommed :-)
>
> Source code
> https://github.com/karino2/NotebookFrontend
>
>
> Play page
> https://play.google.com/store/apps/details?id=karino2.livejournal.com.
> notebookfrontend
>
>
> Some details:
> - This app connect to localhost with specified port number. You must setup
> portfowarding
> - This app only support token authentication. no password support.
> - Basic cell execution is done via websocket, while save-restart
> kernel-file browsing is via REST request
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jupyter+unsubscr...@googlegroups.com.
> To post to this group, send email to jupyter@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jupyter/c7cdc980-293a-4ef1-9a69-9871c6d0bd86%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jupyter+unsubscr...@googlegroups.com.
To post to this group, send email to jupyter@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAOvn4qjMF3h_tzR47-bhdeEbhoOW67WEoUEXSmqynkr2ZEtV1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.