I'm familiar with re-frame and have used it. The re-frame model works very
well and I like it a lot.
This conversation was started over a year ago, before re-frame existed and
before Om had ref cursors. The story now is quite different (for both
Reagent and Om).
On Sun, 19 Jul 2015 at 06:14 Kurt
On Wednesday, April 9, 2014 at 6:33:31 AM UTC-4, Daniel Kersten wrote:
Hi,
I'm trying to figure out the best way of structuring complex applications in
Om and I've hit a bit of a brick wall that I'm hoping someone can help me
with.
I like the concept of cursors - narrow down the
Thanks for the reply, David.
On Sunday, October 5, 2014 6:45:26 AM UTC-7, David Nolen wrote:
Ian's NativeStore looks an interesting approach to the problem.
Ah will check it out in detail.
There's also some new work in progress in master, the examples
`two-lists` and `refs` if you are
The idea behind IResolve is that many programs would like to get at
information in the app-state without directly receiving it from a
parent component as the parent component doesn't need it and shouldn't
care.
David
On Mon, Oct 6, 2014 at 1:02 PM, Viksit Gaur vik...@gmail.com wrote:
Thanks for
Hi David,
I've been looking at your new example code and I like where you're going
with this. It looks like a potentially better approach than what was talked
about at the start of this thread. Awesome work!
On 6 October 2014 18:47, David Nolen dnolen.li...@gmail.com wrote:
The idea behind
Hello all,
Any updates on this issue in terms of - how do I access different parts of the
app state from different locations?
Thanks!
On Wednesday, April 9, 2014 3:33:31 AM UTC-7, Daniel Kersten wrote:
Hi,
I'm trying to figure out the best way of structuring complex applications in
Om
Ian's NativeStore looks an interesting approach to the problem.
There's also some new work in progress in master, the examples
`two-lists` and `refs` if you are willing to spend some time reading
uncommented code. Lengthier explanations are planned.
David
On Sun, Oct 5, 2014 at 5:23 AM, Viksit
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) to
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
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
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 dkers...@gmail.com wrote:
Yes, the multiple cursors solution works quite well with the
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 dim...@gmail.com wrote:
Thanks, will keep this in mind. Am I understanding correctly that when B
modifies Y it communicates that change to A through
12 matches
Mail list logo
