Hi
user
Admin Login:
Username:
Password:
Name:
Code the Docs: Interactive Document Environments
--client
pyconau
--show
pycon_au_2016
--room Room_103 11355 --force
Next: 1 Click: A Pleasure To Write, A Pleasure To Use
show more...
Marks
Author(s):
Paris Buttfield-Addison
Location
Room 103
Date
aug Sun 14
Days Raw Files
Start
11:10
First Raw Start
error-in-template
Duration
0:40:00
Offset
None
End
11:50
Last Raw End
Chapters
Total cuts_time
None min.
https://2016.pycon-au.org/schedule/184/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Code_the_Docs_Interactive_Document_Environments.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
Distributing example code and applications with documentation is now easy. There are a million different ways to get code to people: from zips, to GitHub, to gists, and beyond. Code is easy to distribute. But how do we create a better link between example code, and written documentation? Luckily, clever boffins have come up with some solutions: interactive document environments. These let the live code and the documentation sit side-by-side with one another, the distributed example code is the documentation. This talk will take a brief look at some of the different interactive document environments out there – mainly Jupyter, IPython Notebooks, and Swift Playgrounds – and the various strengths, weaknesses, and caveats of these tools. We’ll also explore the future, and discuss where these tools are going, as well as the implications for technical documentation. Learn how to add interactivity to your documentation, and why this might be a good idea!
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review