Josh Abernathy

Oof, yeah, you could dynamically implement selectors using the Objective-C runtime to call through to JS.

https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/ObjCRuntimeGuide/Articles/ocrtDynamicResolution.html is probably a good starting point.

Hmm, so if I apply the following patch: ``` patch diff --git a/Few-iOS/TableView.swift b/Few-iOS/TableView.swift index de5c1bf..eaf8269 100644 --- a/Few-iOS/TableView.swift +++ b/Few-iOS/TableView.swift @@ -322,14 +322,10 @@ public class TableView: Element {...

Certainly true. I personally don't have a whole lot of need for ADK support, but it shouldn't be too crazy for someone to do the necessary bindings.

Yeah, I'd really like to avoid making `Element` `Equatable` for those reasons :point_up:

On Mac we save and restore the selected indexes: https://github.com/joshaber/Few.swift/blob/221ff4ccf6c339bb7d815398614556b07a80073d/Few-Mac/TableView.swift#L53-56 Could we do that on iOS too?

I'm really curious to see how React Native does this. I've (obviously) been pretty Mac-centric where I think something like this is less necessary. But on iOS it'd be really...

Pulled from the example in http://techjaw.com/2015/02/23/pre-release-react-native-talk-at-facebooks-london-office-react-js-user-group/:  

No great ideas at the moment. A protocol could suffice though it puts the work on the user.

Yeah probably. React has a similar hook.