Author: Caroline Briaud

Caroline Briaud
• 4D Product Team Leader •Caroline joined 4D SAS in July, 2013 as an Engineering Manager responsible for new features definition. Caroline helped the Engineering team to put in place the R-release concept, with the new development process definition and its application within 4D’s engineering teams.Caroline is now leading the 4D Product team, mainly made up of Product Owners which are representing the customers within Engineering.Caroline started her career as a software developer in the mobile phone industry. She specialized in program management with an American company in an international context spread across US, India and China.
Product blank

Boost your performance with the new cache manager

The 4D v16 version has definitely been designed for better performance and scalability. In addition to major features like preemptive multi-threading, 4D v16 64-bit is embedding a brand new cache manager for a optimized handling of objects in cache memory avoiding any fragmentation issues.

The new cache manager improves the usage of very large cache for modern computers (with 64 or even 128 GB of Cache) allowing to take advantage of low RAM prices to have even large databases fully in memory. It also improves the situation of small cache size with very large data files, by decreasing the amount of unloading memory with increased support of priorities for data objects to be hold or released from cache.

Product 4D Write Pro

View properties in 4D Write Pro

From 4D v16, you can define at design phase the way a 4D Write Pro document will be displayed in a 4D Write Pro area. Without writing a single line of code, you can define several view attributes such as the resolution, zoom, page view mode. Advanced properties are also available to define whether you want to show 4D expressions or values for instance. Again no code to write, just a checkbox and it’s done.

Product 4D Write Pro

Protection of 4D Write Pro dynamic expression evaluation

With 4D v16, 4D Write Pro is now providing a higher level of protection regarding the evaluation of 4D expressions in documents.
Developers can now fully rely on 4D for checking the evaluation of these expressions. By doing so, end-user machines and databases will be automatically protected from any possible side effects.

A valid 4D expression can be a field, a variable, a 4D command, a statement returning a value, a project method, and so on.

Starting with 4D v16, “unsafe” 4D expressions will no longer be evaluated and an error will be displayed instead.

News 4D Windows 64-bit: Altura free

Altura-free version of 4D Windows 64-bit is on the way

On the way to provide Windows 64-bit version of the 4D product line we reached a major milestone, an Altura-free version. Altura is a library to emulate MacOS functionality on Windows, which was used to help plug-in developers to provide their products on Windows.

Although internally 4D for the most part did not use Altura any longer for a while, it was still deeply integrated to provide the functionality for 3rd party plug-ins.

Product blank

Headers and footers in 4D Write Pro

4D Write Pro is moving forward with 4D v16!

You can now insert headers and footers in your 4D Write Pro documents but also retrieve any existing headers and footers when opening an existing .4w7 document from the 4D Write plugin.

You can define document sections and add headers or footers for all or independently per section. You can have different headers/footers for the right and left page, or for the first page of the section. Of course, headers and footers can be styled as the rest of the document (font, color, margin, padding, borders…) and can contain images as well.

Product blank

Go further with Object fields

Object fields introduced with v15 allows unstructured data bases, similar to schemaless database (NoSQL). 4D v16 goes a big step further. Get a dynamic structure for unstructured data… Confused?

Imagine you use an object field to allow your customers to store custom data, where they can create their own fields. This works well and is one of the most interesting reasons for using an object field. The problem is, how to allow your customer to query this unstructured data? You don’t know which ‘fields’ they used, you cannot build a query editor on top or offer a drop down with used values.