Re: [ClojureScript] Trouble with null values from onKeyPress in React/Om

2015-03-04 Thread Moritz Ulrich
If you log it to the console like this, Chrome (at least) will print it interactively and update it if something changes. React uses a pool of event objects and invalidates (= resets everything to null) as soon as the handler is done. This is also problematic when putting events into a

[ClojureScript] Trouble with null values from onKeyPress in React/Om

2015-03-04 Thread Andrew S
I seem to be having the same problem as this guy: http://stackoverflow.com/questions/22123055/react-keyboard-event-handlers-all-null I need some assistance how to translate this answer into clojurescript. I have an Om component (a dom/input) with this handler: :onKeyPress #(.log

Re: [ClojureScript] Re: IMPORTANT: ClojureScript Firefox Nightly ES6 Issue

2015-03-04 Thread David Nolen
I just cut 0.0-2985. This is only for people who need to and can upgrade to address the FireFox Nightly issue. No release information for this. There's a proper release coming this week or next which will enumerate the changes since 0.0-2913. David On Wed, Mar 4, 2015 at 3:38 AM, Mitchel

[ClojureScript] Re: Trouble with null values from onKeyPress in React/Om

2015-03-04 Thread Andrew S
Turns out that using onKeyDown instead of onKeyPress worked. The React docs suggest they behave the same, but apparently not so (in Chrome at least). -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are

Re: [ClojureScript] Re: ANN: re-frame 0.1.7 Initial Release

2015-03-04 Thread Marc Fawzi
Not defending cursors (I'm new to it all, including ClojureScript), but someone has to play devil's advocate to your devil's advocate :) - their use can sometimes distort the way you structure you data. Cursors want you to layout data hierarchically (which often fine) but one day you'll find

Re: [ClojureScript] Re: ANN: re-frame 0.1.7 Initial Release

2015-03-04 Thread Mike Thompson
On Saturday, February 28, 2015 at 1:44:52 AM UTC+11, Erik Price wrote: On Thu, Feb 26, 2015 at 7:55 PM, Mike Thompson m.l.tho...@gmail.com wrote:  The key thing for me is:  JUST. DON'T. USE. CURSORS. There I said it. They appear convenient, I know. They are a way of achieving reference

[ClojureScript] Re: Why, in principle, can't macros be defined in ClojureScript itself?

2015-03-04 Thread Stuart Sierra
On March 3, 2015, Peter West wrote: Macros eventually all expand to CLJS-compatible code. Currently, IIUC, both macro definition and expansion are handled by the Clojure compiler, with the resulting code (presumably CLJS compatible) being handed back to the ClojureScript compiler. Was this

[ClojureScript] Help using zlib with cljs on node

2015-03-04 Thread mark
New to cljs, and I'm having trouble using the zlib library. (I'm trying to consume events off an aws kinesis stream) I need to gunzip a buffer, and am trying the current code: (.gunzip zlib (js/Buffer. event) (fn [e, res] (if e (throw (js/Error. e))

Re: [ClojureScript] Re: ANN: re-frame 0.1.7 Initial Release

2015-03-04 Thread Daniel Kersten
I've been using Om (and therefore cursors) heavily for almost a year and am finding myself moving further and further away from cursor. The issue for me is absolutely the write-back - allowing your views to write to them encourages your code to do so and encourages a style where your ui/dom event

Re: [ClojureScript] Re: ANN: re-frame 0.1.7 Initial Release

2015-03-04 Thread Daniel Kersten
I do find cursors fantastic for reusable isolated components. For example if I have a widget that edits some data, I find it useful to give that widget a cursor that it may modify, but it needs to be managed by the parent so that what happens to the data is transparent to the widget. The parent

Re: [ClojureScript] Re: ANN: re-frame 0.1.7 Initial Release

2015-03-04 Thread Marc Fawzi
I much rather have unidirectional data flow and have ui/dom events only dispatch messages back. So view model data - ui - messages Ah! Enlightenment. Thank you. On Wed, Mar 4, 2015 at 3:51 PM, Daniel Kersten dkers...@gmail.com wrote: I've been using Om (and therefore cursors) heavily

Re: [ClojureScript] Re: ANN: re-frame 0.1.7 Initial Release

2015-03-04 Thread Marc Fawzi
I understand regarding nested components, makes lots of sense and r/wrap should help, but I've yet to use it personally since I'm just literally starting to write my first Reagent app I think the missing part of the picture you're painting is that components can have specialized instances, so

Re: [ClojureScript] Re: ANN: re-frame 0.1.7 Initial Release

2015-03-04 Thread Marc Fawzi
Writing to cursors from within components (and generally changing app state from within a component) is not a good pattern. You want to have clearly defined places where state mutation can happen, and in the normal case you put those in event handlers (sitting outside the component but being

[ClojureScript] Re: Why, in principle, can't macros be defined in ClojureScript itself?

2015-03-04 Thread Peter West
On Thursday, 5 March 2015 05:31:49 UTC+10, Stuart Sierra wrote: Thanks to all for the replies. Stuart, I wasn't thinking about self-hosting; merely about unifying the experience under Clojure and ClojureScript, wrt macros. Some work has already been done towards this, and I was wondering

Re: [ClojureScript] Re: Example of a working macro?

2015-03-04 Thread Zubair Quraishi
Sure, zubairquraishi.com On Tuesday, March 3, 2015 at 6:42:00 PM UTC+1, marc fawzi wrote: Thank you very much Zubair! Do you have a blog or active twitter? Would love to follow. Sent from my iPhone On Mar 3, 2015, at 8:43 AM, Zubair Quraishi zuba...@gmail.com wrote: There are

Re: [ClojureScript] Re: Example of a working macro?

2015-03-04 Thread Zubair Quraishi
Thanks for the info, I will fix the documentation as soon as possible! On Tuesday, March 3, 2015 at 7:06:13 PM UTC+1, Colin Yates wrote: (by the way, the demo link in the coils repo is dead) On 3 March 2015 at 16:43, Zubair Quraishi zuba...@gmail.com wrote: There are several macros in my

[ClojureScript] Re: IMPORTANT: ClojureScript Firefox Nightly ES6 Issue

2015-03-04 Thread Mitchel Kuijpers
On Tuesday, March 3, 2015 at 11:12:03 PM UTC+1, David Nolen wrote: If you have a ClojureScript based product and your customers use FireFox Nightly you will encounter trouble due to a RegExp detection bug in prior ClojureScript releases interacting with recent Firefox ES6 related changes.