This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # alda (1)
- # aws (4)
- # boot (276)
- # cljs-dev (3)
- # cljsjs (1)
- # cljsrn (3)
- # clojars (22)
- # clojure (174)
- # clojure-austin (1)
- # clojure-italy (2)
- # clojure-russia (20)
- # clojurecup (1)
- # clojurescript (233)
- # cursive (4)
- # datavis (97)
- # datomic (122)
- # hoplon (80)
- # ldnclj (8)
- # leiningen (6)
- # om (82)
- # reagent (10)
- # spacemacs (8)
- # specter (5)
@micha Hope you like the change to Javelin. For some reason, I could not create a pull request using the github windows tool. Perhaps because I already have project write access--I'll need to check.
All I did was replace the first paragraph on lenses and added a reference. Easy enough to revert.
Pull requests can only be built for a branch, it looks like: https://help.github.com/articles/creating-a-pull-request/
I'm thinking that for more extensive changes then I should just create a branch that can be merged in later.
@micha If I go here, I get a brief description of each project: https://github.com/hoplon But if I go here, I get no descriptions of the demos: https://hoplon.github.io/demos/ My first thought is that we should be pulling the descriptions out of the build.boot files. But there are none! I'll note that project.clj carries a description, but boot.build does not. Is this a boot template issue? Or a deficiency of boot???
Perhaps we can just add a :description to boot.build. Would it work with https://github.com/boot-clj/boot/wiki/For-Cursive-Users
In any case, I think it important to have a description of each demo on this page: https://hoplon.github.io/demos/
@micha I tried putting :description in a build.boot file and everything looks ok. More to the point, the description is added to the project.clj file generated by "boot lein-generate"
yeah you can have a function in your build.boot that outputs any kind of data file of course
And I'd be more than happy if you did the "easy" part of extracting the description for the web page
which is why I was thinking it better to put the description in the build.boot for each demo
i think instead of making that index html page we should just use the wiki or something and link to the demos
@micha I just had a great idea for a project. Though likely you may have already thought of it. --Connect a javelin lens via castra and notify to a database lens. Wow!
we have been intrigued by ideas like that, we call the durable cell "the stem cell"
I like the idea of connecting models with the underlying reality. Now you can have a value displayed on a page which reflects the current value in the database AND changing that value updates the database. Makes the display very "real". Virtual reality meshes with reality and all that.
i've found that it's important to completely decouple the view over the state, that is to say the representation of the state, from the semantics for updating the state
usually in my experience the application state is not like a register where you fetch and store values
usually there are side effects involved and the view over the state that the application sees is only a small part of it
i suppose what i mean to say is that it only makes sense for certain parts of the state