Caution, my comments should be taken with a grain of salt. I've build
prototypes with Clara in the browser but nothing of production quality.
Therein could lay dragons... YMWV.
Ryan, Clara's author, uses it much more extensively on servers and such.
His use cases are primarily JVM based but I
On Mon, Apr 20, 2015 at 1:45 PM, Kurt Sys kurt@gmail.com wrote:
The basic stuff I need is really very similar. What I like about react, is
not the dom diffing as such, the 'should-update' mixin. This really can
make things way easier. It doesn't play as nice as I thought it to be
between
Thank you for sharing this Alan! Its really interesting.
Would Clara then work with something like Hipo? I like the distinction you make
between it and mutation based reactions. Very interesting topic that deserves
more discussion imo.
Sent from my iPhone
On Apr 20, 2015, at 2:56 PM, Alan
The basic stuff I need is really very similar. What I like about react, is not
the dom diffing as such, the 'should-update' mixin. This really can make things
way easier. It doesn't play as nice as I thought it to be between rum and
datascript queries, but it'll work. Datascript queries are
Lower level means more possibilities, I suppose :).
Very interesting stuff going on.
Op zondag 19 april 2015 19:31:37 UTC+2 schreef Julien Eluard:
Nice! Let me know if I can help.
Also keep in mind hipo is lower level than those libraries. In particular
there is nothing reactive and the
I had the afterthought that my examples were a bit odd. As far as splitting
with regex is concerned Clojure and Clojurescript behaviour is
significantly different in my experience. In my use case I gave up trying
to find regex patterns that would work for both clj and cljs and started
writing
leiningen clojurescript template descjop version 0.1.1 released today.
descjop is,
A Leiningen template for Web based desktop application with Electron(atom-shell)
lein-template-descjop
https://github.com/karad/lein_template_descjop
clojars
https://clojars.org/descjop/lein-template
changes :
Just tried the beta on our test suite. Aside from warnings from new
Clojure functions now shadowed by existing functions and obvious cases of
hash sensitivity, there are a couple less clear-cut cases (which likely
fall into the above hash case but will require further investigation), and
we
Hi Jamie - thanks for your thoughts.
I don't think this will work as the first time the user makes a
selection the non-default state is the default-state + the user's
selection.
I am also not sure how the component sees the latest set of
default-values, unless default-value is itself a
2015-04-20 6:03 GMT+02:00 Peter Taoussanis ptaoussa...@gmail.com:
This got me wondering: is there an official contract somewhere describing
hash behaviour similarities we _can_ safely depend on?
I don't think there is. IIRC clojurescript _has_ duplicated the recent work
to minimize collisions
The 1.7.0-beta1 release has Reader Conditionals, and apparently the latest
ClojureScript release as well. Wonderful, can't wait to try them out. This
is the beta1 release announcement
https://groups.google.com/forum/#!topic/clojure/7S127m8bLNQ
On Sun, Apr 19, 2015 at 10:19 PM, Daniel Compton
There's no contract, but strings, keywords, and symbols should hash the same,
and collections of these (vectors, lists, maps, sets) should hash the same.
It's difficult to hash numbers the same between Clojure and Clojurescript.
Clojurescript numbers are all doubles (because JS), so they should
When you're writing macros that should emit different code depending on
the language target, you can dispatch on the value of env.
Although, your mention of using cljx makes me think that your scope is
broader than just macros…
- Chas
On 04/19/2015 11:20 AM, Dominykas Mostauskis wrote:
Is
This is an edge case of clojure.string/split with limits and non-consuming
assertions. ^ and $ are fully supported with the meaning of the underlying
regex engine (which may be subtly different in javascript and java).
This is clearly wrong. It occurs because clojure.string/match uses the size
Hi,
This is somewhat reframe specific, but how do people handle default-values that
can change? My specific use-case is that I have a tree which can be expanded
and collapsed. By default the tree should be expanded to a certain level,
however, as soon as the user manually expands or collapses
My first thought is the Component would have local state with your default
value. If a non-default value is passed to your C, then it's used instead.
(or passed-in-value default-value)
The default is clearly based on the data passed into the tree, which agains
suggests a local state. The
16 matches
Mail list logo
