I'm happy to announce the release of Om 0.8.0-alpha1. This release
includes the single biggest conceptual enhancement since its initial
release - Reference Cursors.
As we begin to build larger and larger applications with Om, we
often run afoul of the need to organize our application around a
Boguta and David Nolen, and honorary
studiomates Brandon Bloom and David Lansdowne, for their invaluable advice
and support. We're especially fortunate to have attracted the attention of
Joseph Parker, who has been building amazing things with Arcadia since it
was a sloppy hack hidden on Github
File a bug in JIRA, thanks! http://dev.clojure.org/jira/browse/ASYNC
David
On Sun, Oct 12, 2014 at 5:56 AM, Tom Coupland tcoupl...@gmail.com wrote:
I've been seeing this weird looping behavior with some go loops over the
last few days. An exception is being thrown from a function within the
You can set explicit JVM memory settings. I'm also not convinced that
Chestnut's strategy of triggering CLJS compilation on (run) is a good
one. In anycase Chestnut's Github Issues is the right place to bring
this up.
David
On Mon, Oct 13, 2014 at 2:19 PM, gvim gvi...@gmail.com wrote:
I've just
As already mentioned use identical? In ClojureScript you must use
keyword-identical? for fast comparisons.
On Friday, October 10, 2014, Jony Hudson jonyepsi...@gmail.com wrote:
Hi All,
I've been optimising a piece of code lately, and have come to wonder
about the performance of keyword
?
On 12 October 2014 02:25, David Nolen dnolen.li...@gmail.com
javascript:_e(%7B%7D,'cvml','dnolen.li...@gmail.com'); wrote:
As already mentioned use identical? In ClojureScript you must use
keyword-identical? for fast comparisons.
On Friday, October 10, 2014, Jony Hudson jonyepsi
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2371
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2371]
This release includes minor fixes, faster collection
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2356
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2356]
### Fixes
* fix var analysis so that some.ns/foo.bar
UTC+10, David Nolen wrote:
I just cut 0.0-2342, the only change is a updated dependency on
tools.reader 0.8.9 - this fixes an issue where source metadata would
leave into the runtime.
David
On Thu, Sep 18, 2014 at 8:23 AM, David Nolen dnolen...@gmail.com
wrote:
ClojureScript, the Clojure
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2341
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2341]
This releases comes with considerably better
I just cut 0.0-2342, the only change is a updated dependency on
tools.reader 0.8.9 - this fixes an issue where source metadata would
leave into the runtime.
David
On Thu, Sep 18, 2014 at 8:23 AM, David Nolen dnolen.li...@gmail.com wrote:
ClojureScript, the Clojure compiler that emits JavaScript
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2322
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2322]
The primary reason for this release is a critical
Any such facility is at odds with Google Closure Compiler's advanced
compilation.
David
On Mon, Aug 25, 2014 at 11:59 AM, Timur timurha...@gmail.com wrote:
Hi everybody,
Is there a way to resolve a function or object using its string name in
ClojureScript? I found this however it is old:
Amazing work!
David
On Wed, Aug 20, 2014 at 8:31 AM, Karsten Schmidt i...@toxi.co.uk wrote:
Hi fellow Clojurians,
it's my absolute pleasure to finally announce the open source release
of an art project I've been working on full-time since beginning of
the year:
DevArt Co(de)Factory is a
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2311
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2311]
This release fixes a regression in browser REPL.
Just wanted to add that all of the current transducers work in Clojure
is now available in ClojureScript master.
David
On Wed, Aug 6, 2014 at 2:01 PM, Rich Hickey richhic...@gmail.com wrote:
I pushed today the initial work on transducers. I describe transducers
briefly in this blog post:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2301
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2301]
The primary reason for this release is the inclusion
I just cut 0.0-2307, the only change is that the compiler now
optimizes anonymous multi-arity fns which results in a big performance
boost to transducer code.
David
On Thu, Aug 7, 2014 at 5:08 PM, David Nolen dnolen.li...@gmail.com wrote:
ClojureScript, the Clojure compiler that emits
On Mon, Aug 4, 2014 at 9:11 AM, Herwig Hochleitner
hhochleit...@gmail.com wrote:
I dug a bit deeper to see where :js-globals came from and found the old
ticket for this exact issue: http://dev.clojure.org/jira/browse/CLJS-680
I propose that we remove it, because it's unnessecary when we gensym
I would rely on the behavior in the REPL to check this - the REPL
compilation environment is likely different.
On Mon, Aug 4, 2014 at 3:59 PM, Sam Ritchie sritchi...@gmail.com wrote:
Hey Herwig,
I'm currently on [org.clojure/clojurescript 0.0-2261], and I'm seeing no
munging:
I meant would not
On Mon, Aug 4, 2014 at 4:28 PM, David Nolen dnolen.li...@gmail.com wrote:
I would rely on the behavior in the REPL to check this - the REPL
compilation environment is likely different.
On Mon, Aug 4, 2014 at 3:59 PM, Sam Ritchie sritchi...@gmail.com wrote:
Hey Herwig
This release includes some long outstanding proposed enhancements:
### Changes
* OM-133: validate Om component fn return values
* OM-134: add om.core/set-state-nr! and om.core/update-state-nr!, they
do not refresh (experimental)
* OM-162: extend default cursor to IEmptyableCollection
let-binding:
ns.console = (function console_1337(){return console;});
Ticket?
2014-08-01 15:07 GMT+02:00 David Nolen dnolen.li...@gmail.com:
js/foo does not resolve to the global namespace.
David
On Thu, Jul 31, 2014 at 9:42 AM, Sam Ritchie sritchi...@gmail.com wrote:
Hey guys,
I
js/foo does not resolve to the global namespace.
David
On Thu, Jul 31, 2014 at 9:42 AM, Sam Ritchie sritchi...@gmail.com wrote:
Hey guys,
I ran into this last night when trying to port some ancient JS in our
project over to cljs. I was defining an om component called
users-typeahead, and in
I'm happy to announce Om 0.7.0. The biggest change is depending on
ClojureScript 0.0-2277 and React 0.11.1. There's a breaking change
around the :ctor option to om.core/root which is now renamed
:descriptor. Check the om.core/root docstring for more details.
As it's been a long while between
:36 PM, David Nolen dnolen.li...@gmail.com wrote:
I'm happy to announce Om 0.7.0. The biggest change is depending on
ClojureScript 0.0-2277 and React 0.11.1. There's a breaking change
around the :ctor option to om.core/root which is now renamed
:descriptor. Check the om.core/root docstring
Thanks for the correction, fixed!
On Fri, Aug 1, 2014 at 4:26 PM, Rostislav Svoboda
rostislav.svob...@gmail.com wrote:
Thanx a lot guys!
The biggest change is depending on ClojureScript 0.0-2277 and
BTW the Using it section of README.md still says 0.0-2173:
(defproject foo 0.1.0
...
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2280
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2280]
### Changes
* depend on latest
Can you be more specific about the naming issues?
David
On Wednesday, July 30, 2014, Thomas Heller th.hel...@gmail.com wrote:
David its probably best to hold off on that release. It seems the
closure-library HEAD version depends on a newer closure compiler version
than the one available via
Based on this information it sounds like the new Google Closure
artifacts are good to go. The keyword thing we'll have to address in a
subsequent release. It would be useful to know what Mobile Safari
clients you see being affected.
David
On Wed, Jul 30, 2014 at 11:11 AM, Thomas Heller
(Linux; U; Android 4.1.2; de-de; GT-N8010 Build/JZO54K)
AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30
Got some more in the log if you need them.
HTH
On Wednesday, July 30, 2014 8:57:51 PM UTC+2, David Nolen wrote:
Based on this information it sounds like the new Google
On Friday, July 25, 2014 8:37:06 PM UTC+2, David Nolen wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2277
Leiningen dependency information:
[org.clojure
Just add sonatype to your :repositories project.clj entry
https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L79
David
On Tue, Jul 29, 2014 at 4:22 PM, Thomas Heller th.hel...@gmail.com wrote:
Uhm small hint on how I'd do that? My maven-fu is weak.
But given that
]
Confirmed to resolve CLJS-826.
On Tuesday, July 29, 2014 10:30:21 PM UTC+2, David Nolen wrote:
Just add sonatype to your :repositories project.clj entry
https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L79
David
On Tue, Jul 29, 2014 at 4:22 PM, Thomas Heller th.h
is causing the
problem.
Would be nice if you could build a new closure release and bump the
dependency in clojurescript.
Thanks,
/thomas
On Friday, July 25, 2014 8:37:06 PM UTC+2, David Nolen wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2277
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2277]
The main reason behind this release is fixing a
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2268
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2268]
The main reason for this release is to address a
?
kl. 04:42:39 UTC+2 onsdag 2. juli 2014 skrev David Nolen følgende:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2261
Leiningen dependency information:
[org.clojure
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2261
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2261]
### Changes
* Dependency on Clojure 1.6.0
*
Nothing to add other than to say this is really cool stuff :)
David
On Tue, Jun 24, 2014 at 2:29 PM, Mike Fikes mikefi...@me.com wrote:
(Apologies to Greg for having essentially hijacked this thread, but I
suspect he'd find this cool.)
I have no experience with the Swift REPL yet, but I'm
On iOS is advanced compilation really necessary? :simple + :static-fns true
should suffice.
On Wednesday, June 18, 2014, Mike Fikes mikefi...@me.com wrote:
Is there a way to indicate that a (ClojureScript) protocol is intended to
be used from the host?
Details:
I can define a protocol and
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2234
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2234]
This release fixes a critical bug around the `case`
core.logic only currently supports solving finite domains CLP(FD),
you'll have to look elsewhere for a CLP(R) solver for now.
David
On Tue, Jun 10, 2014 at 5:30 PM, cej38 junkerme...@gmail.com wrote:
I picked a toy problem that was really easy to solve, figuring that once I
had the idea down,
That's that's the suggested way - just pick a large bound.
David
On Tue, Jun 10, 2014 at 11:28 AM, cej38 junkerme...@gmail.com wrote:
I found the solution to my first problem at
https://github.com/clojure/core.logic/wiki/Features (with a few small
changes by me):
(run* [q]
(fresh [x y]
collisions in large 3d meshes as a result. Awesome!
K.
On 8 Jun 2014 18:07, David Nolen dnolen.li...@gmail.com wrote:
1.6.0 branch is ready to be tested
http://github.com/clojure/clojurescript/tree/1.6.0, please give it a try in
your projects. You can install this version of ClojureScript
- unreachable code
{return null;
^
Jun 10, 2014 7:49:49 AM com.google.javascript.jscomp.LoggerErrorManager
printSummary
WARNING: 0 error(s), 4 warning(s)
On Monday, 9 June 2014 20:07:48 UTC+3, David Nolen wrote:
That's great to hear, the feedback is much appreciated.
David
On Mon, Jun
at 4:16, David Nolen wrote:
Given the feedback so far such a request seems to be in the minority.
You could run a separate project for the CLJS parts. That said, is there
something in the latest release (0.0-2227) that you find problematic that
you can't continue with it?
David
On Fri
into your local Maven.
Use this in version number in your project.
David
On Fri, Jun 6, 2014 at 10:43 AM, David Nolen dnolen.li...@gmail.com wrote:
Future releases of ClojureScript will have a hard dependency on Clojure
1.6.0. If you have any objections, speak up now :)
David
--
You received
Future releases of ClojureScript will have a hard dependency on Clojure
1.6.0. If you have any objections, speak up now :)
David
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that
, but I’m curious what are the motivating factors? Are there
any new features/bug-fixes planned for ClojureScript that will depend on
Clojure 1.6.0 features? or is this just a case of keeping things as
up-to-date as possible?
On Friday, June 6, 2014 at 17:43, David Nolen wrote:
Future releases
2014-06-06 19:19 GMT+02:00 Karsten Schmidt i...@toxi.co.uk:
+1
On 6 Jun 2014 16:59, David Nolen dnolen.li...@gmail.com wrote:
Clojure 1.6.0 introduced Murmur3 for much improved collection hashing
and several new functions macros. There's very little incentive to
continue to support 1.5.X
Socks phill.w...@gmail.com wrote:
Can a lein-cljsbuild clj+cljs project specify separate versions of Clojure
for the cljs and clj parts?
If not, please give it another 6 months.
On Friday, June 6, 2014 10:43:42 AM UTC-4, David Nolen wrote:
Future releases of ClojureScript will have a hard
I wouldn't pass judgement on Swift too soon. Eval works just fine in the
REPL and it appears the language supports hot code loads out of the box.
Swift also has real support for final fields via 'let'. I personally think
a ClojureSwift could be quite interesting :)
On Wednesday, June 4, 2014,
Thanks for the report, docstring updated.
David
On Tue, May 27, 2014 at 5:16 PM, Dom Kiva-Meyer li...@domkm.com wrote:
The clojure.core.match/match docstring states that it takes ...a vector
of occurrences, vars. Clause question-answer syntax is like `cond`.
Questions must be wrapped in a
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2227
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2227]
Enhancements
* optimized case
*
Can you demonstrate a complete minimal example?
Thanks,
David
On Tue, May 20, 2014 at 4:06 AM, Austin Haas aus...@pettomato.com wrote:
I'm having trouble isolating a small test case. I call the following code
in an update tick:
(let [prev' @prev
state' @state]
(let [rems
There's no easy way to do this beyond making your own relational string
type as you've suggested.
On Sunday, May 4, 2014, Adam Saleh adamthecam...@gmail.com wrote:
Hi,
every once in a while I am toying with an idea of doing string
manipulation in core.logic.
Naively trying to use appendo
Om 0.6.1 significantly changes how component local state works - we now
rely on React's forceUpdate to update components that use local state. This
is a significant change so I would like people test this out on their
existing code bases as soon as possible.
The immediate benefit is that
It's mostly for demonstration purposes, but I think it will be a common
pattern when more complex coordination is required. I think components
should probably communicate via callbacks and applications can glue things
together with core.async if it's beneficial.
David
On Wed, Apr 9, 2014 at
beneficial to use callbacks or channels? Are there
'rules-of-thumb' that I could follow until that intuition is established?
On Wednesday, April 9, 2014 8:40:19 AM UTC-7, David Nolen wrote:
It's mostly for demonstration purposes, but I think it will be a common
pattern when more complex
Also don't use a channel unless you actually need complex coordination. I
would always default to a callback first.
David
On Wed, Apr 9, 2014 at 7:56 PM, David Nolen dnolen.li...@gmail.com wrote:
Reusable components - use callbacks
Application components (non-reusable or less re-usable
project (the
one I mentioned above). So if you need a lab rat for some of these
ideas...
On Wednesday, April 9, 2014 6:57:50 PM UTC-5, David Nolen wrote:
Also don't use a channel unless you actually need complex coordination. I
would always default to a callback first.
David
On Wed, Apr 9
On Wed, Apr 2, 2014 at 3:42 AM, rlewczuk rafal.lewc...@gmail.com wrote:
First one is about object created by (om/build ...) - in all tutorials
these objects are always created on the fly in (render ...) functions. So
if some component disappears from view for some time, it loses its state.
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2202
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2202]
This release is similar to 0.0-2199, it just
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2199
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2199]
The only difference is the removal of spurious
Thanks!
On Mon, Mar 31, 2014 at 6:26 PM, Stuart Sierra
the.stuart.sie...@gmail.comwrote:
Oof, it's been ages since I looked at that stuff. I'll take a look.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to
It looks like the zip file that usually included with the releases is
missing?
http://repo1.maven.org/maven2/org/clojure/clojure/1.5.1/
vs.
http://repo1.maven.org/maven2/org/clojure/clojure/1.6.0/
Thanks,
David
On Tue, Mar 25, 2014 at 7:00 AM, Alex Miller a...@puredanger.com wrote:
We are
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2197
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2197]
Changes Enhancements:
* updated Google Closure
Unless you're compiling a very large file - with auto :optimizations :none
you should always get sub-second compile times under auto.
David
On Fri, Mar 21, 2014 at 10:55 AM, Timothy Baldridge tbaldri...@gmail.comwrote:
are you using lein cljsbuild auto ? That's what I use, and I get about
On Fri, Mar 21, 2014 at 11:45 AM, Adrian Miron adrian.miron...@gmail.comwrote:
On Thursday, March 20, 2014 10:58:08 PM UTC+2, David Nolen wrote:
If you don't pass app state data to this component then you don't need to
bother with build at all. If you need a component that doesn't need app
On Thu, Mar 20, 2014 at 5:57 AM, Adrian Miron adrian.miron...@gmail.comwrote:
I'm starting to use om in some projects and one of the first components I
had to build was a simple notification component. It shows a message at the
top of the page. Other components in the page will use it to
Max,
Just a fair bit of warning that such a project should probably only happen
under GSoC only if it actually pushes along *official* support for
bootstrapping ClojureScript in ClojureScript. Just forking the compiler and
making changes until it works just isn't going to fly and I do not think
Just tried 1.6.0-RC1 with ClojureScript master. All ClojureScript tests
pass except for one which is due to assumptions about print order
(different now due to hash code changes). Easy enough to fix once 1.6.0
actually ships.
David
On Tue, Mar 18, 2014 at 1:44 PM, Alex Miller
Yep, we'll get rid of it once 1.6.0 actually ships.
David
On Tue, Mar 18, 2014 at 5:04 PM, Alex Miller a...@puredanger.com wrote:
I assume that fixing this is a matter of updating src/clj/cljs/core.clj in
clojurescript to exclude unsigned-bit-shift-right?
On Tuesday, March 18, 2014
I've written up an explanation how to make this work
http://swannodette.github.io/2014/03/14/externs-got-you-down/
David
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from
Andrew,
I've tried the new JARs on a couple of projects and I have not encountered
these issues. Did you make sure to run a `lein cljsbuild clean`?
Thanks.
David
On Wed, Mar 12, 2014 at 8:19 PM, Andrew Keedle akee...@gmail.com wrote:
Stuart,
Did you ever get any response to this? I made
While I think Om's approach to application state management delivers
considerable benefit, I think it would be unfortunate if all the labor put
into reusable Om components was confined to Om users. With the latest
release I've included examples demonstrating how two important things are
now
I'm cross posting this to the miniKanren mailing list.
It sounds like core.logic or cKanren could be applied to your problem but
would need more details. I also wouldn't rule out finite domain solvers
like JaCoP.
David
On Wed, Mar 5, 2014 at 9:52 AM, Laurens Van Houtven _...@lvh.cc wrote:
Your markup needs to look something like:
div id=classes/div
script src=http://fb.me/react-0.9.0.js;/script
script src=js/out/goog/base.js type=text/javascript/script
script src=js/om_ho.js type=text/javascript/script
script type=text/javascriptgoog.require(om_ho.core);/script
HTH,
David
On
of fun working on this stuff, btw. Om is very cool.
Looking forward to getting into the intermediate tutorial with Datomic too
:)
,chris
On Thursday, February 27, 2014 6:03:22 AM UTC-8, David Nolen wrote:
Your markup needs to look something like:
div id=classes/div
script src=http://fb.me
Fixed in 1.6.
David
On Thu, Feb 27, 2014 at 3:50 PM, Brent Millare brent.mill...@gmail.comwrote:
Clojure 1.5.1
user= (defprotocol IEmit (-emit [x]))
IEmit
user= (defrecord css [y] IEmit (-emit [_] y))
user.css
user= (-emit (-css 3))
3
user= (map -emit [(-css 3)])
I don't really have anything to add to this thread but I will say that Om's
use of identical? is an implementation detail that's likely to change. =
already does an identical? check, ideally Om could use not= in the future
instead of (not (identical? ...)).
David
On Tue, Feb 25, 2014 at 12:54
At long last the ClojureScript compiler can now target Node.js under
optimizations :whitespace or :none as of this commit:
http://github.com/clojure/clojurescript/commit/0c7b31ada01237de33cef77b817ccef3f2b3576d
Some basic notes here:
- that
change does work indeed! But then why does my original version work in
Clojure? A change in quoting usually only causes havok/failure, but
here it doesn't seem to...
Thanks again! K.
On 23 February 2014 22:15, David Nolen dnolen.li...@gmail.com wrote:
I think your unquoting needs
Awesome!
On Mon, Feb 24, 2014 at 2:06 PM, Daniel Solano Gómez cloj...@sattvik.comwrote:
Hello, all,
I am happy to report that Clojure has been accepted as a Google Summer
of Code 2014 mentoring organisation. I'd like to thank everyone who
gave us ideas for our Project Ideas [1] page, and
You shouldn't use js*, and in this case it can be avoided. The problem
you're encountering is a long outstanding wart that ClojureScript macros
resolve symbols in Clojure not ClojureScript. Instead of + (which is
actually clojure.core/+) you want to specify cljs.core/+:
(defmathop cljs.core/+
cljs.core in that macro's namespace, but then
it complains this way:
clojure.lang.Compiler$CompilerException: java.lang.RuntimeException:
Can't take value of a macro: #'cljs.core/+,
compiling:(macromath/macros.clj:59:1)
Hmmm
On 23 February 2014 19:52, David Nolen dnolen.li...@gmail.com
The issue is that advanced compilation produces a single artifact.
David
On Sun, Feb 23, 2014 at 8:22 PM, boz b...@cox.net wrote:
I'm having trouble with the Om basic tutorial Higher Order
Componentshttps://github.com/swannodette/om/wiki/Basic-Tutorial#wiki-higher-order-components
using
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-2173
Leiningen dependency information:
[org.clojure/clojurescript 0.0-2173]
Changes Enhancements:
* IAtom marker protocol
*
The only change is that we now depend on the just released React 0.9.0.
Feedback welcome!
https://github.com/swannodette/om
David
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that
Due to asm.js some JS engines are starting to compile switch statements
where the cases are integers into jump tables. Compiler enhancement that
compiles optimizable case expressions to JS switch statements would be a
welcome enhancement - http://dev.clojure.org/jira/browse/CLJS-713.
David
On
In order to stay in sync with React 0.9.0-rc1 I've cut Om 0.5.0-rc1. There
are a couple of small breaking changes due to React but otherwise the
differences between 0.4.2 and 0.5.0-rc1 are minor. One big enhancement is
that you can now render to a string with om.dom/render-to-str.
Another big
On Mon, Feb 17, 2014 at 3:43 AM, Ransom Williams auvergn...@gmail.comwrote:
First of all thanks to everyone working on clojure for making web
development suck less. I recently sandboxed a clojure server application,
and the tooling, documentation, and availability of libraries are all
/tests/main.js in 7.81 seconds.
On Thursday, February 13, 2014 10:02:50 PM UTC-8, David Nolen wrote:
Happy to announce a new release of Om. There are some breaking changes
mostly to make the API more uniform - om.core/root was needlessly different
from om.core/build.
The biggest and most
Om 0.4.0 requires ClojureScript 0.0-2156, also looks like you need to run a
`lein cljsbuild clean`.
David
On Fri, Feb 14, 2014 at 8:00 AM, Tatu Tarvainen tatu.tarvai...@mac.comwrote:
Btw, I seem to get the following compiler errors after upgrading om from
0.3.6 to 0.4.0
(clojurescript
You will need to implement unification for your record type. I recommend
just using simpler data structures unless how to do this is apparent to you
- it's not particularly difficult but you need to go to the source if you
want to understand how to make it work.
David
On Fri, Feb 14, 2014 at
exists? doesn't seem right to me. Also we do use `exists?` currently in
ClojureScript since feature detection is so common in client side code and
the name seems more appropriate to me in that context. That could of course
change but we would need to coordinate.
David
On Fri, Feb 14, 2014 at
Also I think the ship on overloading some already sailed with some- and
some-
David
On Fri, Feb 14, 2014 at 3:27 PM, Dom Kiva-Meyer li...@domkm.com wrote:
Great changes! I have a question about #5.
5) New some operations
Many conditional functions rely on logical truth (where falsey
degree of precision, and
perhaps more characters, would have been a better choice.
On Friday, February 14, 2014 2:36:51 PM UTC-8, David Nolen wrote:
exists? doesn't seem right to me. Also we do use `exists?` currently in
ClojureScript since feature detection is so common in client side code
cause I missed the boat. :-)
Did that discussion take place here or in Jira? I'd definitely like to be
able to chime in with thoughts/suggestions in the future WRT this topic.
On Friday, February 14, 2014 7:46:23 PM UTC-8, David Nolen wrote:
exists? is a pretty critical feature for application
201 - 300 of 2038 matches
Mail list logo
