WebForms Core, or WFC, is a new technology based on the Commander-Executor concept, developed by Elanat.
WebForms Core Organizations in GitHub WebForms Core is a DSL for defining commands for creating, modifying, and controlling the DOM and the execution flow of the user interface, running alongside a client-side Runtime.
This DSL enables declarative and Model-driven abstractions, allowing data flow, UI generation and modification, user interactions, and operation ordering to be defined without directly implementing DOM-related logic on the client side.
The Runtime then interprets and executes these commands and applies the requested changes to the user interface.
WebForms Core is not designed only for forms and CRUD operations.
It can even be extended to the creation of an interactive browser game.
Version 2.1 introduces high-level declarative capabilities.
This version provides a higher abstraction over the WFC core, combining the advantages of declarative development through advanced methods and mechanisms with imperative development.
WebForms Core 2.1 supports JavaScript ES2020 and modern browsers based on common web standards from 2020–2021 and later versions.
The previous version (2) supported ES2022, and in this version we committed to supporting some older browsers as well.
Therefore, this version is fully compatible with up-to-date browsers on Windows 7 and mobile devices released from 2015 onward, including Android 6.0 (with the latest Chrome version available for it, Chrome 106 in 2022) and iOS 15 (with Safari 15 in 2021).
Structure-centric UI Generation In WebForms Core, it is possible to go beyond the Component level and focus on automatically generating UI structures instead of manually constructing individual UI components.
In this approach, rather than defining every Input, Label, form, and table individually, the developer defines rules and data structures, and the system creates the UI based on them.
For example, a Model or database table structure can be used as the basis for automatically generating Add and Edit forms, input fields, and even data presentation structures.
The developer is therefore primarily specifying "what data exists and what structure should be generated", rather than "how every HTML element should be constructed." Compared with Blazor: Blazor primarily provides a Component-centric UI Model, while WebForms Core can provide, in addition to reusable Components and structures, a Structure-centric or Metadata-driven UI Generation Model.
Other systems can also build such generators, and this is not an exclusive technological advantage.
The important point is that the architecture and tools of WebForms Core are highly suitable for building systems that automatically generate DOM/UI structures.
Compared with React React is essentially a component and state-based UI library.
WebForms Core offers something different: a DSL + Runtime to define and implement UI flow, Data Flow, and Execution Flow.
Compatibility Between WebForms and WebFormsJS For example, WebFormsJS version 2.0.1 remains compatible with the WebForms class version 2.0 and 2.0.9.
Likewise, the WebForms class version 2.0.1 remains compatible with WebFormsJS version 2.0 and 2.0.9.
WFC is a continuously evolving technology, and using the latest versions of the technology is recommended.
WebForms Core 2.1 Version 2.1 is another major update, just like the previous two versions.
We spent more than three months writing tests for compatibility between the WebForms classes and the WebFormsJS library.
At Elanat, WFC 2.1 achieved a more than 99% quality assurance rate for WFC 2.1.
This percentage represents the success rate of our tests: we continued testing until we could no longer find problems.
The WebForms class is currently very stable.
If a problem is reported in WebFormsJS in the coming days, we will fix it immediately and release version 2.1.1 and later.
These patch versions remain fully compatible with the WebForms class version 2.1.