htmx

Just want to be able to have the response, modify it as a dom node, before it is processed and eval'd

If you dig through the code base (it isn't that big) and you find a spot you want a new event, I'm happy to add it

seems like maybe an event here: https://github.com/bigskysoftware/htmx/blob/a5a290809c734a32e031ebb6421572bdfcbb77f7/src/htmx.js#L252

I write pretty basic, if idiosyncratic, javascript

what is the advantage of this over `python3 -m http.server 8088`?

trying oob method
thank you so much and sorry for overlooking that
I am migrating for intercooler and thought I was smart enough to not read all docs 😛 my bad

Thank you, I will try this and create a GH issue

<@!725789255590215732> Looking at things for a little while, I am feeling like what we are really trying to do is manual oob processing of the content returned from the server. Just like a top level oob dom element can be returned, we instead want our javascript to process that node (currently a template tag that contains scripts and styles that will be tracked and injected into the head or bottom of the body of the page) instead of having htmx try to oob swap the element via it's ID.

Maybe we could allow a custom oob swapper?

Heading to bed, but for now, we are just going to use `transformResponse` and do our processing there, but will think about it more tomorrow.

I suppose the order of the oob swaps would be important for us though. We need to swap in out scripts and style tags before any other oob or normal swaps.

OK, sounds good.  If you can give me more context I can think about it to and we can come up w/ the best way to handle this, make any changes we need and document it.

<@!344701259024039937> I added some oob events recently - https://github.com/bigskysoftware/htmx/pull/667 - could you use those?

can I somehow use the settle and swap modifiers on oob swaps?

solved my issue using class-tools instead, but the question stands I guess

<@725789255590215732> I have a very blunt question: do you really see htmx as a sort of HTML6?

Because I like to introduce this project in a very heavy opinionated way, like: "hey guys! HTML6 has come! Go check it out!"

I thought WTFWG or whatever they're called went all "living document" on the standard

🙂 I think htmX is probably arrogant enough

remember when we went to wicg and said "make our framework a web standard plz"

But, conceptually, I hope htmx is a reasonable potential future direction for HTML