> I was in much the same position as you a few months ago. Refactoring > Compojure to use the Ring libraries took a lot of work, so I have an > idea of the amount of effort involved :)
I've added the latest version of Ring to Conjure, but I haven't updated the cookies or parameters yet. Otherwise, it seems to be working. I'm busy with other stuff right now (more on that later), but I'll get to it. > Another idea is to write a conjure Leiningen plugin. Then developers > could create a project using Leiningen, and then use "lein conjure" to > generate all the directory paths, etc. e.g. Yesterday morning, I took one more look at Leiningen for Conjure. After a few false starts and build hacking, I had exactly the same idea for a Conjure plugin for Leiningen. I've started breaking Conjure into two jars, conjure.jar which will be all the base libraries for Conjure, and lein-conjure.jar which will be the Conjure Leiningen plugin. After setting up the Leiningen builds and moving the source files into a more appropriate structure, I'm now fixing all of the errors and test failures. Right now, pretty much everything that was in the vendor/conjure directory will be in the conjure.jar. All of the scripts and a new initial Conjure generator script will be in the plugin. Everything else will be generated just like before. > I believe there's a leiningen-war project on GitHub that generates war > files for a Leiningen project. You may want to take a look at that. The above changes will obviously make the leiningen-war project very useful. I'll check it out when I'm done with the plugin. Strangely, I don't see it in the Leiningen plugin list. > If there's any problem with dropping it in, let me know. I tried to > make it as straightforward as possible, but I might not have thought > of everything :) I checked out clout, and found I couldn't use it. Maybe I don't know exactly how it works, but I would like to define routes with something like Rails old "/:controller/:action/:id", but clout seemed to require something more like "/book/:id" where book would then be hard coded to the book controller and the action could be figured out from the request method. Though this is somewhat closer to how Rails works now, it isn't very useful for me. Am I missing something, or is that how you designed it? How would the Rails route: "/book/1/edit" work? Clout does look like an interesting project, and will probably use it to some extent if I can figure out how best to do it. -- 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
