With 4D 21 R3, building modern user interfaces becomes even easier. The Object Library has been enhanced to align with today’s UI standards, including both Fluent UI and Liquid Glass design systems.
As a result, you get ready-to-use widgets that are visually consistent across platforms and optimized to speed up development.
A modernized Object Library
Concretely, the objects provided in the standard object library, as well as those from the 4D Widgets component, have been updated to match these modern design systems.
Fluent UI look

Liquid Glass look

But this evolution goes beyond a simple visual update. The code behind these objects has also been modernized to take advantage of current 4D development best practices.
As a result, when you use the Object Library in your forms, you automatically benefit from:
- a visual integration consistent with Fluent UI or Liquid Glass,
- ready-to-use objects to build modern interfaces,
- cleaner, more readable, and more maintainable code.
Note: Fluent UI rendering requires enabling Use Fluent UI on Windows in Settings. If you try these widgets without changing this setting, the UI will appear in Classic Windows look.
A smooth transition
If you are already using these components, the transition is seamless. The visual rendering of your widgets is automatically updated, with no additional effort required.
The object methods associated with the widgets are not modified. However, if you drag a widget from the Object Library again, its object method will be recreated using the updated version.
Conclusion
This update makes it easier to build modern interfaces while continuing to rely on well-known, reusable components from the 4D ecosystem.
With preformatted and customizable widgets, you can accelerate form development while ensuring a consistent and professional user interface, without starting from scratch. These widgets simplify development and automatically adapt to your platform and theme, whether light or dark.
This evolution combines visual modernity, productivity gains, and technical continuity.
Comments are not currently available for this post.