Bumping to Reagent V0.5.0 is in the roadmap but 0.4.2 works well on its own.
We're having this issue when using kioo.
Le mercredi 18 mars 2015 22:22:40 UTC+1, Mike Thompson a écrit :
> On Thursday, March 19, 2015 at 3:01:19 AM UTC+11, Arnaud BOS wrote:
> > I've posted a new issue on kioo's projec
For the record, it's not better with reagent v0.5.0.
--
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 receivin
On Tuesday, 17 March 2015 19:10:51 UTC+1, David Nolen wrote:
> I don't know what else to suggest other than you're going to need to try some
> experiments to figure out what going on, the Clojure REPL you started can
> help you:
>
>
> (System/getProperty "java.class.path")
> (require 'cljs.clo
Still missing critical information like the results of running the
following after starting a _regular_ Clojure REPL with `java -cp cljs.jar
clojure.main`:
(System/getProperty "java.class.path")
(require 'cljs.closure)
On Thu, Mar 19, 2015 at 6:12 AM, Sergi Mansilla
wrote:
> On Tuesday, 17 Marc
> Caused by: java.io.FileNotFoundException: Could not locate
> cljs/closure'__init.class or cljs/closure'.clj on classpath:
Is it possible you are trying (require 'cljs.closure')? That trailing ' should
otherwise not be there. ' means quote in Clojure and is not a String.
--
Note that posts f
Good catch and shame on me for not reading the precise error closely enough
in both cases :)
Yes it look like in both cases you all have written:
(require 'cljs.closure')
which doesn't mean what you think in Clojure, but may seem familiar if
you're used to JavaScript. The right thing is:
(requi
Hi,
I'm creating a component here that will actually render on canvas, to be
more specific I wanna have a tree definition that end's up rendering on
Canvas (kind of the react-canvas project, but on Om, and for other
purposes).
In React is more clear how to write things like this, you can do:
Hi, I asked this before and the short answer is *not* by passing in
realised components in another another component's state as you have
done (which was almost my first attempt).
The consensus was to use multi-methods. If you can't then you pass the
child state and the child fn through to the cont
You might want to check out this article:
https://github.com/Day8/re-frame/wiki/Alternative-dispatch%2C-routing-%26-handling
Using techniques MikeT describes there, it should be possible to slowly migrate
your app to re-frame rather than undertake a rewrite. For instance, it should
be possibl
That was it, solved for me now. Silly that I didn't see it before.
Thanks!
On Thursday, 19 March 2015 12:28:18 UTC+1, David Nolen wrote:
> Good catch and shame on me for not reading the precise error closely enough
> in both cases :)
>
>
> Yes it look like in both cases you all have written:
Thanks for the reply Colin, I did read the entire thread but I'm still
don't have a solution...
My case is a bit different than yours, because yours will just render in
the end, in my case I need to do more manual stuff (for rending on the
canvas context) and I'm trying to rely on the React lifecy
Glad you got it working.
I haven't really got the context to follow (deep in server side event
sourcing ATM) but one tiny tiny point; (-> :a (identity)) is the same
as (-> :a identity) (i.e. for single parameter functions you can just
put their symbol which I think reads nicer). Tiny, as I said :)
Implementing should-update with `(not= old-props new-props)` fixes the issue,
isn't it supposed to be optional?
See this commit:
https://github.com/arnaudbos/kioo-reagent/commit/9eb9b8c145d8354447975f96d3055296a0329d83
I don't get it, is this somehow related to this ? :
https://github.com/reag
I used a channel in the parent. You pass that to the descendants and write to
the channel. The ancestor receives messages via the channel.
On Mar 19, 2015, at 7:53 AM, Wilker wrote:
> Hi,
>
> I'm creating a component here that will actually render on canvas, to be more
> specific I wanna hav
Hi Jamie,
I think the problem with that approach is that we are adding more async
delay into the render process, maybe it add more complications.
In the end here I decided to just go with SVG, it actually suites my needs
pretty well and React/Om can manage it automatically.
On Thu, Mar 19, 2015
I'm reading this now: https://github.com/Day8/re-frame
(so far 30% done with the main Readme) and it appears to be a basic
pattern(s) and reference implementation for using Reagent in line with the
React Flux architecture. true, false or maybe?
I initially resisted the idea because it dumps curso
Ok, putting it on hold, and reading again next week. Till then if anyone
has any thoughts on how it compares to Flux type architectures at the
10,000 foot level, please feel free to enlighten.
Thank youooo
On Thu, Mar 19, 2015 at 12:30 PM, Marc Fawzi wrote:
> I'm reading this now: https://githu
By my understanding, the core pattern is a flux variation. Differences from
Facebook's original flux pattern:
There's only one store and it's a global ratom.
You can compute views from the root store or other derived views using
Reagent's reaction feature.
Your handlers are expected to be wrappe
Mike T is certainly a deep thinker and the contribution is great and
entertaining -- I wish all Readme on github were crafted with such poetic
touch and philosophical rigor
But my gut feeling still on the fence, thinking about how macros work and
if they could be useful here, especially after seei
On Friday, March 20, 2015 at 9:29:44 AM UTC+11, Karl Guertin wrote:
> By my understanding, the core pattern is a flux variation. Differences from
> Facebook's original flux pattern:
>
> There's only one store and it's a global ratom.
>
> You can compute views from the root store or other derived
<<
Looking at re-frame from the Flux perspective is like looking at a cone
from the side elevation and seeing a triangle. The view is only useful up
to a point.
>>
Reminds me of this!
https://johncarlosbaez.wordpress.com/2015/03/17/planets_in_the_4th_dimension/
It's not an ellipse! It's a circl
Now *re-frame* is* "Reactive All The Way Down" ™*
Thanks to some Googling, at least as far as setting focus on rendered
element when they mount and update, we don't have to target the DOM ... I
just couldn't believe that React would not honor the autofocus attribute on
input and textareas..
https
> On 20 Mar 2015, at 11:20 am, Marc Fawzi wrote:
>
>
> Mike T is certainly a deep thinker and the contribution is great and
> entertaining -- I wish all Readme on github were crafted with such poetic
> touch and philosophical rigor
>
> But my gut feeling still on the fence, thinking about ho
that video was an awesome and illustrative counter-example, made me laugh a
lot
given enough free time, people will find new and unexpected ways of using
any given implement
On Thu, Mar 19, 2015 at 9:22 PM, Peter B. West
wrote:
> > On 20 Mar 2015, at 11:20 am, Marc Fawzi wrote:
> >
> >
> > Mik
24 matches
Mail list logo
