Ah, interesting. Would definitely love to see some sample code when you have the time. Specifically the bits about calling into nashorn from an interface exposed in ClojureScript, I haven't seen this done before and would be interested to see how that works.
On Wed, May 20, 2015, at 04:15 PM, Dustin Getz wrote: > Yes, 99% of the application logic is defined in clojurescript e.g. > Routing and Ajax queries, there is a very small amount of JVM code > which uses nashorn to call into a specific interface exposed in > clojurescript which knows how to render html, check if a url is > canonical, redirect or compute initial state and render html for that > state, and some other minor things. However it does constrain the way > you structure your clojurescript application, for example Ajax has to > happen in a certain structured way to make this work smoothly. Really > the only tricky bit is getting the builds structured just perfectly as > not all browser dependencies work in nashorn (no dom). There are five > build targets: dev-browser, dev-server, prod-browser, prod-server and > figwheel. Debugging sucks. > > -- > 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 "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. -- 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 "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
