How are you using shadow-cljs ui

[jacekschae]

After reworking shadow-cljs ui some time ago I think it's time to take a next step and introduce dark mode.

Any comments / recommendations are more than welcome!

[jacekschae]

What is your setup when you develop front end / mobile apps with shadow-cljs -- could you please share your desktop setup? I'm looking into working on the dark mode but thought maybe it would be better to understand what is the layout that people normally use. Do you use shadow-cljs ui do you look at the console?

Thanks for sharing 🤗

Here is an example from a laptop:

[p-himik]

Not sure how useful this data point is, but FWIW I don't really pay attention to that UI. I check the terminal output of shadow-cljs and go from there.

[mjmeintjes]

I use the "Inspect Stream" a lot, and also the "Force compile" functionality sometimes.

[jacekschae]

Not sure how useful this data point is, but FWIW I don't really pay attention to that UI. I check the terminal output of shadow-cljs and go from there.

Thanks for sharing @p-himik I think it is useful. I assume you are not using tap> and mainly console.log.

@mjmeintjes same for see I feel like inspect stream is the most important -- thanks for sharing.

[p-himik]

Your assumption is correct @jacekschae. I do use tap> on the CLJ side, but on the CLJS side I prefer js/console.log, mainly because I need to work with JS objects rather often, and staring at #object[Object] is not helpful. And with cljs-devtools, I can inspect CLJS objects in my browser's console just fine.

[thheller]

@p-himik note that the Inspect UI uses datafy. so if you are working with a lot of custom JS classes you can extend the relevant protocols do display them in a nicer fashion. Example. console.log is in the browser is nice too of course.