Java Listener on Textfield

Hellow everybody, Somebody please tell me how to trigger the right Event listener to a text field in java In the example below all components modify their corresponding panel's background color including the text field the latter do this streatement by writing the color among five colors,my

About transients no longer being safe in 1.7-alpha2

Hi, I just want to address this issue (CLJ-1498 ). It was accepted in 1.7-alpha2 and I haven't seen a lot of discussion around it, even though it's quite a big change. With this change the following code is possible: (let [m (transient {:a 0})

Introducing Boot v2 with a streamlined CLJS workflow

Hi! Boot (http://github.com/boot-clj/boot) is a build tool for Clojure. We've pulled together lessons learned from a year or so using boot v1 in production and are now getting ready to release v2. To show what boot can do we present a very streamlined and awesome boot-based ClojureScript devel

Re: Java Listener on Textfield

Hi, not directly an answer to your question, but you may be interested in Seesaw and it binding facilities. Unless you are looking for pure Java solutions in which case your posting in the wrong group. Kind regards, stefan On Monday, November 3, 2014 1:52:46 PM UTC+1, Azzoug Youcef wrote: > >

Re: Introducing Boot v2 with a streamlined CLJS workflow

Tongue in cheek question: if Leiningen were the maven of clojure, would you say boot2 is gradle ? :-) Le lundi 3 novembre 2014, Micha Niskin a écrit : > Hi! > > Boot (http://github.com/boot-clj/boot) is a build tool for Clojure. We've > pulled together lessons learned from a year or so using boo

Re: Introducing Boot v2 with a streamlined CLJS workflow

And more seriously, I remember reading that you put an emphasis on removing the need to use a clean task. If I'm right, then I'd be interested in knowing how one is encouraged / helped to pursue this good property in its own tasks ? Le lundi 3 novembre 2014, Laurent PETIT a écrit : > Tongue in c

Clojure usage in production - survey on Hacker News (Nov 2014)

Hello all, I was curious about the state of Clojure in production, and put up this thread on Hacker News asking for insight, since all the other threads are quite dated. https://news.ycombinator.com/item?id=8549823 Given the large amount of feedback that's already on it, I thought I'd cross

Re: Clojure usage in production - survey on Hacker News (Nov 2014)

I'm really entertained that pivotal labs made that list, as I wrote that code (and that blog post) and "production" is stretching definitions pretty far sadly. On Mon, Nov 3, 2014 at 4:55 PM, viksit wrote: > Hello all, > I was curious about the state of Clojure in production, and put up this

Re: Clojure usage in production - survey on Hacker News (Nov 2014)

Ashton - perhaps you should elucidate on matters on that thread :) And why do you say "stretching" definitions? On Monday, November 3, 2014 4:03:36 PM UTC-8, Ashton Kemerling wrote: > > I'm really entertained that pivotal labs made that list, as I wrote that > code (and that blog post) and "pr

Re: Clojure usage in production - survey on Hacker News (Nov 2014)

I was mostly trying to include interesting companies using it for something. Sorry if I overstepped! :) On Monday, November 3, 2014 6:27:41 PM UTC-6, viksit wrote: > > > Ashton - perhaps you should elucidate on matters on that thread :) And why > do you say "stretching" definitions? > > > On Mon

Re: Clojure usage in production - survey on Hacker News (Nov 2014)

We aren't secretive about our usage of it, but it's used for testing only. It doesn't get shipped to any server, hence why production is a stretch. On Mon, Nov 3, 2014 at 5:57 PM, Alex Miller wrote: > I was mostly trying to include interesting companies using it for > something. Sorry if I ove

Garden defcssfn not rendering

I'm having an issue generating a CSS function (for the scale() transform function) using Garden's *defcssfn *macro. The macro appears to generate the Garden CSSFunction record fine, but the (css) call returns an empty string. (defcssfn scale ([a] [a a]) ([x y] [x y])) (scale 2) ;; #garden

Re: Deterministic Randomness in Functional Clojure

It might also be worth noting that the JDK ships with java.security.SecureRandom a subclass of java.util.Random. http://docs.oracle.com/javase/8/docs/api/java/security/SecureRandom.html R. On 1 Nov 2014, at 10:31, Mars0i wrote: > > > On Friday, October 31, 2014 11:19:19 PM UTC-5, Isaac

OJ - A friendly way to talk to your database using Clojure.

GitHub project link: https://github.com/taylorlapeyre/oj The idea is to lay a solid foundation for talking to databases in Clojure using regular Clojure data structures to represent queries. My goal is to let this library become established enough that is becomes the foundation for larger fra

Re: About transients no longer being safe in 1.7-alpha2

On Mon, Nov 3, 2014 at 5:57 PM, Daniel Marjenburgh wrote: > Hi, > > I just want to address this issue (CLJ-1498 > ). It was accepted in > 1.7-alpha2 and I haven't seen a lot of discussion around it, even though > it's quite a big change. > > With this

Re: About transients no longer being safe in 1.7-alpha2

On Monday, November 3, 2014 9:00:10 PM UTC-6, Atamert Ölçgen wrote: > > > > On Mon, Nov 3, 2014 at 5:57 PM, Daniel Marjenburgh > wrote: > >> Hi, >> >> I just want to address this issue (CLJ-1498 >> ). It was accepted in >> 1.7-alpha2 and I haven't s

Re: About transients no longer being safe in 1.7-alpha2

Thanks Alex! Now that I took a second look at Daniel's code, it seems assoc! is used like swap!, as if it would modify m in place. So I would expect, if it runs without errors, result to be {:a 0}. Given that transients are values (not reference types like ref or atom) I can't think of a case whe

Re: About transients no longer being safe in 1.7-alpha2

On Monday, November 3, 2014 10:44:19 PM UTC-6, Atamert Ölçgen wrote: > > Thanks Alex! > > Now that I took a second look at Daniel's code, it seems assoc! is used > like swap!, as if it would modify m in place. So I would expect, if it runs > without errors, result to be {:a 0}. > Right, that i

Re: About transients no longer being safe in 1.7-alpha2

Hi Alex. I know transients aren't bash-in-place, as they may return new references, but that is not the problem I'm having here. If you bash in place, you would get unexpected results, but still the same result every time. The problem here is that the 'value' of the transient is changing undern

Re: About transients no longer being safe in 1.7-alpha2

I was a bit too quick there and posted some errors int he code: (let [v (transient {:a 0}) f1 (future (reduce #(assoc! % (+ (:a %) %2)) v (range 10))) f2 (future (reduce #(assoc! % (+ (:a %) %2)) v (range 10)))] @f1 @f2 ; wait for futures (persistent! @f1)) >>> -- You receive

Re: About transients no longer being safe in 1.7-alpha2

FWIW I can confirm the following code produces {:a 90} consistently: (let [v (transient {:a 0}) f1 (delay (reduce #(assoc! % :a (+ (:a %) %2)) v (range 10))) f2 (delay (reduce #(assoc! % :a (+ (:a %) %2)) v (range 10)))] @f1 @f2 ; wait for futures (persistent! @f1)) Note that the

Re: About transients no longer being safe in 1.7-alpha2

On Nov 3, 2014, at 11:13 PM, Daniel Marjenburgh wrote: > I was a bit too quick there and posted some errors int he code: That’s still not quite right. I think you mean: (let [v (transient {:a 0}) f1 (future (reduce #(assoc! % :a (+ (:a %) %2)) v (range 10))) f2 (future (reduce #(asso