Hi All
Is anybody using a list recently used memorise function in clojurescript?
I just tried https://github.com/clojure/core.memoize but without success - I'm
fairly sure it doesn't work for clojurescript but I'd like to be wrong.
Perhaps there are alternatives I'm missing.
cheers, Oliver
Let's go with `data` then. I posted the rewrite to Figwheel. Please take a
look.
https://github.com/swannodette/om/wiki/Basic-Tutorial
On Monday, February 2, 2015 at 2:02:35 PM UTC+1, Dan Kersten wrote:
I personally like data. om-tools also calls it data.
On 2 February 2015 at 12:55,
So to summarize:
1. There is no need to fork React now or in the future because React is a
library specified for one purpose, not a framework that can get bloated
over time.
2. Relay is both interesting and useful
3. Scenarios where Relay would be counter productive? I mentioned one, and
if
Brendan makes some good points. Obviously I have a strong preference for
Clojurescript (and this IS a CLJS list), but my intention was not to promote
exceptionalism and I apologize if it came across that way.
I have always viewed the relationship between React and Clojurescript as
symbiotic
Just pushed out 0.0-2758. The only change was a fix for the macro usage
enhancement.
On Sun, Feb 1, 2015 at 5:38 PM, David Nolen dnolen.li...@gmail.com wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code:
I personally like data. om-tools also calls it data.
On 2 February 2015 at 12:55, Khalid Jebbari khalid.jebb...@gmail.com
wrote:
Indeed, data is better than app.
Khalid aka DjebbZ
@Dj3bbZ
On Mon, Feb 2, 2015 at 10:49 AM, Sebastian Bensusan sbe...@gmail.com
wrote:
Thanks Khalid,
The
David Nolen dnolen.li...@gmail.com writes:
I fixed this in ClojureScript master. The fix will appear in the next
release.
The original 'No such namespace: cljsjs.react' error? I still see this
with 0.0-2755 (and with a build from current master). Happens with
piggieback standalone
Indeed, data is better than app.
Khalid aka DjebbZ
@Dj3bbZ
On Mon, Feb 2, 2015 at 10:49 AM, Sebastian Bensusan sbe...@gmail.com
wrote:
Thanks Khalid,
The way I see it, Om has three concepts regarding state:
1. The global state defined with atom. Named `app-state`
2. The cursor passed to
Weasel and piggieback likely need to be changed to load foreign
dependencies.
David
On Mon, Feb 2, 2015 at 9:06 AM, Moritz Ulrich mor...@tarn-vedra.de wrote:
David Nolen dnolen.li...@gmail.com writes:
I fixed this in ClojureScript master. The fix will appear in the next
release.
The
Thanks Khalid,
The way I see it, Om has three concepts regarding state:
1. The global state defined with atom. Named `app-state`
2. The cursor passed to each component with the relevant parts of the
global state. Named `app`
3. Local state of each component, initialized in `IInitState` and
1. There is no need to fork React now or in the future because React is a
library specified for one purpose, not a framework that can get bloated over
time.
Now - I don't see any benefit that would justify that.
Future - Who knows? I never claimed to have a crystal ball. My 2 cents is
Is there anything similar to TodoMVC that compares the different approaches to
using React from CLJS?
I think if there was then comparing and contrasting would be a great way for
some of us to learn the pros and cons of each and maybe et us thinking...
--
Note that posts from new members are
And just pushed out 0.0-2760 which catches a ns spec parsing regression
caught by some helpful people in the ClojureScript IRC channel.
David
On Mon, Feb 2, 2015 at 9:22 AM, David Nolen dnolen.li...@gmail.com wrote:
Just pushed out 0.0-2758. The only change was a fix for the macro usage
Hello.
Probably this question was answered elsewhere but I could not find it myself.
The question is about minimal compiled output size. I am trying to use
ClojureScript for a project that needs only small pieces of javascript (at
least currently) but I noticed that even one-liner with
Do you have some advice on how to narrow it down? Some kind of debug flags?
It's a 30+ files project [1], not sure where to start producing this minimal
example :(
FYI, in case it helps: now with 0.0-2760 the same source code produces
java.lang.StackOverflowError:
I don't have any advice. There needs to be minimal reproducer or there's
not much that can be done.
As to the earlier problem that code path should only be taken if :nodejs
target is somehow being set. If you're not setting this yourself are you
sure that something else isn't? Note that Node.js
I think everyone here agrees w your last point! I think making Relay more
efficiently or more easily usable in CLJS is what DN was talking about, if I'm
not mistaken.
Would love to give it a try. Seems like it could fit naturally with something
like Regent... But too early for me to tell as
17 matches
Mail list logo
