How do you generate this url? 'build-static-app' generates a html file. Why not just use absolute url?

not supported yet. So you'd want a equivalent of :deps/root?

or :git/root, makes sense. Issue and optionally PR welcome

I've created an issue and PR for this, sorry for the delay in doing this https://github.com/nextjournal/clerk/issues/99

Now it's like:

(some-form 1 2 3)
;; result
(another-form 1 2 3)
;; result

What about this?

(some-form 1 2 3)
(another-form 1 2 3)
;; first result
;; second result

do you have an example where that would be desired?

For example here:

I think block of code lines + block of results would be better here. It can be my personal feeling though

Here are some examples from other docs:

Thinking aloud: I think it's a matter of more compact view and/or ability to overwrite certain styles.

also something like in RMarkdown:

Similarly in Jupyter:

in the jupyter example it’s showing stdout & err (which we don’t yet show in Clerk)

you can do this today:

(clerk/with-viewers
  [{:pred vector? :render-fn '#(v/html (into [:div.flex.flex-col] (v/inspect-children %2) %1))}
   {:pred #(and (string? %)
                (re-matches
                 (re-pattern
                  (str "(?i)"
                       "(#(?:[0-9a-f]{2}){2,4}|(#[0-9a-f]{3})|"
                       "(rgb|hsl)a?\\((-?\\d+%?[,\\s]+){2,3}\\s*[\\d\\.]+%?\\))")) %))
    :render-fn '#(v/html [:div
                          [:div.inline-block.rounded-sm.shadow.ml-2
                           {:style {:width 16
                                    :height 16
                                    :border "1px solid rgba(0,0,0,.2)"
                                    :background-color %}}]
                          [:span.font-mono.text-xs.ml-2 %]])}]
  ["#571845"
   "rgb(144,12,62)"
   "rgba(199,0,57,1.0)"
   "hsl(11,100%,60%)"
   "hsla(46, 97%, 48%, 1.000)"])

(return a vector and modify the vector viewer to render elements vertically)

mhm... (with jupyter, I wanted to show that several froms can be combined to get forms block + results block, instead of interleaved view)

I know that vector is possible but requires smart dispatching code.

It's a feature request from my side 🙂

what do you mean by smart dispatching code?

I mean I have to write another function for seqence of colors/palettes/gradients. Or add some logic to my viewer function (🎨)

I don’t yet see how we can automatically do it… We need some way to signal that it should render multiple results?

Maybe double newline can be an indicator to render a block?

(code 1)
(code 2)

(code 3)

(code 4)
(code 5)

this could be rendered as 3 blocks

Anyway, that's just an idea. I'm aware that's a breaking change request but maybe there can be an option to set by user to choose the method of block vs line-by-line rendering.

still would like to understand a bit better what you don’t like about the vector option?

I'm not saying I don't like 🙂 I need to write a piece of code which will render it properly. That's all.

Oh, it works now almost ok (need to get rid of [] at the beginning)

yes, that’s what I mean

(clerk/set-viewers! [{:pred vector?
                      :render-fn '#(v/html (into [:div.flex.flex-col] (v/inspect-children %2) %1))}])

another possibility would be for us to add this as a default named viewer to Clerk, then it would be selectable via metadata like this

(clerk/set-viewers! [{:name :flex-col
                      :render-fn '#(v/html (into [:div.flex.flex-col] (v/inspect-children %2) %1))}])

^{::clerk/viewer :flex-col}
[:one
 :two
 :three]

ok...

So another minor issue: is there a way to get rid of meta tag?

yes, been talking to @U07SQTAEM about this and we want this as an option as well.

Great! Thank you for taking your time for that.

I’m a bit concerned about adding it too soon though because then it’s no longer obvious how to do some of those things. @U4FSZE57V maybe we find a elegant way to unhide it on demand.

What about making such switches/options as a meta for namespace?

Like global no-cache?

(ns {^:nextjournal.clerk/options #{:no-cache :hide-tags :some-other-option}} notebooks.color)

yeah, possible. (Btw think we also want to move those options out from the namespace to the form ^:nextjournal.clerk/no-cache (ns notebooks.color notebooks.color) )

that's even better

We've been thinking about this too, @U1EP3BZ3Q. But our approach with Clerk is the opposite of "move fast and break things", where we really want to make sure that everything fits together well to give the most power with the least API surface. 🙂

Ha! I'm the last person who expect moving fast and breaking things 🙂 Just sharing my observations and conclusions, which are subjective for sure but may be helpful (I hope).

I just meant that we're listening and trying to meet everyone's concerns, even if it seems like we're a bit slow shipping a solution or we don't take someone's pull request as is. 🙂