om: state management considerations

2014-03-27 Thread rlewczuk
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

Re: om: state management considerations

2014-04-02 Thread rlewczuk
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

[ANN] clj-cursor 0.0.1 - server-side cursor for clojure data structures (inspired by om)

2014-04-13 Thread rlewczuk
Hi, https://github.com/rlewczuk/clj-cursor This is my attempt at (properly) managing application state. It is based on David Nolen's cursor concept implemented in the om library. Cursor allows storing whole application state in a single structure, yet still be able to swap under

Re: [ANN] clj-cursor 0.0.1 - server-side cursor for clojure data structures (inspired by om)

2014-04-13 Thread rlewczuk
Also as I have relatively little experience with Clojure programming, any suggestions about style, non-idiomatic code etc. are also important for me. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@goog