Dear Pascal

See my answers inside:

neat... works in windows, some caveats though:
> Thanks ;-)

wait until a cell executes (* means not done yet) before executing next one.
upon opening the notebook, likely each cell with definitions need to be 
executed before one using those definitions is.
> As far as I know, this is the normal behavior of a Jupyter Notebook.
> Please tell me if I'm wrong.

distribution includes qjide which is a cool web front end that also depends on 
python.
Macs get 64 bit, but windows/linux not. :(
> Currently, I don't have access to a 64-bit Linux machine :-(
> But we are working on a 64-bit version for Linux.
> On Windows, the 32-bit version of the package works quite well on 64-bit 
> Windows.
> You may always do a manual installation into your 64-bit environment,
> please see: https://github.com/martin-saurer/jkernel

qjide doesn't like internet explorer (windows 8.1 version), but firefox is 
good.  Actually ie works ok on restart but then breaks quickly again.
> Yes, I know. Internet Explorer as well as Microsoft's new Edge Browser don't 
> work well
> with qjide. It seems the problem is not with qjide itself, but with the 
> web-server part
> of Python.

In trying to transfer jupyter url from ie (default browser) to firefox, I get 
asked for a password/token, but the command to find a token does not provide 
one.  restarting jupyter from .bat file does provide a tokenized url that I can 
paste in the browser of my choice. (firefox strips LF, chrome doesn't)
> I tried to paste the URL provided in the command window to the address bar of
> Chrome, Firefox, IE, Edge, and all of them accepted it without problems.

Large labs such as A_J_introduction are quite slow to load.
> Yes. This seems to happen on all platforms. A Jupyter Notebook is a more or 
> less
> large JSON file. Maybe that's the reason why it takes that long.

Best Regards

Martin

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to