I’m not sure that the original question is still valid, as it’s over 2 years 
old now.  I’ve had success using figwheel[1] to automatically recompile 
Clojurescript and send the updated js to the browser, sans reloading.

[1] https://github.com/bhauman/lein-figwheel 
> On Nov 6, 2014, at 4:57 PM, Asim Jalis <asimja...@gmail.com> wrote:
> 
> Hi Laurent,
> 
> For refreshing the browser, I call (.reload js/location) from the browser 
> REPL.
> 
> So this is the workflow:
> 
> Terminal 1: lein cljsbuild auto dev
> Terminal 2: lein trampoline cljsbuild repl-listen
> Browser: localhost:9000/myapp.html
> 
> 1. I make change to the CLJS file.
> 2. cljsbuild auto dev picks it up and recompiles the JS file.
> 3. In the REPL I call (.reload js/location) which picks up the new JS file.
> 4. In the REPL I call (myapp.run-tests) which runs the unit tests.
> 
> You can view the sources at http://github.com/asimjalis/cluster_splitter.
> 
> Asim
> 
> On Monday, September 10, 2012 9:28:44 AM UTC-7, Laurent PETIT wrote:
> Hello, 
> 
> A "ClojureScript workflow" newbie question.
> 
> People seem to be using a lot lein-cljsbuild to work with their ClojureScript 
> project.
> 
> From what I understand, this means they have a watcher which recompiles 
> javascript in the background whenever they save changes to clojurescript 
> files to the disk.
> Thus, this means that whenever they make a change, they have to restart the 
> application (e.g. refresh the browser).
> 
> Is that the end of the story with lein-cljs ? (wrt development workflow ?)
> 
> On the other end, when looking at the wiki page for ClojureScript One, one 
> can see : 
> 
> "Using the REPL as the main way to deliver code to the browser means never 
> having to refresh the page. One could theoretically build an entire 
> application without a single page refresh. If you find yourself refreshing 
> the page after every change you make, you're doing it wrong. What is this, 
> 2009?"
> 
> 
> So before digging into ClojureScript for the first time, I'd like to know 
> what to thing about all this, so that I don't waste my time following wrong 
> paths.
> 
> 
> What would be my expected "default" workflow when starting to write a single 
> page application with ClojureScript, in September 2012 ?
> 
> Cheers,
> 
> -- 
> Laurent
> 
> -- 
> 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 new members are moderated - please be patient with your 
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en 
> <http://groups.google.com/group/clojure?hl=en>
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to clojure+unsubscr...@googlegroups.com 
> <mailto:clojure+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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 new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to