For those who don't use TailwindUI, dev tools will not allow you to get the code for free. They have free examples that you can use, but the rest is behind a paywall. I bought it pretty early in its' development and it's been a great investment. Highly recommend. I really like the combination of HTMX+Tailwind. Works like a charm.

Nice

Me too

But yeah tailwindui are just examples and without their library headlessui, it’s more an inspiration than something else

So yeah if I were you, I would write headlessui components like in hyperscript but with another name. Like hyperui lol

Yep, that sounds like what I'll do. I'll get back to you when I have something going. Thank you for your input!

+1 for hyperui haha

Np 😉

@User I both paid for TailwindUI and am currently using alpine js, where in dev tools do I need to look to see what they're using in Alpine JS?

ah ok I believe I've found it

@User in case you haven't found it, here's a good example.

this section of the doc also has a good one: https://tailwindui.com/documentation#html-dynamic-classes

are you referring to the dev tools elements tab and then using the element finder tool?

i am referring to right-clicking the button whose transition i want to see and choosing "Inspect" from firefox's context menu. that highlights the node in the inspector, where i can see the scripts attached to it

so the thing highlighted in the blue square is what i was just right-clicking and inspecting

yeah and then looking at this to see what they did with alpine to achieve it?

yep

they used to include some alpine-focused instructions, but i can't find that anymore other than the doc section i linked

yeah this is a good note, thank you

@User Yep @User is right. That's how I do it.

so Ive got an initial form that is just a select drop down with 3 choices. Each one of those 3 choices should cause a different form to render right below the drop down. So basically if they pick option A, then right below the drop down they get Form A, if they pick option B from the drop down then they get form B and so on. Any recommendation on how to tackle this? Mainly wondering how the view should be handled...I've got the select dropdown setup such that its trigger="changed" so that works great for sending a request everytime the user selects a different option. Should this be two views, one for the select dropdown and one for handling the other form? I'm doing FBVs for this

arg, super close. When I change the select from the default of --- to an option it loads the new form correctly, in the correct spot. But when I swap it back to --- it actually nests the entire page within that id instead, lol :x

inception haha

ah ok I think I got it

Instead of the second select, you return a whole form

And then when you submit, you submit the value of your first choice and then you handle the three cases if your view

thats actually exactly what I ended up doing. I ended up with a view for the main select form, and then one view for each of the options. Maybe not necessary but it reads really cleanly

Nice

Hi all, I am just beginning to learn HTMX and have a issue with changing an image for an icon when an item is bookmarked. The logic in the back end is working with Django but I am not sure how to return a response correctly for this.