Using Classes Across Components
Component developers frequently require the utilization of a class from another existing component.
With 4D 20 R6, when a component has a declared namespace, its classes are now accessible to all components loaded in the host project via cs.namespace.
Force Login Becomes Default for all REST Auth
We recently provided a new way of controlling access to the REST API via the privileges and the ds.authentify function: Force Login. This feature offers much more than previously available authentication mechanisms and was clearly explained in this blog post.
With 4D 20 R6, Force Login has become the default mode for REST authentications. Curious about the reasons behind this change and how to manage the transition? Keep reading to find out more.
Enhanced Session Storage Access
You can store information in the storage of various session types, such as Client/Server, Web, or Mobile, allowing for easy reuse across different processes.
Now, in 4D 20 R6, you can access the storage of a specific session. This enhancement enables users to easily maintain the continuity and consistency of information across multiple sessions of the same user. Imagine being able to pull up the same customer record across different applications such as Client/Server or Web.
Managing HTTP Requests with HTTP Agents
In 4D 19 R6, we introduced HTTP classes to modernize syntax and enhance functionalities for our HTTP client commands. Building on this foundation, 4D 20 R6 brings a powerful new feature: HTTP agents. These agents empower developers to customize and optimize their connections to HTTP servers by managing connection persistence and reuse for HTTP requests.
Class property declarations and assignments on a single line
In 4D 20 R5, the streamlined property declaration now offers the convenience of initializing properties simultaneously with their declaration, akin to variable assignment.
This enhancement simplifies code readability and efficiency by allowing developers to declare and initialize properties in a single line. This facilitates smoother integration and reduces the need for separate initialization blocks. It optimizes development workflows and ensures code robustness across compilers and interpreters, promoting cleaner, more maintainable codebases.
Customize App Appearance with New Windows Types
With 4D 20 R5, unlocking new possibilities in application customization, two additional window types now offer flexible modal or non-modal windows without title bars. This means complete freedom to tailor your application’s appearance to your exact specifications. Imagine redesigning the title bar to match your desired aesthetics, integrating features like a customized search box or other elements seamlessly.
But that’s not all! We’ve also introduced several new commands designed to streamline your development process:
- Reduce a window in the title bar on Windows or the dock on macOS,
- Know if the window is reduced in the title bar on Windows or the dock on macOS,
- Know if the window if the window is maximized.
New 4D remote session object with Client/Server connection and Stored procedure
In 4D applications, four types of sessions exist 4D Remote session, Stored Procedure session, Mobile session, and Web session.
The Session command already returns Web or Mobile sessions. This gives you access to a wealth of information about the session and an object shared by all processes in the session.
In 4D 20 R5, the Session command has been extended to the Client/Server connection and stored procedure.
Try-Catch Code Blocks Unveiled!
After implementing the throw() command and introducing the Try(Expression) keyword, we are excited to unveil the next evolution in 4D’s error handling system: the introduction of Try-Catch code blocks!
Shared Classes
Do you want a simplified way to use shared objects, following the classic object syntax and automatically calling use/end use when needed?
Fasten your seatbelts; here come the shared classes!
Singletons in 4D
4D 20 R5 delivers a powerful feature for developers: Singletons!
The singleton design pattern creates a single instance of a class accessible throughout your application.
This pattern offers many benefits, including:
- host for interprocess values,
- utility classes,
- a base for the factory design pattern,
- and many more.
Keep reading for more information about this new concept!
Contact us
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!
* Your privacy is very important to us. Please click here to view our Policy