If nothing else, the functions in oolong.util should be pretty handy for manipulating them. Or can serve as a guide for manipulate them programmatically.
I’m working on a bunch of complementary stuff to this at present, including a library for developing components on top of oolong that will ease the transition between config-world and real-world, along with a bunch of components written to interoperate nicely. I’ve found that oolong simplifies interop in one major regard: specifying everything as nested maps means functions to start components will always take one argument. I’ve seen a lot of libraries do this to solve this problem. James > On 17 Mar 2015, at 23:04, Andrew Oberstar <ajobers...@gmail.com> wrote: > > Just a quick look so far, but it looks pretty interesting. I'm working on a > multi-module project and I'd like to have the flexibility to run those > modules separately or together. Extracting the component structure out into a > config file could be pretty helpful in that regard. Nice work! > > Andrew Oberstar -- 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
