Fork me on GitHub
#fulcro
<
2021-02-07
>
tony.kay05:02:06

I’m starting a new Playlist on YouTube titles “Grokking Fulcro”. This is a dual-purpose video series: • Help existing Fulcro users understand the low-level details. • Show common patterns. Fulcro does things differently than people expect, so knowing how to “think” about common problems requires some shifts that people often struggle with. • Expose people less familiar with Clojure(script) to some of the superpowers you gain by using it. First video just dropped. Here’s the playlist: https://www.youtube.com/watch?v=3dZK5seIaVI&amp;list=PLVi9lDx-4C_TBRiHfjnjXaK2J3BIUDPnf&amp;index=1&amp;ab_channel=TonyKay

🎉 22
💯 11
🚀 10
❤️ 9
bananadance 4
grzm17:02:40

Are there any concrete examples of websocket push-handlers around? I’m leaning towards figuring out a way that the data provided by a push is in the same shape as a mutation with targeted return values (https://book.fulcrologic.com/#ReturnValues). Does this seem reasonable? I’d like to see what others have come up with.

tony.kay18:02:11

That is exactly the plan you should have.

grzm18:02:18

That’s reassuring!

tony.kay18:02:19

In developing your push messages, include an indicator of what component (name in the UI component registry key?) should be used for merge. Then it’s just merge-component!.

tony.kay18:02:09

creating edges (targeting) is also something you’ll need to decide on…perhaps generalizing that to something in a UISM actor model?

tony.kay18:02:31

then your messages could be much more generic and not tied to the UI, and the actors in the UISM could provide what you need.

tony.kay18:02:56

there’s, of course, some coupling of knowing what to push from the server and having that macth UI expectations.

tony.kay18:02:06

yeah, that’s UISM

tony.kay18:02:18

see book chapter

grzm18:02:22

Yeah, I’ve been trying to suss out what the minimal coupling would be.

tony.kay18:02:58

I think UISM is a good match, actually. There’s probably not many “states” to it, but the generalizations UISM allows for hooking in “actors” is handy.

👍 1
grzm18:02:57

I’ve been leaning more and more towards thinking that state machines are the end state of decoupling.

grzm18:02:10

I’ve read you mention elsewhere that you have a couple of production systems out there using websockets. I can understand not being able to share that code. Do you happen to know of some examples that are available to look at?

tony.kay00:02:27

I use them very much like a normal remote most of the time. Most of the systems I work on don’t need much from the push side. A few select features/screens. No, I don’t really have any public examples I know of that use them extensively.