On 14 March 2017 at 16:13, Ben Marwick wrote:
> Looks like it can enable learners to easily access the live-coding file on
> the fly, with the file continuously updated as the instructor saves the
> file during the lessons.
On the conference I organised last week
Just adding to the link Ben posted. I used that line in a tool I made a few
years ago, if anyone is curious to see it in context. This tool creates a
self-updating html page of the history, so users don't have to manually
refresh the page. it also doesn't auto-scroll them back to the top of the
I find things like this really helpful for allowing people to follow
along as you go, and students seem to really appreciate having the
record to download and refer back to.
A Dropbox public links works well for this too. For R, I usually save
the script somewhere in Dropbox (or other cloud
I just came across this little app, it lets you code locally (for
example, in RStudio), and when you save it automatically updates a copy
of the file at public URL: https://github.com/hikarock/casto
It might be useful for keeping a log of live-coding during a SWC workshop.
Looks like it can
Is there a "standard" way of incorporating spellcheck in jupyter notebook
markdown cells? I found a few ad-hoc solutions on the web (calico?, aspell?) -
is there a solution that's easy to share in a workshop?
Nathan
- - - - - - - - -
Nathan Moore
Professor, Physics
Winona State University