Using 4D libraries within project databases
4D provides libraries to help you develop applications. One of these libraries is standard and contains preconfigured form objects and widgets, while other libraries are custom. The standard library is “read-only” and its behavior doesn’t change when developing project databases (with the exception of minor, cosmetic interface differences). You also have the ability to create your own custom libraries to save your own form objects or group of objects. In this case, a few changes have been made to make them even more powerful. The following is everything you need to know about these changes:
A new tool: JSON Validator
4D v16 R4 introduces a new command: JSON Validate. This command allows you to verify that a JSON document is “valid” according to your JSON schema. This is really useful for exchanging information between servers or between a server and its client. Thanks to JSON schema standards, you can define a “protocol” for communication with your server or an external server. More details can be found in this blog post.
Source code sharing of internal 4D components with 4D Partners
4D has initiated a new program to share the source code of internal 4D key components such as the 64-bit Quick Report, the date/time pickers, or even the 4D Write Pro user interface.
Sounds already interesting, but what exactly does it concretely mean for you? You always wanted to use the Time picker widget, but with a different look and feel. The 4D Write Pro user interface is great, but can’t fit exactly in your application, that is requiring a more ‘Microsoft Office like’ ribbon bar approach.