Hi @developpeur-pro,

Thanks, yeah, definitely plan to get to v1. Currently on vacation with the family and have had a few crazy months at work, so ran out of steam.

One of the things I need to finish v1 is a good idea of what works and what does not. The current release contains a bunch of experiments and feedback on which work and which does not is very much needed.

If you are at a stage where you are considering using this in a course you may have a good idea of what to keep and tweak and what to throw out. If you can share that, it would be very helpful.

Hi Egil,

Thank you for your answer. I'm very happy to know that the project is continuing, and I hope you have a great vacation!
I'm still learning HTMX and Htmxor myself. So I only used them in a fairly basic way. That's why it's hard for me to say what works and what doesn't, because I don't know enough about htmx yet.

For now, here is the first feedback that I can give from my implementation of htmxor in an app that I made. Just to provide context, it is an online training monitoring app, with progressive unlocking of chapters and lessons. The main page is made up of the following elements:
A side panel displays the training plan (dynamically constructed in a recursive manner), but only the unlocked lessons are clickable.
Clicking on an item in the plan displays the corresponding lesson in the central part of the page.
At the end of the lesson there is also a "Continue" button, which allows you to move on to the next lesson if certain conditions are met.

I use htmx queries with parameters to navigate between lessons already viewed without changing the state of the plan.
The "Continue" button also triggers an htmx request.

This all works well. The difficulty was above all to define a correct division of components and routes (ordinary or htmx). Htmx and htmxor open up many possibilities, but it is not always easy to find the best approach to answer a problem.

However, I was unable to launch a JavaScript script after executing an htmx request, using the syntax hx-on:htmx:after-request="alert('Made a request!')". JavaScript code does not execute...
On the other hand, running scripts with the hx-on:click="..." syntax works fine.

Outside of this app, I spent a lot of time trying to understand the code for the "HtmxorExamples\Components\Pages\Examples\UpdatingOtherContent\OutOfBandResponses.razor" example.
By running it in debug mode, I finally noticed that the page was completely reloaded each time a contact was added, which removes all the interest of the "Out of band response" technique. I think it would therefore be better to delete this example, which is misleading.

So much for this first rather summary return. I will try to give you more feedback as I experiment. I will also try to contribute to the documentation, which seems to me an essential element to facilitate the learning and dissemination of these innovative technologies.

Thank you again for your work, and I hope that htmxor will have the success it deserves :-)

Cyril