Chas Emerick writes: > On Wed 19 Feb 2014 08:11:57 AM EST, Moritz Ulrich wrote: >> >> Tom Jakubowski writes: >> >>> Connecting a ClojureScript REPL to certain Javascript environments - like >>> those served to a browser but not over HTTP, e.g. in a Chrome extension or >>> Spotify application - is difficult or downright impossible given >>> implementation details of existing ClojureScript REPL solutions. Weasel >>> provides a WebSocket-based transport for a ClojureScript REPL that >>> circumvents these limitations on modern browser platforms. >>> >>> https://github.com/tomjakubowski/weasel >>> >>> Namely, Weasel addresses an issue previously brought up on the Clojure >>> mailing list a couple years >>> ago:https://groups.google.com/forum/#!topic/clojure/lC8me2Gx_B4 >>> >>> Weasel is my first real Clojure or ClojureScript project so there are >>> certainly some rough edges. Feel free to ping me with an email or on IRC >>> (dsrx@freenode) if you need help or have found an issue. >>> >>> Tom Jakubowski >>> >>> P.S. I’m unsure of how I've licensed Weasel. I used the existing >>> ClojureScript REPL code as a rough guide (as I needed to learn how it >>> worked) to writing my own code for Weasel which I then released into the >>> public domain. However, one file in particular >>> (src/cljs/weasel/impls/websocket.cljs) was taken directly from some >>> commented-out code in the CLJS source. I’m happy to re-assign copyright or >>> re-license the rest of the project or do whatever else I need to if someone >>> with more knowledge suggests I’ve screwed up the copyright/licensing. >> >> I just tested it in a small pet-project I have and it works really good. >> It also doesn't seem to suffer from the AdBlock problems the 'normal' >> Clojurescript browser-repl has. >> >> Thanks, and keep up the good work! >> > > I haven't heard of them related to ad-blocking before; hopefully, this > is the same class of problem: > > https://github.com/cemerick/austin/issues/17#issuecomment-25328315 > > - Chas
Whoops - I thought I commented on this issue. Adblock in Chromium was blocking the iframe created by the browser-repl. Disabling Adblock for the site fixed it. -- Moritz Ulrich
pgp6SjlZ3zrMm.pgp
Description: PGP signature
