Fork me on GitHub

I am lost too about what happens on the browser and on the server.


The auto refresh of the fiddle seems magical to me. I do not see any web socket, long poll or any kind of communication between the client and the server except when it is the time to refresh


The new tutorials are very nice. I start to feel comfortable with displaying data. But I am still struggling at inserting data.

Dustin Getz01:09:19

@didiercrunch hyperfiddle.jar is coded in CLJC so the client/server boundary is not hard and fast, the I/O implementation is swappable. For example: REST vs websocket, server rendering vs client rendering. The way the IDE currently works is everything you type is staged — popovers get a hidden "branch" stage — and HTTP POST to the server, which applies the stage with datomic.api/with, and then runs any queries that need to update. It is very chatty but its fast enough for development. Prod is different, because 1) security 2) performance, so it is (or will be) basically like a normal REST app.

Dustin Getz01:09:09

@didiercrunch I'll write up a tutorial for CRUD ops next, also see this:

Dustin Getz01:09:41

On that page, toggle between data and view to get an admin interface (which is a default set of links)

Dustin Getz01:09:21

@spacemods Thank you. By magic fields do you mean hyperfiddle.ui/hyper-control, or did you mean the splat field, or something else?

Dustin Getz01:09:21

@spacemods The "markdown blog" tutorial got bad feedback so i tossed it, but there is a very basic blog here and of course

Dustin Getz01:09:17

@spacemods "Until I can fully design/think in terms of the abstractions, I'm still figuring out exactly what effect each bit of UI/link/query has on the frontend/backend, especially for the "magic" fields/forms/tables." I am going to think about a good way to describe and present this, thanks for the question

Space Guy21:09:50

For 'magic fields', I'm thinking of hyperfiddle.ui/[field, table, form, hyper-control, result, pull, ...] - all of them react to the query + links, especially for interactions like hyperfiddle.ui/field [:neighbourhood/district] expanding into nested forms/fields. I can see each part in ui.cljs but it'll take more time to follow what a complete view is doing