I look forward to further understanding from my mistakes :)
Thank you.
ClojureScript+Reagent combination is a whole new level of thinking.
Absolutely convinced there is something big happening here with front end
development.
On Wed, Jan 28, 2015 at 2:29 PM, Mike Haney wrote:
> Don't be embarr
Don't be embarrassed- even if you think it's over engineered or won't work out
or whatever, you still tried something different - that's more than 90% of
people can say. I've been curious about your approach since you first
mentioned it, even though I wondered about its feasibility. I'm glad y
If your component is conditionally (based on the state being deleted)
rendered, then it will be unmounted and then remounted when recreated.
If the component is not conditionally rendered, then it will simply receive
nil as it's cursor value.
On Wed, 28 Jan 2015 14:51 Colin Yates wrote:
> I am n
So I was supposed to have done this one the weekend but my 20 month old baby
girl objected.
I've finally managed to clean up the project and comments so that it is
understandable to others.
It's a learning project that has taught me:
1) the importance of Real FP (as opposed to sprinkling FP p
So I was supposed to have done this one the weekend but my 20 month old
baby girl objected.
I've finally managed to clean up the project and comments so that it is
understandable to others.
It's a learning project that has taught me:
1) the importance of Real FP (as opposed to sprinkling FP patt
A lazy-seq is not an associative datastructure.
Again, what you could do is pass the entire boards structure along with an
index to the child components:
;; For example
(om/build a-child {:boards (:boards cursor), :index 0})
;; a-child could look like
(defn a-child [{:keys [boards index]} owne
Yes that's a fine idea and pattern core.async was designed to support by
not baking in a default error handling strategy.
David
On Wed, Jan 28, 2015 at 11:23 AM, Stefano Pugnetti <
stefano.pugne...@gmail.com> wrote:
> Hi!
>
> I'm looking for a best practice for handling exceptions thrown in
> as
Perfect, this is what I've been waiting for. Great to see that Windows bugs
are getting fixed.
On Wednesday, January 28, 2015 at 2:54:42 PM UTC+1, David Nolen wrote:
>
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/c
Hi!
I'm looking for a best practice for handling exceptions thrown in asynchronous
components of my code. I've found David Nolen's blog post:
http://swannodette.github.io/2013/08/31/asynchronous-error-handling/ ,
and his ! error-ch (add-some-details err)))
(let [ech (chan 1)]
(start-my-nev
Hi Olav,
Following the Basic tutorial for the latest om-tut (0.8.4) I see live
updates work via swap! on OSX. Could you be more specific about your
platform and the exact steps you've done on the tutorial? While there are
some console warnings on initial eval, live updates work for an external
b
I run "lein quickie" to run all the Clojure tests and "lein cljsbuild auto
unit-tests" for all the ClojureScript tests.
I prefer this over running individual tests for the following reasons:
- I use cljx so this is easier than running the same clj/cljs test separately
- it prevents a *lot* of b
Thanks David,
Regards,
Kashyap
On Wed, Jan 28, 2015 at 5:14 PM, David Nolen wrote:
> You will need an externs file if you want a production build. Depending on
> what type of game you want to build you may want to adopt a lower level
> ClojureScript style or mix and match Closure compatible Java
It will not, but you don't need it on Node.js.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
To unsubscribe from this group and stop receiving emai
I think the most lacking chunk of mind-share is "how do all these bits fit
together" which a single app/documentation of steps would address quite nicely.
I wouldn't worry about X v Y though - everybody has their own criteria. The
same non-trivial app implemented in a number of ways/toolkits wou
I came up with a compromise I think will work well. I'm going to simplify the
app a bit, remove proprietary parts, and then release the whole app as an
example. Then I'll use it as a basis for a series of tutorials for exploring
more advanced options.
--
Note that posts from new members are
I am not sure of the exact interaction between om and react (other than om
implements react's lifecycle for performance enhancements), but two things
occur:
- this sounds like a loaded question - are you seeing some surprising
behaviour?
- "deleted and then reinserted" isn't part of om's life
Thanks David, the Windows love is much much appreciated.
On Wednesday, January 28, 2015 at 8:54:42 AM UTC-5, David Nolen wrote:
>
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
> New release version: 0
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2740
Leiningen dependency information:
[org.clojure/clojurescript "0.0-2740"]
The primary reason for this release is to bring all
I am building an application in Om and wanted to know what happens to an Om
component when the global state containing the Om Component's part of the UI
tree is deleted and then reinserted. Is the Om component garbage collected and
then recreated automatically, or should the component be destroy
You will need an externs file if you want a production build. Depending on
what type of game you want to build you may want to adopt a lower level
ClojureScript style or mix and match Closure compatible JavaScript with
ClojureScript.
David
On Wed, Jan 28, 2015 at 12:33 AM, C K Kashyap wrote:
>
As per the docs "everything in the atom should be associative data structure"
can we not have lazy-seq as elements of a vector .
My state is similar to below
(def state (atom {:boards [lazy-seq-0 lazy-seq-1 lazy-seq-2] }))
The root component uses :boards and each child of the root uses elements
21 matches
Mail list logo
