the quick-start uses the cljs 1.7.48 jar. 1.7.48 had a windows regression,
which was fixed in 1.7.58 ( see:
https://github.com/clojure/clojurescript/releases ). i'm guessing that's what's
causing this error.
w/ mies, you could probably try bumping cljs up to 1.7.58 (or even 1.7.107).
for the q
On Monday, May 25, 2015 at 4:32:37 PM UTC-5, Colin Yates wrote:
> Hi all,
>
> (UUID. "214ecb53-2815-492a-aa11-209843bef82a") gives "WARNING: Wrong number
> of args (1) passed to UUID at line 1 "
>
> What's the correct usage?
>
> Thanks!
pretty sure that's the correct usage. works for me at the
mies is out of date and uses an old version of cljs and clojure 1.6. lein
ancient doesn't upgrade clojure unless you use the :check-clojure option. so it
upgrades cljs to 3269, but leaves clojure at 1.6.0, and that won't fly.
On Tuesday, May 12, 2015 at 9:05:22 AM UTC-5, g vim wrote:
> lein mie
On Wednesday, December 31, 2014 5:47:09 AM UTC-6, Andrew wrote:
> As a followup to this, I'm trying to understand why line 70 prints "not
> found":
>
> https://www.refheap.com/95618#L-70
>
> I am trying to understand the various mechanisms that go into drag and drop
> and am loosely following t
Maps aren't comparable, so they don't make sense with sorted-set. This is
not a bug.
On Dec 25, 2014 12:25 PM, "Sven Richter" wrote:
> Hi,
>
> while I was preparing the bug report Captaion Obvious hit me again. This
> also occurs in clojure:
>
> As Thomas said, this is enough to reproduce it:
>
>
14 11:15:00 AM UTC-6, David Mohl wrote:
> Hey Jack,
>
>
>
>
> here are 2 specific examples taken from my codebase. One inside a render, one
> inside a will-mount: https://www.refheap.com/fec9b8d2d50ce755214817b21
>
>
>
>
> In both cases, if I use update! inst
om/build expects a map for its third argument. your code should work if you
replace (om/build child app owner) with (om/build child app).
On Thursday, December 11, 2014 6:39:24 PM UTC-6, Bob Erb wrote:
> I'm having trouble building Om components that consist of other Om
> components. I can't fig
The best way to get help with this is to post (gist, refheap, or similar) a
complete but minimal case that demonstrates the issue. Here's an example that
you may find helpful that includes (a contrived use of) build-all, opts, and
render-state: https://www.refheap.com/94767
On Thursday, Decemb
The quiescent readme provides a lot of specific information about the
comparison:
https://github.com/levand/quiescent#comparison-with-om
FWIW, I'd encourage you to make the investment and learn Om. It doesn't take
long before the stuff that you're not understanding at first glance seems
trivia
i can't reproduce this. can you post a minimal case showing an example where
transact! succeeds and update! fails?
https://www.refheap.com/94143
On Friday, November 28, 2014 3:28:25 AM UTC-6, David Mohl wrote:
> Hey there. I am constantly running into a small issue with om/update! and
> om/tr
challenge.
>
> The approach, if I may generalise is by all means project off app-state but
> keep it alongside (e.g. through opts as you show), rather than intermingled
> with?
>
> Essentially, it all went wrong when I mutated the cursor itself.
>
> Thanks James,
>
I don't think this is a bug. When you deref a cursor, you get the values stored
in the underlying app-state atom. Here, you're storing a cursor in a
component's local state. When you deref it later, you're still only going to
get the values stored the the cursor's underlying app-state atom...
On Monday, November 3, 2014 3:53:45 AM UTC-6, Colin Yates wrote:
> The performance problem was due to me incorrectly mutating the data to the
> component. Rather than:
>
> (om/build-all child-component (map (fn [child] (assoc child :selected? (=
> (:id child) selected-id) :selected-row-fn (fn [p
It's very complicated, but I don't think it needs to be. You're using channels
and ref-cursors in ways that introduce complexity without any benefit that i
can see. For your purposes, I think it's a lot simpler without either:
https://www.refheap.com/92626
Or maybe i'm overlooking something?
On Sunday, November 2, 2014 10:47:13 AM UTC-6, Colin Yates wrote:
> (om newbie, but getting less so :))
>
> [overhead]
> Is there any overhead for a react component at runtime? If I have a single
> component which emits a bunch of , is there any cost to having each
> be an instance of a compone
On Sunday, November 2, 2014 10:47:13 AM UTC-6, Colin Yates wrote:
> (om newbie, but getting less so :))
>
> [overhead]
> Is there any overhead for a react component at runtime? If I have a single
> component which emits a bunch of , is there any cost to having each
> be an instance of a compone
On Saturday, September 13, 2014 8:58:38 AM UTC-5, Brian Gaines wrote:
> I have noticed you have posted updates since this thread died, but I didn't
> see the feature added. Are you still working on it, or is there another
> method preferred for handling this issue, or have I overlooked it in one
On Thursday, September 4, 2014 9:50:41 PM UTC-5, Tom George wrote:
> Hi,
>
> I'm doing my first real work in clojurescript/om. I have a little web
> service that queries a database and returns a JSON message of all known
> schema owners. I want to use this data source to populate a dropdown.
>
On Sunday, August 17, 2014 3:22:53 PM UTC-5, Ryan Waters wrote:
> The following does not render a vector of numbers like I would expect - what
> (assuredly) simple thing am I missing?
>
> Thank you.
>
> ;;
>
>
>
>
> (def
On Sunday, August 17, 2014 3:22:53 PM UTC-5, Ryan Waters wrote:
> The following does not render a vector of numbers like I would expect - what
> (assuredly) simple thing am I missing?
>
> Thank you.
>
> ;;
>
>
>
>
> (def
The compiled output size for samples/hello project has increased since I last
played around clojurescript. It's currently 62k with advanced compilation,
without gzip. I ran a git bisect and found that the following commit bloated
the hello world file size from 14k to 56k:
commit 29c8597a2c818fb
ys on getting something going
> and then we can compare notes!
>
> The big question for me has always been how to deal with the add/remove item
> from a list enter/exit animation that Jack is talking about.
>
> Ideally animation could shouldn't pollute your application,
HI Daniel,
Apologies in advance for the probably stupid question:
My main use case is to animate elements as they enter and leave the Dom.
Something similar to the way that CSSTransitionGroups work, but hopefully with
more of the power you are providing with the easing functions and timing
mec
Very cool. I tried to use the CSSTransitionGroup on Goya, but it left a bit to
be desired. I'm going to try incorporating this tonight!
On Sunday, May 4, 2014 2:48:37 PM UTC+2, Daniel Kersten wrote:
> Just pushed an update which adds the ability to watch app-state changes to
> trigger animation
My feeling is that your app-state atom should contain everything that would be
saved into a document if your user did a File->Save in a conventional desktop
application. Given that, it wouldn't seem appropriate to put things like
channels or flags for tracking mouse/hover state and that sort of
My feeling is that your app-state atom should contain everything that would be
saved into a document if your user did a File->Save in a conventional desktop
application. Given that, it wouldn't seem appropriate to put things like
channels or flags for tracking mouse/hover state and that sort of
No problem. If you'd like me to test any changes, just let me know!
On Monday, April 28, 2014 9:46:38 PM UTC+2, David Nolen wrote:
> Thanks for the report! This seems like a bug, I went ahead and filed an issue
> for it.
>
>
> David
>
>
>
> On Mon, Apr 28,
0.6.2 seems to work great! I did have one issue with the tx-listen mechanism. I
have a bunch of root components, and had to move the registration of the
tx-listen function to the first call to om/root. Otherwise, the tx-listen
function would not get called. I noticed that there was a bug-fix com
iteup.
Glad to hear that you don't find the multiple roots too nasty. I was tempted to
switch to a single root which passes cursor(s) to all of the child components,
but the multiple roots approach is quite handy!
Best,
-jack
On Thursday, April 17, 2014 5:12:04 PM UTC+2, David Nolen wrote
ter coming from
imperative/PLOP land. I finally feel like I'm not building a pyramid anymore ;)
Thanks for linking from the Om readme! That's good motivation for me to clean
up some of my messy code.
Best,
-jack
On Thursday, April 17, 2014 3:07:31 PM UTC+2, David Nolen wrote:
> Wo
there for public critique as the whole thing is meant to be a learning
exercise. Any and all advice or criticism is welcomed!
Best,
Hopefully the code doesn't make your eyes bleed,
-jack
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You
Does it make any sense to allow components to reference multiple cursors?
Instead of specifying a single path into the application state, you would
specify a collection of paths within the state atom, all of which would trigger
re-renders and allow for transact! and update!? I often find myself
-enter-active {
opacity: 1;
}
.example-leave {
opacity: 1;
transition: opacity .5s ease-in;
}
.example-leave.example-leave-active {
opacity: 0.01;
}
Best,
-jack
On Saturday, March 15, 2014 5:20:07 PM UTC+1, David Nolen wrote:
> Several people have successfully used the CSS transit
le within Om? Sorry in advance for the
probably silly question!
-jack
On Saturday, March 8, 2014 3:08:52 AM UTC+1, David Nolen wrote:
> I would probably do this by hooking into IWillUpdate. Generally whatever
> solution makes sense for React will make sense for Om.
>
>
> David
34 matches
Mail list logo
