This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (11)
- # beginners (16)
- # boot (171)
- # cider (1)
- # clojure (31)
- # clojure-france (2)
- # clojure-italy (3)
- # clojure-korea (12)
- # clojure-russia (1)
- # clojure-sg (4)
- # clojure-uk (3)
- # clojurebridge (3)
- # clojurescript (52)
- # code-reviews (1)
- # datomic (1)
- # editors (3)
- # events (1)
- # jobs (13)
- # ldnclj (3)
- # reagent (6)
- # sneer (1)
the readme file says "This is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google."
nikolap: maybe they wrote it on a laptop owned by Google! reminds of the last episode of Silicon Valley
Counterclockwise has great syntax-highlighted REPL / editor support if you are an Eclipse user.
what is the most efficient way of swinging between Clojure vector and Java array?
I was wondering if anyone has written down advice on code organization of a typical clojure web application (compared to a standard Rails app with models, services, config, etc)
this seems an interesting video about it http://www.infoq.com/presentations/DDD-Clojure
great for acknowledging that you need a good place to put this thing but you’re not sure where right now
he mentions 'domain' should be pure. In the context of a simple crud app, domain would be almost empty then I guess.
@borkdude: I don't think there is any standard (which isn't great imo). I can describe how Yeller's webapp is organized, but I ain't particularly happy with it 😕
@tcrayford: I'm always interested to hear it. Every app I've built is different and I'm always searching to improve the structure.
@borkdude: so roughly the whole thing is in
src/yeller/web. Everything's flat inside there. There's one "main" namespace:
yeller.web.routes (that contains all the compojure routes), and one supporting thing for that,
yeller.web.middleware. Then each "part" of the domain has several namespaces:
yeller.web.invite_handlers (for ring handlers),
yeller.web.invite_views (for stuff that renders into html),
yeller.web.invites (for any logic that isn't strictly to do with HTTP)