Understanding Data-centric app and object composition in Clojure -
i've been impressed work of chris granger , light table. question not light table though, more "bot" architecture described using in blog post "the ide value" : http://www.chris-granger.com/2013/01/24/the-ide-as-data/
now, i'm pretty new clojure better explore way of programming: behavior, object, tag:
(behavior* :read-only :triggers #{:init} :reaction (fn [this] (set-options {:readonly "nocursor"}))) (object* :notifier :triggers [:notifo.click :notifo.timeout] :behaviors [:remove-on-timeout :on-click-rem!] :init (fn [this] [:ul#notifos (map-bound (partial notifo this) notifos)])) (object/tag-behaviors :editor.markdown [:eval-on-change :set-wrap])
where can find clojure code uses style , composition principles?
bot sounds light table "proprietary" flavor of entity-component-system (ecs) architecture. start wikipedia entry , go this post code examples in actionscript (we in world of games).
there some examples in clojure context.
Comments
Post a Comment