@domkm: you can use js* 😛

Anybody seen this exception:

java.lang.IllegalStateException: Can't change/establish root binding of: *cljs-repl-env* with set

I start a repl with boot repl and then in the repl I call (start-repl)

Using adzerk.boot-cljs-repl library for that

https://github.com/adzerk-oss/boot-cljs-repl

Maybe I should ask this in the Boot channel…

@slotkenov: you need to start the repl server using the cljs-repl task then in a client boot repl --client you can call (start-repl)

ahh, I forgot the -c option for boot repl. Didn’t know that was mandatory for the cljs-repl

@martinklepsch: thanks

I can get the closure compiler to pick up an object, but not any properties inside that object My externs file goes like this:

var api = function() {};
api.get = function(limit, offset, callback) {};

By the way: you always need an externs file for any external library? Or am I missing something?

@slotkenov: not always: https://github.com/clojure/clojurescript/wiki/Dependencies#using-string-names

here I use it in a generated library to side-step externs complexity: https://github.com/binaryage/chromex#advanced-mode-compilation

Ah, yeah, I knew that, thanks. But thats kind of hackish I’d say

Didn’t know that library 😉

would be great to have some tool/framework to generate externs files somehow

until then I will use string names, it might increase :advanced build sizes and slow down javascript property lookups a bit, but it is not an issue in many scenarios, for example if the api is not called too often or file size is not that big deal

you could use something like this to make calling code look just fine when accessing props by string names: https://github.com/binaryage/chromex/blob/master/src/lib/chromex/support.clj#L5-L26

@darwin: Nice, thanks for pointing this out

@darwin did you by any chance try these externs?

https://chromium.googlesource.com/chromium/src.git/+/master/third_party/closure_compiler/externs/chrome_extensions.js

look fairly complete to me, although I barely use any of the chrome stuff yet

thanks for pointing that out, last time I checked I found some incomplete externs in closure lib, updated by hand

this could be usable if it was really generated directly from chromium sources

I might eventually support a compilation switch for chromex, to emit non-string property access code, and people could use something like this if they preferred

but right now string access just works(tm), I don’t want to hear from people messing with outdated externs files / using them incorrectly

yeah externs can be painful

chrome api calling code is produced through this generator, I would just make this line configurable, and instead of oget I would generate there normal js-interop access https://github.com/binaryage/chromex/blob/master/src/lib/chromex/wrapgen.clj#L70

and similar

suddenly I'm getting "Invalid :refer, var does not exist in file" errors when I compile incrementally, but if I compile from scratch all is well

@domkm: FYI https://github.com/binaryage/cljs-devtools/releases/tag/v0.5.3

@darwin: Awesome! Thanks!

@martinklepsch: That might just work! I'll give it a shot later. Thanks.

@martinklepsch: js* works but compiler options :language-in :ecmascript6 :language-out :ecmascript3 isn't compiling class declarations

@martinklepsch: Nevermind. It works with simple optimizations (and, presumably, advanced as well) 😄

How can I get js/Notification's onclick to work? I posted details to the question on SO: http://stackoverflow.com/questions/36225109/how-can-i-create-a-js-notification-in-clojurescript-that-can-focus-on-the-window

@josh.freckleton: I replied on SO

@chrisoakman: You sir, are a saint. I spent so long beating my head against this! However, (.focus js/window) still doesn't focus. Even if I run that straight in the figwheel REPL. Any idea why not? (it does however work if it's straight javascript...)

I'm not familiar with window.focus() generally

although the code I posted on that SO thread compiles down to return window.focus(); directly (the return because it's the last expression in that function)

I have a build:

{
              :builds {:prod
                       {:id "prod"
                        ; The path to the top-level ClojureScript source directory:
                        :source-paths ["src-cljs"]
                        :figwheel false
                        ; The standard ClojureScript compiler options:
                        ; (See the ClojureScript compiler documentation for details.)
                        :compiler {
                        :output-to "resources/public/main.js"  
                        :asset-path "out"
                        :main "tanks.core"
                        :optimizations :advanced}}
                       :dev {:id "dev"
                        ; The path to the top-level ClojureScript source directory:
                        :source-paths ["src-cljs"]
                        :figwheel true
                        ; The standard ClojureScript compiler options:
                        ; (See the ClojureScript compiler documentation for details.)
                        :compiler {
                        :output-to "resources/public/main.js"  
                        :asset-path "out"
                        :main "tanks.core"
                        :optimizations :none
                        :pretty-print true}}}}

figwheel seems to be loaded

in the prod build

weird, just deleting the out file worked

@chrisoakman: hm... window.focus() should force the browser to jump to that window/tab automatically. It works just fine in js. I'm traking the problem, and here's an insight. Run the following code:

(do (js/alert "an alert")
    (.focus js/window)
    (.log js/console "console log"))

EDIT: ah weird, I just closed that tab, and re-opened it, and now alerts work, but not focus...

@josh.freckleton: I'm not sure about window.focus(); my gut says it's not a CLJS thing though

given the context you've shared here

@chrisoakman: I'll get it, thanks for all the help

you're welcome; anytime

@chrisocowan: if you're curious at all, I think I've found out that window.focus only works if it's from a user-initiated action. For some reason, there's something about your (awesome) cljs code you helped me with which makes it think that notification clicks aren't user initiated. The following works, and I just need to convert to proper cljs now:

(do (js* "

Notification.requestPermission(function (permission) {
  if (permission !== 'granted') return 'false';

  var notification = new Notification('Here is the title', {
    icon: '',
    body: 'Some body text',
  });

  notification.onclick = function () {
    window.focus();
    return 'true';
  };
});"))

wait, false alarm, it's broken again...

hrm, it looks like in order for the focus to work, some chrome tab needs to have focus when I click on the notification. If not, nothing happens until I click on a chrome tab, and then the notification. Weird.