Il giorno domenica 21 luglio 2013 01:09:48 UTC+2, frye ha scritto: > > 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> > ) > > As far as I know, in Markdown you can show images inline but that's all. Anyway, it's possible to write HTML code inside a Markdown text and that's how I approach this problem. If I have to embed for example a video, I just use the <video> HTML element.
There is a more comprehensive text markup language called AsciiDoc<http://powerman.name/doc/asciidoc>(used by O'Reilly for their books if I recall correctly, Chas is much more authoritative than me in this ;) And it should be possible to use it in the JVM using asciidoctor-java-integration<https://github.com/asciidoctor/asciidoctor-java-integration>. Maybe it can be an additional option. > - what I should use to model workflow; possibly > lamina<https://github.com/ztellman/lamina> > ? > > I'm not sure Lamina is the right tool for this job. What are your ideas for modeling and executing workflows? > > - > - 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've not investigated this in depth, but why not a simple HTTP interface that talks EDN? > 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. > I don't know if you have read this<http://www.chris-granger.com/2013/01/24/the-ide-as-data/>, but maybe it could give you some ideas about the plugin architecture. "The blog engine as data". The plugin system could be the kernel, and maybe most features could be implemented as plugins. Just dreaming out loud :) > > > > Cheers > > Tim Washington > Interruptsoftware.ca / Bkeeping.com > > > > On Sat, Jul 20, 2013 at 1:31 PM, Manuel Paccagnella < > manuel.pa...@gmail.com <javascript:>> 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.
