Cool. I'm very open to any help you can offer. Right now, I'm working through:
- if / how to attach assets (images, etc) to .rtf or .md file formats (see here<http://stackoverflow.com/questions/17758621/howto-attach-image-audio-video-pdf-to-rtf-md> ) - how to cleanly model entity relationships, beyond just nested maps; I like the Datomic schema approach, and am wondering if: 1. I can just use their entity relationship approach as an in-memory library 2. later take those entity relationships, and spit out i) relational data ii) mongo data, etc (not just using SQL as Datomic's storage, but having a 3rd party client be able to read the output data structure ) - what I should use to model workflow; possibly lamina<https://github.com/ztellman/lamina> ? - what's the best interface & messages to pass between the core service and plug-ins; I'm thinking of the nrepl<https://github.com/clojure/tools.nrepl>protocol, but I need to work out: 1. communication between plug-ins 2. way to list possible actions (namespace qualify action names) 3. way to publish actions 4. way for core service to listen for messages from a plug-in 5. way to pass binary data (asset(s)) between stefon and plug-in I think the next week or so will be investigating this list. It represents most of the hurdles I see in getting a successful core / plug-in architecture running. Insight or expertise on any of these points is very welcome. Cheers Tim Washington Interruptsoftware.ca / Bkeeping.com On Sat, Jul 20, 2013 at 1:31 PM, Manuel Paccagnella < manuel.paccagne...@gmail.com> wrote: > Interesting +1 > > I've slammed together some quick and dirty Clojure code and wrote my own > little blog engine (I'll not link the repo, the code is... well > quick&dirty: I needed something running quickly). But it has the bare > minimum and I didn't find any real feature complete blog engine as the one > you are proposing. An engine designed with a "clojuresque" vision behind > its architecture (simple, modular, extensible, and made of composable > pieces) would be very interesting to see come to life. > > I'll read through the comments and hopefully add something when this > headache will give me a break. I'm about to begin writing a prototype > system for my dayjob, but I'd like to help you in this endeavour (I hope > I'll have the time to do that). > > Cheers, > Manuel > > -- -- 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/groups/opt_out.
