How do you guys write body text in reagent templates?

Anyone know a way to have, e.g., inline Markdown?

I've done it where i convert markdown to html then use dangerously set inner html https://facebook.github.io/react/tips/dangerously-set-inner-html.html

Also, here is a recipe with a link to a blog post about markdown. https://github.com/reagent-project/reagent-cookbook/tree/master/recipes/markdown-editor

Oh, I mean something much more prosaic. Reagent’s semi-hiccup is nice for structuring the page, but rough for formatting text I’m writing in templates. I’d like to avoid [:p “Template syntax like “ [:strong “this”] “!”]

something like [:p (markdown “Template syntax like *this*!”)] would be wonderful

@tel: Not reagent - but you might learn something from looking at the hoplon code — they use markdown extensively in some of their demos : https://github.com/tailrecursion/hoplon.io/blob/master/src/index.cljs.hl#L96-L104

@tel - here is the macro they use : https://github.com/tailrecursion/hoplon.io/blob/master/src/util.clj#L26-L33

So looks like they are processing the MD as part of generating the code — and not processing on the clojurescript/client side.

yeah, that’s clever

and sort of wild

is there an xml->reagent function floating around anywhere?

I'm not sure, but hickory might be of interest - html to hiccup

Figwheel-reloadable local state in Reagent: http://vvvvalvalval.github.io/posts/2015-09-16-bottup-approach-to-reagent-state.html

@jaen: what did you find hard about hooking into dispose in Reagent?

I'd have to go over the code again, it was a while ago, I can get back to you with more details later-ish, after I go read that code again, if you want. But basically I wanted to have reactive query objects - I do (logic/query [:some datascript]) and get back a reactive object that forces re-render when the output of query changes. To do that I had to register datascript callbacks via d/listen! and to not have this grow in an unbounded manner I would have to hook unlistening on when the reactive query gets disposed on component unmount.

@jaen I’m working on something veeeerry similar with RethinkDB

What we did was to create a Reaction off the Ratom, and add an :on-dispose key in ratom/make-reaction. When Reagent detects that the reaction isn’t being watched anymore it will call the on-dispose that cleans up the parent ratom

So I kind wrapped everything in a reaction, but I must have missed the :on-dispose key

If that works then maybe I can keep using reagent

Also, isn't rethinkdb server-side?

Yep

But same principle

Interesting

It’s a little tied into re-frame, but none of it is re-frame exclusive

In general this feels like a good direction, some transient local state and automagic synchonisation of perrsistent state between the frontend and backend.

I didn't use reframe, but what I wrote was for myself was basically guided by reframe readme ; d

I figured maybe I'll better understand it that way

meteor has some significant prior art there

@jaen: You're re-running all queries whenever the db changes?

Yes, I don't think I did anything significantly smarter than that

@jaen: If I'm understanding that means that any part of the UI that depends on those reactive queries re-renders on any db change, right?

@zane only if the query actually changes, Reagent won’t update otherwise (modulo identical? vs = checking)

Got it. It'll fall back from identical? to =, you mean?

https://github.com/Day8/re-frame/wiki/When-do-components-update%3F

Not sure if @jaen’s queries/datascript will return results from a query that are identical?. If they are then Reagent won’t update, if they’re not identical it may. Depends a little on how it’s being used, I’m mostly familiar with re-frame’s pattern. More info in above link.