quattro_4 scribble

scribble 落書き (調べた事をただ落書きする)

thoughtbot Build Phase #32

Ed Bageley Jr.

Reactive Coco
KVO - Key-Value Coding and Observing
Key-Value Coding and Observing - Foundation - objc.io issue #7


music on
usually itunes
punk ska

begly junior
actor
floating back station
mostly recycle paper
disposable

masatusettu
another storm
what it does
how much time nice weather
crazy winter
humid summer
weather not great
move
choice
usa
small enough
why here
pretty good
hot
one week spring
nothing ever gonna change
similar thing sanfrancisco
california
very high level
super deep understanding
cut this out
c function
kvo thing
leads to elegant code
absolutely mis use over use
wrong
more problem api itself
keypath
prepair for segue
case statement
objc.io
single keypath
retain it
observe valid property
kvo
scope keypath
neat tidy
direct target action
ns keypath
value for key
part of method name
real method
valid key
change immediate
add yourself observer
not clear
order of operation
change notification
readonly property
overriding
first section
category
nil
truthy
doing self.button
kvo stuff
retrigger
update submit button
get change dictionary
reactive coco
dont find
uikit
reactive coco
form fields
everything filled out
not necessary kvo compati
rack signal
not doing straight kvo
debuging
kvo ui text field text
not guarantee observable
kind of binding
link
object oriented
text field
automatically update model object
internal rule
reactive coco example
text is not kvo bable
delegate
as simple as possible
text field
did finish editing
basically have three object
actual view object
sending stuff back
model
valid
update
save button
coredata
valid property ns managed object
model of validation
required
context
binding
view model
dectating
one direction
big circle
waiting for feedback
model never talks to binding
view model
nice place
dead simple
setup text field
awareness of
view model
model object
model dictating
magic
complicated ui
os x
coco binding
generally avoid
kvc
kvo
nasty
in the framework
almost dont see anymore
why the hell
we need binding ios
transition
no clue
that wouldnt surprise at me
observing other way around
why they gave us
memory spike
legacy from app kit
setup binding via
observe
ns object
swap implementation
hook kvo
api
try reactive coco
get idea of
tell dont ask
lot more sense
need to look at again
in general
learning haskell
functional programming
imparative
unreadable
less chaining
fewer square blaket
little cleaner
keep going
experimenting now
classic initialzation pattern
didnt succeed return nil
arc nils out pointers by default
semi colon
preceding initialization
junk data
super init nil
self nil
ivars
not declairing
storage
compiler smarter
explicitly change
stupid pattern
get away from
compiler warning level
self is nil
screwed up condition
more spam
optical testing