freenode/#clasp - IRC Chatlog
Search
3:07:21
drmeister
Bike: The changes you made worked well - everything compiled with no errors. There are fewer GC warnings as well - it's like it was before this problem came up.
3:13:35
drmeister
I'm going to need some help tomorrow figuring out how to turn this into a workflow. Some of the steps involve calculations that take a loooong time and I want every input cell evaluation to return as quickly as possible and the whole jupyter notebook to act as a dashboard that pushes the calculation forward and reports back on how far it has gotten.
3:14:47
drmeister
I'm writing out the am1 charge calculations as a bunch of input files and a makefile.charges that you use to launch the charge calculations.
3:15:09
drmeister
Then the jupyter notebook will read the output files and not proceed until they are all available.
11:48:40
drmeister
Shiho: Everything in 'dev' clasp/cando works - could you clone a new copy and call it 'cando-unsafe' and build that while you work on the older one.
12:17:30
drmeister
On line 142 - how do I access the 'cy' graph that is defined inside of the closure on line 34?
12:28:08
drmeister
I moved the 'cy' variable to the outer scope where onSubmitGraph() was defined and I used: var command = '(defparameter graph::*graph* \"' + JSON.stringify(cy.json()) + '\")';
12:49:18
Shinmera
Do not use onClick or any other JS attributes. Just don't use them. They're severe antipatterns that are obsolete and bad.
13:10:55
drmeister
Shinmera: That goes against the freewheeling "anything goes" ethos of Javascript - doesn't it? :-)
13:11:27
drmeister
var command = '(defparameter graph::*graph* \"' + JSON.stringify(cy.json()).replace(/\"/g,'\\\\\"') + '\")';
13:12:57
Bike
beach: it might have caused a problem in function-tree, presumably by virtue of functions no longer forming a tree, but i'm not sure yet
13:14:16
drmeister
Shinmera: Now - I can only have one of these up at a time right? If I try two - one of them flashes the graph and then goes blank.
13:14:48
drmeister
I only need one - and the new Jupyterlab will allow me to keep it in a separate panel alongside the notebook (I think).