This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-05
Channels
- # architecture (2)
- # aws (1)
- # bangalore-clj (4)
- # beginners (97)
- # boot (35)
- # cider (8)
- # cljsjs (3)
- # cljsrn (35)
- # clojure (190)
- # clojure-dusseldorf (4)
- # clojure-italy (7)
- # clojure-poland (1)
- # clojure-russia (17)
- # clojure-spec (74)
- # clojure-uk (30)
- # clojureremote (2)
- # clojurescript (298)
- # code-reviews (18)
- # component (18)
- # cursive (18)
- # datascript (3)
- # datavis (2)
- # datomic (24)
- # dirac (17)
- # emacs (3)
- # garden (7)
- # hoplon (51)
- # jobs (2)
- # jobs-rus (2)
- # leiningen (4)
- # luminus (11)
- # mount (24)
- # off-topic (1)
- # om (32)
- # onyx (25)
- # pedestal (1)
- # powderkeg (9)
- # protorepl (6)
- # re-frame (11)
- # reagent (15)
- # spacemacs (6)
- # sql (35)
- # uncomplicate (1)
- # unrepl (74)
- # untangled (130)
- # yada (6)
^^ pls try this out! [hoplon "7.0.0-SNAPSHOT"]
we made a change that dramatically increases performance
cc @jumblerg β«
it should help a lot with initial loads
@alandipert: already on it!
in our little test app, adding 1000 li
s to a ul
went from 5000ms to ~30ms
i also love that we just skipped hoplon 6. seems appropriate, it was getting kinda like perl.
lol yeah the -alpha business
onward and upward
^ stoked for this!!!
@ejemba in that example get-state is run and then again every second
https://github.com/hoplon/demos/blob/master/castra-simple/src/app/rpc.cljs#L17-L19
@alandipert any other breaking changes you can think of that may want to go into 7?
i don't think so
Woot!
also this latest change shouldn't be breaking
So I have been working on a project, itβs still WIP and there is little code available but I will be launching this at an upcoming conference; https://github.com/degree9/meta
Opinions welcome π
hm - did we never fix nil
children stopping appends?
i forget where that landed
https://github.com/hoplon/hoplon/issues/159 - still in play
^^ removed because it made hoplon task 6x slower for our app
hm i think we can actually keep it, it just shouldn't be used by hoplon task by default maybe. anyone use it/like it?
Agreed. I used it for a bit but now I never do. Just use ns with hoplon/page metadata when necessary
i use the page macro and will for the foreseeable future, because our massive app uses it
and i use it for experiments, because the template does lol
but not using it is a pretty good idea too i think
for anyone listening in this looks like:
(ns ^{:hoplon/page "index.html"} mybiz.application ...)
i'm thinking about documenting it though. and it's the thought that counts, they say.
i'm down to just switching over to it wherever we have examples
at least, in the immediate docs and templates
a cool thing about that is people could use the hoplon task together with reagent or whatever
to be rid of .html stubs
π π not worthy
For a for-tpl
structure to edit element values in the UI:
(let [data (cell [1 2 3])]
(for-tpl [x data]
(elem :click #(swap! x inc) @x)))
As I understand it, x
is formula cell that carries the value of part of the data
sequence. So by default it does nothing to the data
cell. And x
is not reset!
directly. Instead you update the underlying value in data
.
What is the idiomatic way to get the new values for x
to use in other components? Like perhaps a formula cell that contains all the updated x
values for data
?@alandipert Can I suggest that we abstract the boot-hoplon dsl stuff out? I think it is both convenient to be able to build your own dsl and confusing for Hoplon users how much magic is being done with the .hl files