6 posts tagged with "Feature"

This release addresses two major issues in the underlying infrastructure of HtmlFlow:

1. Unified API Generators: Combines two previously separate API generators—one for Java and another for idiomatic Kotlin builders using function literals with receivers—into a single unified infrastructure.

2. Simplified Manual Integration: Streamlines the process of merging manually written builders (e.g., of(), dynamic(), async(), suspending(), etc.) with automatically generated HTML builders.

All HTML builders are now available through Kotlin Extensions with function literals with receiver, enabling both nested method and method chaining idioms.

• Kotlin Extensions - new dyn { } lambda with parent Element as receiver to allow the use of implicit this.

This release introduces the following new features and fixes:

• Added Kotlin extensions, such as the .l property, which can be used to close tags in Kotlin instead of .__().

This release introduces the following changes when migrating from HtmlFlow 3.x to 4.x:

• DynamicHtml and StaticHtml are replaced by HtmlView and HtmlDoc, respectively. Both inherit from the new HtmlPage type.
• The factory methods DynamicHtml.view() and StaticHtml.view() have been moved to the HtmlFlow class, becoming HtmlFlow.view() and HtmlFlow.doc().

A new custom element feature allows defining HtmlFlow views, as shown in the listing at the end of this post. This feature applies to both static and dynamic views.

You can find this sample in the unit tests at htmlflow.test.views.HtmlCustomElements.

Invoking .custom("alert-info") returns an instance of the new CustomElement class, which inherits from the existing Div class. As a result, the returned instance has most HTML features available.