This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-17
Channels
- # announcements (2)
- # asami (3)
- # babashka (30)
- # beginners (23)
- # calva (28)
- # cider (3)
- # clj-kondo (16)
- # clj-on-windows (7)
- # cljs-dev (7)
- # clojure (47)
- # clojure-austin (3)
- # clojure-europe (25)
- # clojure-gamedev (3)
- # clojure-greece (1)
- # clojure-nl (1)
- # clojure-uk (3)
- # clojurescript (54)
- # community-development (24)
- # conjure (16)
- # duct (1)
- # emacs (8)
- # events (1)
- # figwheel-main (4)
- # fulcro (13)
- # gratitude (20)
- # helix (3)
- # honeysql (8)
- # hyperfiddle (12)
- # introduce-yourself (1)
- # jobs (6)
- # lambdaisland (1)
- # lsp (23)
- # malli (1)
- # meander (27)
- # minecraft (11)
- # off-topic (12)
- # pathom (1)
- # portal (11)
- # releases (1)
- # remote-jobs (1)
- # ring (11)
- # sci (1)
- # shadow-cljs (53)
- # specter (5)
- # xtdb (20)
fullstack web view with query/view composition and render, database on server. With stable hot code reloading
lines 55 and 56 both use ~@
but we're not in a backticked form. I guess you're reusing the operators in p/defn
compiler for something?
~@ outside of ` is the current syntax for client/server transfer, we have not gotten to implementing the better (p/client) syntax yet
you mean the p/client
and p/server
code samples you showed where wishful thinking?
To communicate clearly the talk uses our target syntax as the ~@ was a mistake and is not readable, we should have the good syntax soon
should I read it as a toggle? Like toplevel starts as cljs, first ~@
toggles to server, next ~@
toggles to client again?
yes it's a toggle currently
understood, thanks
My colleagues want a quick demo of photon. I improved the webview example with state-preserving hot-reloading of the server db.
I had to wrap the reader conditionals in e.g. do or let
exprs, otherwise e.g. defonce
thought I passed it only 1 arg, the name conn
.
(defonce conn (let [c (do #?(:clj (d/create-conn {:order/email {}})))]
#?(:clj (d/transact! c [{:order/email "" :order/gender :order/female}
{:order/email "" :order/gender :order/male}
{:order/email "" :order/gender :order/male}]))
c))
I tried defonce
-ing the !state
atom of the client too, hoping that the input would preserve its email filter value. No luck there.
Anyway this'll already be a very nice demo!
@U2DART3HA I think I should ping you about this small improvement to the demo(s).
If you didn't get what I mean by all this, I'll screencast a 1 minute demo for you, showing before & after the change.
Understood, will push the fix in a minute
Will pull in days, unless other interesting stuff surfaces. 🙂 No urgency but thanks a lot!