tectu / zim Goto Github PK

This is going to be a long-term effort: Introduce a widget system.

The idea behind the widget system is that components can be created programmatically (such as an HTML table, form, ...). A widget known how to render itself and might implement the necessary endpoints for user interactions.

As of today, zim::controller creates an internal instance of the underlying malloy server. However, there are scenarios where a user might want to re-use an existing malloy server.

A potential scenario involves having a "headless" web service built with only malloy and slapping a GUI (eg. HTML frontend) on top of it.

Provide a high-level interface (most likely in zim::controller) to set a favicon.

This function should accept a filesystem path to the corresponding favicon.ico file and automatically register the corresponding GET /favicon.ico endpoint.

Alternatively, a filesystem path could be provided to the controller configuration (zim::controller::configuration). Upon initialization of the controller (zim::controller::init()) the controller could check whether a valid filepath was provided and create the corresponding GET /favicon.ico endpoint as needed.

Provide a high-level form component implementation similar to the current pages.

In contrast to a page, a form should ideally also implement the necessary POST end-point and provide a user callback.