WebExpress

When processes in WebExpress should not only be represented technically but also experienced visually, a dedicated editor becomes essential. Status values such as new, planning, in progress and completed form the foundation of many workflows. Only the ability to arrange these statuses freely and make their transitions visible creates a tool that makes processes intuitively understandable. This is where the idea of an SVG‑based editor comes into play, presenting status nodes and their connections interactively. The editor displays each status as a movable node on an open workspace. Users can arrange these nodes freely to structure their own workflows. The transitions between statuses are shown as lines that define the possible change from one state to another. Instead of drawing these connections automatically and rigidly, the editor allows manual routing. Each transition consists not only of a start and end point but also of a series of waypoints that define the path of the line. Thes...

Although WebExpress itself has existed for much longer, the blog celebrates its first anniversary today. Its reach may still be zero, yet this does not diminish its value in the slightest. The blog fulfills an essential purpose. It helps to understand WebExpress more deeply from a developer’s perspective by capturing thoughts, decisions and technical considerations in written form. This act of thinking through writing makes architectural choices more comprehensible, reveals development steps with greater clarity and creates a kind of technical journal that will prove immensely valuable over time. It would, of course, be desirable for an active community to form around WebExpress . A framework does not thrive on code alone, but on exchange, feedback, discussion and people who contribute their own ideas. This is an area that will require more focused attention in the future. Only through feedback can a living ecosystem emerge, and only through diverse perspectives can WebExpress truly...

The development of our new WQL prompt control began with the ambition to make the input of complex filter expressions as direct and efficient as working in a terminal. The goal was to create an input environment that feels familiar, responds quickly, and at the same time respects the specifics of WQL syntax. This includes a suggestion system that offers matching attributes, operators, and values while typing, displaying them clearly in the hint area below the input field. The most likely continuation appears as plain text, complemented by a list of alternative values, limited to a maximum entries for clarity. Suggestions can be navigated using the arrow keys, while the Tab key can be used to accept a selected completion. To ensure that suggestions remain up to date and performant, they are provided through a REST interface that adheres to the defined WQL syntax. To avoid unnecessary network load, requests are triggered only after a short input delay. This debouncing prevents a request ...