Josh Abernathy
Josh Abernathy
This is great, thanks for starting to think through it! I'm wondering what the motivation is for separating `ElementType` and `Layoutable`? It seems unlikely we'd need one without the other.
(Sorry for taking so long to answer!) Ah, yeah, so this is kinda interesting. `Input` has a default frame: https://github.com/joshaber/Few.swift/blob/b53fbd13026cf13327b2a66fc87f9189787656bb/Few-iOS/Input.swift#L56 which means the layout algorithm will use that instead of...
> And is there any reason why Input has a default width of 100? Mostly because at the time it seemed like a good idea to have a reasonable default...
> I could work on a PR for it if you wouldn't mind. That'd be great! I wonder if we should still have a default but leave the width undefined?
Yeah this is tricky :\ Presumably we want to use Core Animation to do the interpolation. It's not terribly clear to me how we can treat the animation as a...
I definitely like the conceptual purity to that. :+1: A couple immediate thoughts: 1. It's hard to see how that would fit with allowing Core Animation to do the interpolation....
Oh no, I think it's definitely interesting. Especially in the sense that it's true to the "views as functions of their state" description.
(:metal: Can't wait to see ComponentKit!)
I lean towards "no" for all of that, for simplicity's sake.
I'm not sure anything involving multithreading is ever trivial :smile: I'm not convinced that the tradeoffs in complexity are worth it. I think we'd need some concrete cases where performance...