Hi James, ‘component’ is a difficult term to google for, so I hadn’t come across your project :)
I think your module had slightly different design goals from mine. Mine were: * everything in one config file (although i also provide support for separate data-config and system config) * be minimal. i’ve got a bunch of things i’m building on top of oolong at present that will together provide a more “complete” experience I see you note that phoenix is ‘batteries included’. That’s a great experience for new users, but i wasn’t trying to build that on this occasion :) The leiningen template and plugin are also nice additions, and reloaded workflow integration is very handy. Reloaded workflow has been an experience for me. I haven’t yet managed to get it working in the face of compile errors. I find myself restarting the leiningen repl about as much as before. For this reason I chose to keep it separate and delay dealing with it for a few weeks. Have you managed to overcome these problems? I’m definitely interested in knowing how if so. I’ve only really given phoenix a few minutes of my attention so far, but I like what I see and I’m liable to steal ideas for some of the things i’ll be building on top of oolong. Feel free to reply offlist if you have any further questions. James > On 18 Mar 2015, at 09:07, James Henderson <ja...@jarohen.me.uk> wrote: > > Hi James, > > This looks very similar to Phoenix - a project I've been working on for the > last few months. It's pretty likely you hadn't heard of it (and that's fine - > it's not been hugely publicised!), but if you have, I was wondering whether > there was anything about it that you felt was missing/a bad design decision? > If so, would be great to get your feedback! > > Cheers, > > James > > On Tuesday, 17 March 2015 10:02:51 UTC, James Laver wrote: > I've been using stuartsierra's handy component library for a while now, but I > wanted an easier way of connecting components together. > > To that end, I wrote oolong. The main mode of operation is to take an edn > configuration file and connect the specified systems and components. > > https://github.com/jjl/oolong > > https://clojars.org/oolong > > Feedback welcome. I spent quite a while documenting it so hopefully it should > be fairly clear to understand. > > James > > -- > 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 a topic in the Google > Groups "Clojure" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/clojure/T_skapDqZ0U/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > clojure+unsubscr...@googlegroups.com. > For more options, visit 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
