andrewzhurov / brawl-haus Goto Github PK

We've got editor fields: hiccup, garden
And result fields: compiled hiccup, compiled garden, render

👿 Problem is: components inherit styles,
e.g. editors use class .collection, which also comes with materialize.css
e.g. render would inherit and we would not get pure Garden compile result to be our styles

😈 Desired behaviour: components get their own clean boxes

For writing view people would need to know:
Simple and enough:

• basic clojure (at least data structures: vector, keyword, map)
• hiccup syntax
• garden syntax
  Complex, for thick client logic:
• reagent
• re-frame

So for a start we'd go with pure Clojure material
Material would be in format: theory, tests, practice
🤔 integrate theory in practice - one editor field with eager evaluation, theory as comments
😮 we can integrate tests in a fashion:

;; Lisp is a family of languages, having one characteristic in common:
;; :homoiconicity - language constructs we write and underlying AST presentation being the same...
;; :logical - ...
;; :easily-scaled - ...
(answer-a :easily-scaled) => {:result false :description "It's not necessarily, many languages have this trait, though you would know on the spot they are no LISP :), e.g. Erlang. It's about something else..."

Need to move names.txt from public directory to another place. This file used on server side.

Place oriented approach, where we re-write the same cell of memory with new value
vs.
fact oriented approach, where all that happens are facts (data + point in time) and when something had changed - it's a new fact, it doesn't revoke the previous one.
E.g.
Fact1: Message added at time T1, with text X1
Fact2: Message edited at time T2, text now X2
Those two do not collide, they coexist.

So we could demonstrate this approach with 'message edit' feature:

1. give ability for author to change content of message
2. keep/log all those revisions of a message
3. in UI show latest revision
4. in UI give ability to inspect all revisions

E.g.

Make local Clojure environment setup easy

Current approaches I see it can be done:

• set locally via ansible config (it's how I set things for my Ubuntu 16.04)
  https://github.com/andrewzhurov/ansible_local
• develop inside a Vagrant box (thx @char16t for suggest)
• develop inside a Docker image

I think local setup prevails because of:

• simple (less tools/abstractions)
• comfort (speed, GUI environment)
• already done, but need polish
  Cons:
• no Windows support

Polish contributions and other UX suggestions are in need!
We could capture a vid on this topic also

Use query-string to represent position details, no place-semantics a-la
/patient/323abc/edit
go for
?resource=patient&patient-id=323abc&tool=edit
It's labeled format, so no need to go look routing cheatsheet and parse semantics in your head

Hickey talking about 'place semantics are evil':
https://www.youtube.com/watch?v=2V1FtfBDsLU&feature=youtu.be