Another tip, I have extracted the support for nesting html templates using enlive from http://clojurescriptone.com. What that gives you is the support for "sandboxing" all the templates under a given url i.e templates/* so that the designers can work with HTML-only but in a DRY fashion.
What I mean by that is that you don't have to repeat including resources like CSS, scripts, headers/footers etc. in all your templates. It's a ring middleware: https://github.com/ebaxt/enlive-partials kl. 00:28:02 UTC+1 fredag 11. januar 2013 skrev larry google groups følgende: > > > So, I am working on a web app that is buillt with Clojure/Ring/Jetty > and, importantly, Enlive. My directory structure is like this: > > /resources > /public > /css > /js > /img > /templates > > /src > /discovery > core.clj > > > The great thing about Enlive is that the templates are pure HTML. This > makes it easier for graphic designers and frontenders to work with > them directly. I am working with a designer and frontend developer, > who have absolute power over the stuff going into the /resources > folder. > > I have 2 questions: > > 1.) In my routes, I am using (wrap-resource) instead of (wrap-file). > Is there any way to enable live updates, so that if the designer > changes the images in /resources/public/img, they can then see the > changed images when looking at the app in their browser? Right now I > have to recompile the app and restart it for change to be visible to > the designer. > > 2.) I notice that if a change is made in /resources, but no change is > made anywhere else, then if I run "lein compile" nothing happens. Is > there a way to force lein to compile? > > I have little insight about how to build a multiperson workflow while > doing Clojure development. One thought I had: I could automate the re- > build of the app, and give the designer an easy way to trigger that > rebuild (click a button in Jenkins -- easy enough because we rely on > Jenkins for all of our builds, and the interface is simple enough for > non-programmers to handle). But I would like to hear what other people > do. > > > > -- 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
