veyepar: The story of redux-logic, a new approach to organizing business logic with Redux

Hi user

Admin Login:

Name: The story of redux-logic, a new approach to organizing business logic with Redux
--client nodevember --show nodevember16 --room Stowe_Hall 11529 --force
Prev: 11 Universal Apps: Lessons from the trenches
Next: 11 This Is NativeScript

show more...

Author(s):	Jeff Barczewski
Location	Stowe Hall
Date	nov Sun 20	Days Raw Files
Start	15:45	First Raw Start	15:43
Duration	00:35:00	Offset	0:01:54
End	16:20	Last Raw End	16:43
Chapters	00:00 0:21:19
Total cuts_time	30 min.

http://nodevember.org/talk/Jeff%20Barczewski
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

final audio

assets release.pdf The_story_of_reduxlogic_a_new_approach_to_organizing_business_logic_with_Redux.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
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
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Like many of you, I was searching for the best way to build my JavaScript applications. How do I structure my code properly so my app can grow without being boxed in? I started experimenting to find the best approach to use for my Redux apps. There seemed to be a good sized gap between my ideal goals and the way others were doing things. Was I doing things wrong or just misunderstanding the ideas? I explored further by reading blog articles, questions and answer forums, github issues trying to gain all the knowledge I could. It seemed like I was still missing something. The solutions people were leading me to were either lacking in capabilities or the resulting code was much too complex for my liking. I wanted things to be simple and straight-forward so that any of my teammates could easily pick things up, understand, and be comfortable working with it. How could these solutions be the recommended ways to structure my code? Is there a better way? After finally grasping the essence of what I was looking for and taking inspiration from existing projects, I set out to build that small focused library. I wanted to see if it might be possible. It seemed reasonable on paper, but would it work? I share all the highlights of my journey and explain the simple inner workings of redux-logic. Everyone who attends will come out with a better understanding of business logic and how to apply it in Redux. markdown
Comment:	production notes

recording sheet

2016-11-20/2016-11-20/15_43_06.ts Apply: 15:43:06 - 15:51:47 ( 00:08:41 ) S: 15:43:06 - E: 16:13:06 D: 00:30:00 (End: 521.0) show more...

vlc ~/Videos/veyepar/nodevember/nodevember16/dv/Stowe_Hall/2016-11-20/2016-11-20/15_43_06.ts :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	15:43:06		seconds: 0.0 Wall: 15:43:06
Duration	00:30:00
	16:13:06		seconds: 521.0 Wall: 15:51:47
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-11-20/2016-11-20/15_43_06.ts Apply: 15:51:47 - 16:13:06 ( 00:21:19 ) S: 15:43:06 - E: 16:13:06 D: 00:30:00 (Start: 521.0) show more...

vlc ~/Videos/veyepar/nodevember/nodevember16/dv/Stowe_Hall/2016-11-20/2016-11-20/15_43_06.ts :start-time=0521.0 --audio-desync=0

	Raw File	Cut List
	15:43:06		seconds: 521.0 Wall: 15:51:47
Duration	00:30:00
	16:13:06		seconds: 0.0 Wall: 15:43:06
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-11-20/2016-11-20/16_13_06.ts Apply: 16:13:06 - 16:22:00 ( 00:08:54 ) S: 16:13:06 - E: 16:43:06 D: 00:30:00 (End: 534.0) show more...

vlc ~/Videos/veyepar/nodevember/nodevember16/dv/Stowe_Hall/2016-11-20/2016-11-20/16_13_06.ts :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	16:13:06		seconds: 0.0 Wall: 16:13:06
Duration	00:30:00
	16:43:06		seconds: 534.0 Wall: 16:22:00
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-11-20/2016-11-20/16_13_06.ts Apply: 16:22:00 - 16:30:46 ( 00:08:46 ) S: 16:13:06 - E: 16:43:06 D: 00:30:00 (Start: 534.0) (End: 1060.0) show more...

vlc ~/Videos/veyepar/nodevember/nodevember16/dv/Stowe_Hall/2016-11-20/2016-11-20/16_13_06.ts :start-time=0534.0 --audio-desync=0

	Raw File	Cut List
	16:13:06		seconds: 534.0 Wall: 16:22:00
Duration	00:30:00
	16:43:06		seconds: 1060.0 Wall: 16:30:46
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2016-11-20/2016-11-20/16_13_06.ts Apply: 16:30:46 - 16:43:06 ( 00:12:20 ) S: 16:13:06 - E: 16:43:06 D: 00:30:00 (Start: 1060.0) show more...

vlc ~/Videos/veyepar/nodevember/nodevember16/dv/Stowe_Hall/2016-11-20/2016-11-20/16_13_06.ts :start-time=01060.0 --audio-desync=0

	Raw File	Cut List
	16:13:06		seconds: 1060.0 Wall: 16:30:46
Duration	00:30:00
	16:43:06		seconds: 0.0 Wall: 16:13:06
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this

2016-11-20/2016-11-20/15_43_06.ts
audio viz

audio viz

2016-11-20/2016-11-20/16_13_06.ts
audio viz

audio viz

Veyepar Video Eyeball Processor and Review