How can I do a binding with shadow cljs?

https://github.com/roman01la/cljss/commit/ef661a5d29356ff97e2e07b75af48fc06c876d53#diff-56b26c1ab3f7c730b3d264bf99467f74R179

same way it is done there

https://shadow-cljs.github.io/docs/UsersGuide.html#clj-run

(defn foo [] (binding [x y] (shadow.cljs.devtools.api/compile :the-build))

might have to disable caching though

Ok. I was avoiding clj-run and leveraging build hooks.

Could I wrap the build-state of a build hook with it?

no

hmm yea just took another look and realised

So the dynamic variable binding should be avoided to keep it to build hooks and keep caching then?

no idea. i don't know what cljss does

it looks like it doing a bunch of side effects in macros

and that seriously breaks with caching enabled

Yea this is the SSR implementation being worked on.

I'm looking to leverage it in shadow-jam and just figuring out how I can leverage that SSR.

I probably need to have a closer look at the caching situation then as well because I perform image manipulation and generate multiple image files in macros.

don't do such things in macros

ever

There isn't really any other way for me to perform it from what I can tell.

It's the macro I use here. https://github.com/groundedSAGE/shadow-jam/blob/master/src/routes/index.cljc#L14 that I am referring to.

there are plenty of ways. they just might not be documented too well

Allows defining a source image and other details which it then uses to grab image, collect certain metadata, use that metadata to figure out data required for the html markup and generates corresponding assets.

so the basic misconception I see it that you think everything has to happen in the macro

it doesn't have to happen in a macro at all

thats the fallacy with starting with a macro in the first place

so lets imagine this without a macro at all

you have want to achieve [:picture [:img {:src "some.jpg"}]]

I thought it through and discussed with others and apparently macro was only way. I try and avoid macros as I know the objective is data > fn > macro

where the PATH to the image is "replaced"

so you instead call [:picture [:img {:src (your.lib/get-path "some.jpg")}]]

you then of course want responsive versions

[:picture [:source {:srcset (your.lib/get-path "some.jpg" :small) :media "..."}]] [:img {:src (your.lib/get-path "some.jpg")}]]

so then the question becomes what get-path looks like

its a function

so it can take data from everywhere

so lets suppose there is a global "myImages" variable

(defn get-path [img-name img-variant] (goog.object/get js/myImages img-name (name img-variant)))

now the question is how do you get the info you need for myImages

a) generate it statically since you know which images you have and then append it to the final build output

It's actually

[:picture [:source "various responsive sizes"] [:source "the same thing again but fallback image format"] [:img "the image again which contains more metadata and fallback"]]

thats what I just posted above

Ah yes slow typing. Apologies.

the other option is to actually employ a macro but only store which images where accessed and which variants

so you can extract that in a build hook

so basically the concept is to use a helper function that can return data that was not part of the CLJS compilation at all

and then append it to the final build output instead

or pass it to the build by any other means

in my experience image processing too much is actually a problem in the long rum

sometime you don't just want to use the same image in different sizes

sometimes you want a big one and a small cropped one (instead of the whole area)

sometimes the smaller one is completely different

building a system that can generate all the images you want into a macro is just gonna be painful to use for everyone

I kind of see what you mean with the helper functions. For me right now the macro seems easier to grok. I'm just working to bring this up to a gatsby like experience (through stealing ideas) then hopefully people with more dev chops can chime in and help me polish it lol.

so then steal how they deal with images

they don't have macros either

I've print screened your explanations. Brain a bit foggy as is late here now.

I'm a bit too busy with other stuff but hooking image processing and scss into shadow-cljs is on my list

just won't be part of normal compilation and a plugin of sorts instead

probably not going to touch ssr though

I'm interested to see your image processing implementation when done and see how much more I have to learn 😛

well I'm just going to take whatever tools already exist

make them generate some edn/json data

and then concat that into the build

done

right now my image processing is a .sh file with a bunch of convert img.jpg other-image.jpg