4 ms·
Shouldn't it the other way around? 1. receive an "intent" (request) 2. get whatever data that intent depends on 3. choose a suitable view I tend of think UIs
by gcanti 12y ago
Shouldn't it the other way around?
1. receive an "intent" (request)
2. get whatever data that intent depends on
3. choose a suitable view
I tend of think UIs as projections of the state/model
- bsimpson 12y agoYou used different words to describe the same flow. More importantly, I'm talking about the _features_ that need to be isomorphic, not necc. every little step. I think we can presume that any server knows how to "receive a request".