Use htmx where useful

[bschmalhofer]

https://htmx.org/ might lead to more flexibility and less obtuse code. For new features and complete refactorings things look very simple. An example is provided in https://github.com/RotherOSS/otobo/tree/htmx_dancer2_showcase_rebased_ 1

Another example is peridoc reloading of a Dashboard component::

<div
  hx-trigger="every [% Data.RefreshMinutes | html %]m"
  hx-get="?Action=AgentDashboard;Subaction=Element;Name=[% Data.WidgetName | html %]"
>

The question whether htmx works together with the existing JavaScript is important. I see two clashes. htmx does something and previous fuctionality is lost. Or the existing JavaScript does something and htmx is perplexed. Both cases can be handled reasonably well. htmx supports callbacks, like `hx-on::after-settle, which can be used to replicate the current behavior.

<div
  hx-trigger="every [% Data.RefreshMinutes | html %]m"
  hx-get="?Action=AgentDashboard;Subaction=Element;Name=[% Data.WidgetName | html %]"
  hx-on::after-settle="Core.Agent.AppointmentParticipationWidget.AppointmentParticipationEvent( Core.Config.Get('AppointmentParticipation') );"
>

When Core methods reload content with hx tags then htmx.process(Swappedelem) must be called. See also the htmx_experiment in the non-public ticketicalintegration repository.

Cheap trick: $SwappedElem[0] turns a jquery element into a plain JavaScript element.

[richieri]

Not sure if you guys are already aware of it, but you can avoid conflicts in some parts of the application by using the hx-boost attribute.

For example, if you want htmx to be executed only on some parts of the page, you can add hx-boost="false" to the body element, and then add hx-boost="true" on DIVs, forms or any other elements that you want htmx to be looking at.

The opposite also might be valid: you can have hx-boost="true" at the body element, and disable it on some specific parts of the application with hx-boost="false"

https://htmx.org/attributes/hx-boost/

[bschmalhofer]

Hi @richieri ,

I wasn't aware of hx-boost specifically, thanks for the hint.

That htmx plays well with existing frameworks and applications is one of the reasons I like it. However, the strategic decision on whether to use htmx has not been made yet.

[svenoe]

Hey Ronaldo, nice to hear from you and thanks for the hint. :)
(I would also say the decision is more about the when or as part of which project. ;)