Yeah it seemed like Google wasn't too committed to open source Closure but I
hope the move to github changes that a bit. Also seemed like they forgot to
publish the docs but they are just hidden really well with no public mirror I
could find.
Hi All,
I just wrote a blog post for beginner CLJS developers (like me) which
illustrates a typical REPL session complete with many of the initial mistakes
that I made in the hopes that anyone new to ClojureScript REPL development may
avoid the same pitfalls.
Hi Alex,
I like it!
One thing worth considering is `deref`ing the `app-state` atom in lieu of
letting the #Atom ... representation print. Maybe just slap an `@` on front
without explaining atoms in depth?
- Mike
On Apr 5, 2015, at 7:00 PM, Alex Eberts alex.ebe...@gmail.com wrote:
Hi
On Monday, April 6, 2015 at 12:11:28 AM UTC+2, Shaun Mahood wrote:
Thomas, have you got any good resources for working with Closure in Cljs?
I've tried to figure it out and read a decent amount but have found it
difficult to get the hang of.
Apart from the docs I linked not really. The demos
Hi Mike,
Thanks for the feedback! Good suggestion re: @. I'm inclined to add a small
section rather than simplifying the whole thing as I think there are some
useful mistakes to learn from in the longer explanation.
I realize the post is probably way too long already - I was only intending it
On 6 Apr 2015, at 9:38 am, Alex Eberts alex.ebe...@gmail.com wrote:
Hi Mike,
Thanks for the feedback! Good suggestion re: @. I'm inclined to add a small
section rather than simplifying the whole thing as I think there are some
useful mistakes to learn from in the longer explanation.
Thomas, have you got any good resources for working with Closure in Cljs? I've
tried to figure it out and read a decent amount but have found it difficult to
get the hang of.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this
On Saturday, April 4, 2015 at 7:10:00 AM UTC+3, Mike Thompson wrote:
So the problem sequence would be:
1. first event handler called with db snapshot
2. sync-dispatch called, making changes to app-db
3. first event handler finishes, and the value it returns is written into
Hey Tim,
I have no real feedback for you since I don't use Reagent or Om but thought I
should mention that it might be better to leverage what the Closure Library has
to offer before grabbing external Javascript.
The Closure Library comes with a full fledged DatePicker that is fully
On Sunday, April 5, 2015 at 9:13:57 PM UTC+10, whodidthis wrote:
On Saturday, April 4, 2015 at 7:10:00 AM UTC+3, Mike Thompson wrote:
So the problem sequence would be:
1. first event handler called with db snapshot
2. sync-dispatch called, making changes to app-db
3. first
On Saturday, April 4, 2015 at 9:38:11 PM UTC+3, whodidthis wrote:
Yes you will lose everything if you change input value through dispatch as it
is asynchronous. Something synchronous like a local atom will work though. As
does re-frames app-db.
Basically you need something like
Hi Thomas, thanks for the feedback!
The goog.* libraries are still a bit of a black box to me, but you're right, I
should look into them more since they don't introduce an external dependency
and are built right into the Closure compiler.
On a more philosophical level, I'm not totally crazy
12 matches
Mail list logo
