That's how I'm currently doing it, yes.
I'm sure there are many other ways that work just as well too.
On 12 April 2014 19:49, Dmitry Suzdalev wrote:
> Thanks, will keep this in mind. Am I understanding correctly that when B
> modifies Y it communicates that change to A through the channel whi
Thanks, will keep this in mind. Am I understanding correctly that when B
modifies Y it communicates that change to A through the channel which is in
:shared state?
On 12 April 2014 20:49, Daniel Kersten wrote:
> Yes, the multiple cursors solution works quite well with the caveat that
> intermed
Yes, the multiple cursors solution works quite well with the caveat that
intermediary components must make sure not to discard parts of the cursor
that lower components need.
Another approach that is working well for me as a temporary solution is to
store this information in local state and using
Understood.
Well, after reading through this thread, I see that
a) David is working on a solution to this problem, which will deliver both
convenience and auto updates
b) for now there's an option to pass multiple cursors to the component
(there's an example in Om's wiki, on 'Cursors' page)
12 апр
Ah, yes, I meant shared state. The reason I was saying shared and not app
is that app state usually gets "narrowed" the lower in the component tree
you get, so when your low down in the tree and then need to access
something on a completely different branch, how do you do this without
accessing the
Ok :) If you are talking about :shared state, than it's true, but for the
generic case of the global app state, auto updates are supposed to work
regardless of which part of the state cursor points to AFAIK.
12 апр. 2014 г. 17:37 пользователь "Daniel Kersten"
написал:
> I think perhaps I was misu
Pulled Tao out of a recent project. Handles the route problems your
describing...would love feedback
https://github.com/pleasetrythisathome/tao
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed
I think perhaps I was misunderstanding how cursors work. Let me try it out
and get back to you then :)
On 12 April 2014 12:25, Dmitry Suzdalev wrote:
> Hi Daniel!
>
> Can you clarify this moment a bit for me:
>
> On Wednesday, April 9, 2014 2:33:31 PM UTC+4, Daniel Kersten wrote:
> > I can pass
CSSTransition groups are cool, but often what you want to do is transition
state (or props). I wrote a tiny thing along the same lines for React which
I've used a lot in production
https://github.com/pleasetrythisathome/react.animate
Haven't had time to write the corresponding Om stuff yet, but
Hi Daniel!
Can you clarify this moment a bit for me:
On Wednesday, April 9, 2014 2:33:31 PM UTC+4, Daniel Kersten wrote:
> I can pass the entire app state to each component (perhaps trough shared
> state) and use transformation functions (similar to what Sean Grove did in
> his recent slides) t
Thank you Jack for this question and later example, it certainly helps a
newcomer like me :)
Dmitry.
On Sunday, March 16, 2014 11:39:33 PM UTC+4, Jack Schaedler wrote:
> Hi David,
>
>
>
> Thanks for the quick response! Seems to be working just fine now. I must have
> screwed up something simp
11 matches
Mail list logo
