I'm interested in this thread, it does seem however that DerbyJS is farther
ahead in this type of work though. I was looking for a similar JVM stack,
but not sure how to put it together as well. Atmosphere seems like it fits
for the basic communication even including pubsub. Derby updates the v
Hi,
I'm mainly an Angular dev that's been playing around with Om. I decided to make
a test application, one that included editing, a recursive tree, filtering and
adding items, to see how Om worked. I just finished updating the app to 0.5.0
and was hoping to get some insight on how functional
I got the 'advanced' mode working for a simple hello world
Your question prompted me to go back and update to the latest versions of
everything
so you can see it at
https://github.com/vladp/cljs_om_dojo/
I suspect in advanced mode the including of reactjs needed to be different.
But not 100% sure
Excellent!
On Sat, Feb 22, 2014 at 8:55 PM, Joel Holdbrooks wrote:
> Ankha is a generic data inspector for use with Om. You can use it to
> interactively view your application's state or any other supported data
> structure (see README).
>
> Learn more here: https://github.com/noprompt/ankha
>
>
Ankha is a generic data inspector for use with Om. You can use it to
interactively view your application's state or any other supported data
structure (see README).
Learn more here: https://github.com/noprompt/ankha
Comments, suggestions, and patches welcome. Expect more features to come.
--
Would that still work with advanced compilation? I can't quite recall if
you-app.core/start would be renamed by Google closure compiler?
--
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 G
What about providing a your-app.core/start-application which takes a
edn-string as a parameter, then adding a
I have a setup that 'posts' for some EDN data on the server in order to update
an OM component.
That works fine, but I want to avoid an extra 'post' on the initial page load
and rather dump the starting state with the primary browser request (i.e. just
output the EDN string somewhere on the pa
Likely a core.async bug.
David
On Fri, Feb 21, 2014 at 8:57 PM, Kevin Marolt wrote:
> On a (possibly) related note:
>
> The #js data literal doesn't seem to work correctly
> inside the go macro as well: Compiling
>
> (go (prn (
> produces
>
> "WARNING: Use of undeclared Var /bar ..."
>
On a (possibly) related note:
The #js data literal doesn't seem to work correctly
inside the go macro as well: Compiling
(go (prn (/bar ..."
and prints out
"#js {:foo nil}"
if /bar is nil.
Of course,
(go (prn ( I'm building utility macro to convert sequence of functions into java
The #js tagged literal, like all reader macros (@, ~, ~@, #, etc) are resolved
at read-time, which is before the macro runs and doesn't happen again
afterwards for the macro-expanded code.
Reader forms are for syntactic convenience, so if you have a situation where
you want a JavaScript object
Reagent is now at 0.4.1, with support for ClojureScript 0.0-2173.
Reagent's atom now implements the necessary IAtom, ISwap and IReset protocols.
Reagent should still be compatible with older ClojureScript versions, but you
will get a lot of compilation warnings.
/dan
On 21 feb 2014, at 16:57
12 matches
Mail list logo
