Thanks David, that's what I thought might be the case.
Oddly enough as far as I can tell, RN is a function from an om-tools mixin
(and therefore cljs code). I'll see if I can replicate in a test project.
On 30 Jul 2014 00:53, "David Nolen" wrote:
> Using JS libs as their own externs is not guara
I knew I forgot something! It's in Clojars now as [bootstrap-cljs "0.0.1"].
On Wednesday, July 30, 2014 4:51:22 AM UTC+7, Paul English wrote:
> Very cool, you should deploy a version to Clojars to make it accessible.
>
>
>
> On Jul 29, 2014, at 1:58 PM, Olli Piepponen wrote:
>
>
>
> > Hi,
>
Hi all,
I needed to define some shortcuts in an application and was left unhappy
with the current existing library, so I more or less ported my own JS
keybinding library to ClojureScript:
https://github.com/piranha/keybind
It's quite simple to use and should be enough for most purposes (if it's
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 maven.
At least I'm seeing some renaming issues for advanced compilation.
--
Note that posts from new members are moderated - pl
Can you be more specific about the naming issues?
David
On Wednesday, July 30, 2014, Thomas Heller 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 maven.
>
> At lea
How to insert a comment in the generated javascript file?
1. In simple compilation mode
2. In advanced compilation mode
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"
Sorry, I would be if I could.
Trying to track it down, but debugging an optimized build is not exactly easy.
:(
When using 2277 I have no errors, when using 2277 with the new closure lib
release I have some "undefined" errors. That usually means some sort of
renaming gone wrong.
Error:
Cannot
Geez, 2277 actually works just fine. 2234 doesn't work, but it actually doesn't
work with either closure-library version. Forgot that I reverted to 2234 due to
the keyword issue.
2277 + [org.clojure/google-closure-library "0.0-20140718-946a7d39"]
seems fine, except for that keyword issue.
Sorr
You could use :preamble to prepend a file to the generated output.
On 30 July 2014 15:37, Yehonathan Sharvit wrote:
>
> How to insert a comment in the generated javascript file?
>
> 1. In simple compilation mode
> 2. In advanced compilation mode
>
>
> --
> Note that posts from new members are m
FYI, using the :psuedo-names compiler option is very handy for debugging
advanced-compile munging issues, e.g.:
:compiler {:optimizations :advanced
:pseudo-names true
...}
On Wednesday, July 30, 2014 10:11:17 AM UTC-5, Thomas Heller wrote:
> Geez, 2277 actu
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 wrote:
>
I posted some User Agents in the other Thread.
https://groups.google.com/d/msg/clojurescript/diRGgGmTXPk/bbNMj3XHQ4AJ
Mozilla/5.0 (iPad; CPU OS 7_1_2 like Mac OS X) AppleWebKit/537.51.2 (KHTML,
like Gecko) Version/7.0 Mobile/11D257 Safari/9537.53
Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_2 like Mac
Can you please list the affected clients on this ticket
http://dev.clojure.org/jira/browse/CLJS-830, thanks!
David
On Wed, Jul 30, 2014 at 5:29 PM, Thomas Heller wrote:
> I posted some User Agents in the other Thread.
>
> https://groups.google.com/d/msg/clojurescript/diRGgGmTXPk/bbNMj3XHQ4AJ
>
>
On Wednesday, July 30, 2014 1:45:43 AM UTC-7, Daniel Kersten wrote:
> Thanks David, that's what I thought might be the case.
>
> Oddly enough as far as I can tell, RN is a function from an om-tools mixin
> (and therefore cljs code). I'll see if I can replicate in a test project.
>
> On 30 Jul
I'm not sure if its caused by om-tools or if its just chance that it
happens to be a call to om-tools. I haven't been able to reproduce it in a
minimal test case yet. I'll try again tomorrow. If it turns out to be
om-tools, I'll open an issue, but its also likely that its a problem in my
own code.
I set :pseudo-names true and it confirms that its the call to the mixin
function that causes this, but I have not yet managed to reproduce it in a
minimal project.
On 30 July 2014 23:53, Daniel Kersten wrote:
> I'm not sure if its caused by om-tools or if its just chance that it
> happens to be
On Wednesday, July 30, 2014 4:07:06 PM UTC-7, Daniel Kersten wrote:
> I set :pseudo-names true and it confirms that its the call to the mixin
> function that causes this, but I have not yet managed to reproduce it in a
> minimal project.
>
>
>
>
> On 30 July 2014 23:53, Daniel Kersten wrote:
17 matches
Mail list logo