egil

egil, 10 days ago

@khalidabuhakmeh @jonstj Htmxor is definitely not production ready, but things are heading in the right direction. Beta level stuff. Still breaking changes coming, most likely 😊

egil, 10 days ago

@khalidabuhakmeh @brtkdotse do it in Htmxor too and let me know how it feels 😏

egil, 10 days ago

@khalidabuhakmeh @brtkdotse that would be amazing (was mostly kidding). Looking for a project at work I can try this on, for now though, I'm just imagining things. If you want to do it together on a stream or async just let me know.

egil, 10 days ago

@khalidabuhakmeh @jonstj speaking off issues, a generic approach to controlling any response header could look like this in Htmxor: https://github.com/egil/Htmxor/issues/18

egil, 10 days ago

@khalidabuhakmeh @brtkdotse great. I am hoping it is fairly intuitive experience given that you followed the getting started guide to set up the project or cloned the minimal app project. But if you share a link I would love to see where you ended up 🙂

egil, 10 days ago

@khalidabuhakmeh @brtkdotse starting with this is probably the easiest, also includes some sample components and pages: https://github.com/egil/Htmxor/tree/main/samples/MinimalHtmxorApp

Otherwise check out the docs: https://github.com/egil/Htmxor/blob/main/docs/index.md

Re. reviewing in a stream, I'll be happy to do that any time next week.

egil, 10 days ago

@khalidabuhakmeh @brtkdotse I will have a go at doing an "egils version" ASAP and report back!

egil, 5 days ago

@khalidabuhakmeh @brtkdotse gah, other things keep coming in my way, but Khalid, you can use @onget htmxor event handlers instead of "doing everything in OnInitialize", that will make it feel more like a Blazor component. For example: https://github.com/egil/Htmxor/blob/main/samples/HtmxorExamples/Components/Pages/Examples/ArchiveToggle/Index.razor#L45

egil, 2 days ago

@khalidabuhakmeh @brtkdotse here is a simpler version that I think addresses some of your concerns: https://github.com/khalidabuhakmeh/HtmxorTodoApp/pull/1

egil, 2 days ago

@khalidabuhakmeh @brtkdotse I like the trick with having a form elsewhere in the page and targeting it with form="formId" to get around having forms in table rows. An alternative I've used is hx-include="closest tr" as demo'ed here: https://htmx.org/examples/edit-row/

egil, 2 days ago

@khalidabuhakmeh @brtkdotse that's right. In terms of fallback, I also need to ensure that the htmxor specific event handlers works in fallback scenario, as blazors standard form post do.

egil, 19 days ago

@khalidabuhakmeh @alexzeitler currently I lean towards:

• If something can be a component that makes sense on its own, then, by all means, make it that. Then you can decide if it's a routable component or just a component that's used by other components.
• If something only makes sense in the context of a component, but you still want to update it individually, then leveraging the template fragment pattern makes sense.

More detail in my answers here: https://github.com/egil/Htmxor/discussions/39

egil, 21 days ago

Nerd sniping @khalidabuhakmeh 😘

egil, 21 days ago

@khalidabuhakmeh my example matches on a route, but the the point of a fragment is that it does not make sense on its own, otherwise, it may just as well be a routable component.

Here is another example where the fragments choose to render or not, based on request headers.

https://github.com/egil/Htmxor/blob/examples-project/samples/HtmxorExamples/Components/Pages/Examples/UpdatingOtherContent/TriggeringEvents.razor

This is the article that inspired the whole endeavor: https://htmx.org/essays/template-fragments/

So for me, making an fragment addressable does not make much sense as I see it.

egil, 21 days ago

@khalidabuhakmeh in terms of routable components, this is my first attempt at docs for how Htmxor does routing: https://github.com/egil/Htmxor/blob/main/docs/routing.md

egil, 1 month ago

@brtkdotse @khalidabuhakmeh well ok, still prototyping, so “I hope it will” solve all the things is probably more precise 😊

egil, 1 month ago

@brtkdotse @khalidabuhakmeh @patriksvensson the headers I have a solution for 🙂

egil, 1 month ago

@patriksvensson @khalidabuhakmeh @brtkdotse yeah I have looked at your stuff too. Have a custom HtmxContext that has a HtmxRequest and a HtmxResponse properties that provides access to incoming and outgoing headers. The context can be accessed in components. That's my best solution for now.

egil, 1 month ago

@khalidabuhakmeh @patriksvensson @brtkdotse something like that is almost possible. Cannot do custom directives until the razor compiler team enables that, but this is possible for the headers that are static (i.e., won't change based on request):

@attribute [Header("some header", "some value")]

egil, 1 month ago

@patriksvensson @brtkdotse @khalidabuhakmeh ill add header control through attributes to my todo list. It's a good idea.

egil, 28 days ago

@khalidabuhakmeh aaand that's a wrap. Did call you out a bunch of times (in a good way I hope) and quoted you quite a bit. Thanks for the input.

egil, 28 days ago

@khalidabuhakmeh so when I say call out, I just mean I referenced you a bunch, not in a disagreeing way 😊

egil, 28 days ago

@khalidabuhakmeh here is a pretty concise example of template fragments, routing, callbacks, setting response headers: https://github.com/egil/Htmxor/blob/main/samples/MinimalHtmxorApp/Components/Pages/Counter.razor

egil, 28 days ago

@khalidabuhakmeh agreed. Good point. Still learning, but did figure out that trick with blazing pizza and the orders and configure logic.