OK, maybe in the newyear

We do have several places for discussions already -- Github, Discord, Stack Overflow, Reddit. I'm all for having the best tools for the job (and Discord is NOT great for many uses) but adding yet another channel should be done carefully.

I think the biggest issue right now is that questions and issues don't immediately go to Github or Stack Overflow.

Having multiple channels is indeed a chore, but can work out fine, as long as there is clear directions on why - that is, what each channel should be used for. In the case of Kirby, they provide support and info in several ways, but it’s quite clear when to use each channel: - general socialising and asking quick questions: Discord - asking support questions and requesting complex guidance: Discourse - reporting issues and bugs: Github - requesting and voting for new features: Nolt - personal, private support - eg., license issues: email There was some discussion in the Kirby team about moving the forum to GitHub Discussions, precisely because of that - i.e., easier, more centralised issues, less channels to manage. Several points were raised, which have made the team reluctant to make the move - such as the fact that if you have several repositories, you end up with a separate forum (discussion) in each repo, rather than a ‘central forum’. Kirby might still decide to move over to Github Discussions, but for the time being they’re sticking to Discourse. Ultimately, each platform has features that are compelling, and that have made it difficult for the Kirby team to move away.

Yes. All good points. I think 2/3 of the issue is just being clear about what kinds of messages go where (and enforcing it). I hope my last message didn't come off as anti-forum 🙂

If we're able to establish clear roles for all of the places, nearly anything will work better than Discord 😛

It’s also easier if you have help… 😉

So I've done some work to get hx-trigger="restored" working for back button presses. There's still some tidying up and I'll have to write tests but would the best way to get this looked at be to create an issue and then link a pr to that?

Yes. PRs are gold. Plan to write tests and documentation too, but I usually get away with doing that after I’ve gotten an okay on the basic concept.

And, there’s a big effort to keep the file size down right now, so bonus points if it doesn’t add a lot of code or if it can be written as an extension.

Hi, i want to pass the value from select menu when it changes to an attribute of a DIV:

<select name='account'>
         {% for account in accounts %}
           <option id="{{ account.id }} value="{{ balance }}">{{ account.name }} | ${{ account.balance}}</option>
         {% endfor %}
</select>

And the target DIV its like this:

<div data-kt-dialer-max="***SELECTED OPTION VALUE HERE*****">

This doesn’t have any htmx in it. Are you looking for a way to do this via hyperscript?

I want to know if its possible to achive my objective using htmx, and if it is, how

Im currently using django, its working great with ajax requests

I was reading this example: https://htmx.org/examples/value-select/ But it uses hx-get and i dont need to make a request because i already have the values loaded in the dom

thanks! let me know if you have any other tips or suggestions for contributing

You would probably use hyperscript for that. As an example, let's say you have the folllowing HTML structure:

<label>Choose an ice cream flavor:
  <select class="ice-cream" name="ice-cream">
    <option value="">Select One …</option>
    <option value="chocolate">Chocolate</option>
    <option value="sardine">Sardine</option>
    <option value="vanilla">Vanilla</option>
  </select>
</label>

<div id="output" data-my-attribute=""></div>

We want the value of

data-my-attribute

inside our

#output

div to reflect whatever is selected inside our

ice-cream

select field. We can do that with one line of hyperscript - here is how our

<select>

tag would look, with the hyperscript:

<select class="ice-cream" name="ice-cream"
  _="on change set #output's @data-my-attribute to my value">

In case somebody is interested: I will give a presentation about Java/Thymeleaf and htmx tomorrow for W-JAX Hybrid

Hey @User look at this PR for Craft CMS carefully 🙂 https://github.com/craftcms/cms/pull/10075

Adds a condition builder framework (powered by Htmx)

🤯

Thanks for your response! But im not sure why its not working, i have set the id on the target div and i added the hyperscript line in the select tag

first things first: did you include hyperscript off a CDN? (it's not part of htmx)

next, try adding a

log me

in the change handler and see if it is being logged when you change

Yes i have imported hyperscript

_="on change log me" when the selection changes, theres no output in console

🤔

I removed an extra class that was using js and its now receiving the event

😑

Hmmm but it is still not changing my targets class value