On Wed, Apr 2, 2014 at 3:42 AM, rlewczuk wrote:
>
> First one is about object created by (om/build ...) - in all tutorials
> these objects are always created on the fly in (render ...) functions. So
> if some component disappears from view for some time, it loses its state.
> This might be the ca
Hi,
Thank you for all answers, as I did my homework (reading overview sent by
Jeff and applying Luca's suggestions), things have improved quite a bit.
Yet there are still some things I'm not fully grasping, so I have more
questions :)
First one is about object created by (om/build ...) - in a
Hi Rle,
I'm a clojurescript / om newbie too. I'll try to answer to the best of my
knowledge and maybe someone else can improve this first guess.
Il giorno giovedì 27 marzo 2014 09:20:41 UTC+1, rlewczuk ha scritto:
>
> Hi,
>
> After playing a bit with om, I'm somewhat confused about state maintai
There is some explanation about component local state in the documentation
here:
https://github.com/swannodette/om/wiki/Conceptual-overview
UI components will often have transient state that really doesn't make
sense to expose externally. For example the characters in an input as
someone is t
Hi,
After playing a bit with om, I'm somewhat confused about state maintaining
possibilities it offers. There is global application state and local
component state. I have some doubts about using local state as it seems to
lead to troubles as soon as code grows a bit (I'm thinking about
trad
