Hc 9890fe7

Quick start

If you really do not want to write a single line of front-end code, include the page $(opam var share)/hc/hc-page.js in your page. Now the following:

<script type="text/javascript" defer src="hc-page.js"></script>
<button data-request="POST /clicked"
        data-effect="element">Replace me</button>

instructs a click on the button to perform a POST request to /clicked and replace the button with the HTML response. That's it.

If you installed hc with tests (opam install -t hc). The hc-examples binary serves a few interaction examples.

Manuals

• The manual explains it all.

API

• Hc Hc HTML generation and HTTP headers for Webs.
• Hc_page Hc web page driver.

TODO

• Review animation interaction for hc-in, it's not so good to have transition on bare elements which are triggered according to .hc-in -> bare
• Provide and trigger events for Hc behaviour itself, this allows to chain Hc connections in interesting ways and helps coordinating with other front end code. Update. Something was hastily added in Hc.Ev. needs proper design and documentation.
• Because of resource costs we likely want something like multi-target response updates for SSE and websockets. Also useful for deletion examples (or should we enrich effect ?)
• Provide support for full page target. Support a data-preserve attribute which patches by id in the replacement
• Provide support history via data-push-history, pushes the request url, snapshots body element for state restoration.
• Provide support for load and revealed events.
• The event source mecanism remains expressively limited e.g. for click event from that element, key from that other one, but maybe we don't care. It's possible to work around. Parsewise it's difficult to have a <sel> argument in an attribute beyond itself (e.g. from:<sel>).
• Define the semantics in case of HTTP errors
• Maybe for keep event simple, only trigger on request element but devise a separate DSL to declare custom events and fan-in from other events. Or even, let that to separate JavaScript fiddling.
• Consider data-response-sel to apply on the response.
• Provide request counters and discard if older reponse or not latest.
• Provide default filters that easily
• Provide focus and scroll position management.
• Sometimes it feels a bit stupid to have a trip to the server. Provide local substitution.
• We likely want to expose the dom effecting stuff (for now exposed hastily for hyperbib and undocumented), make a nice api and let hc use it.
• Allow to tweak the Referrer-Policy for requests. For now we use same-origin. Possibly allow to set referer.
• Support for header specification ?