Clay Allsopp

Hm, so if we keep the same name, how does this implementation of `shouldComponentUpdate` interact with existing implementations? I.e. I have a component and already have some logic in `shouldComponentUpdate`...

Ah yeah. Personally, I think ditching blocks and mimicking that library's API is a good idea, with documentation that says those methods will block the running thread: ``` ruby Dispatch::Queue.concurrent.async...

Yup! As long as it had tests :)

:+1: looks like we should `sam_colorWithCSS`, right?

Hmm you mean `UITabBarController`? It's not directly supported in Routable. One idea is to create five different `Routable::Router`s, one for each tab, and each tab has it's own `UINavigationController` as...

hmmm if I remove the `require "bubble-wrap"` in remote_model.rb and uninstall/build/install the gem locally it works (as in it at least compiles the remote_model files), but if I keep that...

oh looks like there's some new instructions for using BubbleWrap as a dependency (https://github.com/mattetti/BubbleWrap/blob/master/GEM.md), looking into it

@macfanatic can you do a `gem update remote_model` and try now? should update to 0.0.2. I tried a new project locally, added remote_model to the Gemfile and it works for...

Yeah, it works if "anything that you want to protect will require you to have the user to touch the screen to see." There might be a way to support...

Nope, all screen shot detection techniques only work after-the-fact.