Product Road to IPv6

Enhance IPv6-related user interface

Besides the fact that it has a larger address space, IPv6 also has many other advantages over IPv4: built-in features like support of multicast transmission, increased security with IPSec (providing confidentiality, authentication and data integrity) and the ability to display, in the 4D client connection dialog box, all the 4D Server available even if they are published on a non standard port (different than 19813).

4D introduced IPv6 support with 4D v14, however some dialogs were not perfectly arranged for the IPv6 use cases. 4D v16 R4 provides some UI improvements for a better user experience for people using IPv6 network configurations.

Product blank

4D initiates a new variable type: Collection

4D v16 R4 introduces a new type of variable called Collection. What are these variables intended for? Like Objects or BLOBs, collections can be used to hold almost any kind of variable types like texts, numerics, booleans, objects and even other collections. The good thing is that, all these variables types previously mentioned can be mixed inside the same collection, where arrays must always contain the same type of elements!

Product blank

Easily design your own 4D Write Pro toolbar with standard actions

You need a custom 4D Write Pro toolbar for your application but you’re concerned it might take too much time to implement it? Good news, with 4D v16 R4 standard actions can now be assigned to checkboxes and pop-up menus. Save time with this ready-to-use feature and easily create a user-friendly interface perfectly matching your needs!

You can now create a pop-up menu to control the font size or the border style for your 4D Write Pro area just in one click, no code needed! Just assign the action using the property list and it’s done. And the object status and value will be automatically updated by 4D depending on the context and text selection! Simple and powerful…

Product blank

Validate your JSON object

We use more and more the JSON format. For example, to save settings in a file, to store software configuration, or to exchange client-data on the web with other servers.

How can you validate that the received data is in the expected format? How can you validate that all the necessary information is actually present? How can you do this validation without writing a tiresome method for each type of JSON format?

Simply by writing a JSON schema and use the JSON Validate new command!