Hi
user
Admin Login:
Username:
Password:
Name:
Is your helper library opinionated enough?
--client
pytexas
--show
pytexas2014
--room MSC_2300_A 8698 --force
Next: 1 I ♥ Maps: Quantum GIS + Python
show more...
Marks
Author(s):
Paul Murphy
Location
MSC 2300 A
Date
oct Sat 04
Days Raw Files
Start
09:00
First Raw Start
08:59
Duration
00:25:00
Offset
0:00:59
End
09:25
Last Raw End
09:26
Chapters
00:00
0:00:02
0:00:04
Total cuts_time
25 min.
http://www.pytexas.org/2014/talks/39/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Is_your_helper_library_opinionated_enough.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
It's a constant debate. How do you build a helper library? At one end of the spectrum we have Runscope CEO John Sheehan who thinks that helper libraries are evil and shouldn't exist at all. At the other we find helper libraries that don't look or smell anything like the API. And somewhere in the middle we have helper libraries that are so close to the API itself that they are nothing more than a thin veneer. Which is better? Who’s right? The real question to me is how idiomatic should a helper library be? Should a Django library make a Django developer feel comfortable, or should she have to read the API docs to understand how it works? Should a Python library look RESTful, or should it look like a hierarchy of classes? At our company, we maintain two libraries. They both have advantages and disadvantages, they appeal to different developers, and sometimes even the same developer at different times.
Comment:
production notes
2014-10-04/08_59_01.dv
Apply:
08:59:01 - 09:00:29 ( 00:01:28 )
S:
08:59:01 -
E:
09:00:29
D:
00:01:28
show more...
vlc ~/Videos/veyepar/pytexas/pytexas2014/dv/MSC_2300_A/2014-10-04/08_59_01.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
08:59:01
seconds: 0.0
Wall: 08:59:01
Duration
00:01:28
09:00:29
seconds: 0.0
Wall: 08:59:01
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2014-10-04/09_00_29.dv
Apply:
09:00:29 - 09:00:31 ( 00:00:02 )
S:
09:00:29 -
E:
09:00:31
D:
00:00:02
show more...
vlc ~/Videos/veyepar/pytexas/pytexas2014/dv/MSC_2300_A/2014-10-04/09_00_29.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
09:00:29
seconds: 0.0
Wall: 09:00:29
Duration
00:00:02
09:00:31
seconds: 0.0
Wall: 09:00:29
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2014-10-04/09_00_32.dv
Apply:
09:00:32 - 09:00:34 ( 00:00:02 )
S:
09:00:32 -
E:
09:00:34
D:
00:00:02
show more...
vlc ~/Videos/veyepar/pytexas/pytexas2014/dv/MSC_2300_A/2014-10-04/09_00_32.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
09:00:32
seconds: 0.0
Wall: 09:00:32
Duration
00:00:02
09:00:34
seconds: 0.0
Wall: 09:00:32
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2014-10-04/09_00_34.dv
Apply:
09:00:34 - 09:26:08 ( 00:25:34 )
S:
09:00:34 -
E:
09:26:08
D:
00:25:34
show more...
vlc ~/Videos/veyepar/pytexas/pytexas2014/dv/MSC_2300_A/2014-10-04/09_00_34.dv :start-time=00.0 --audio-desync=0
Raw File
Cut List
09:00:34
seconds: 0.0
Wall: 09:00:34
Duration
00:25:34
09:26:08
seconds: 0.0
Wall: 09:00:34
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2014-10-04/08_59_01.dv
2014-10-04/09_00_29.dv
2014-10-04/09_00_32.dv
2014-10-04/09_00_34.dv
Veyepar
Video Eyeball Processor and Review
