On Mac, application signature has become a standard, and since Big Sur, you can’t even run unsigned applications. In the past, we published a workaround to build client-server applications running on a Windows server and accepting connections from Mac clients. With the release of 4D v19, we have updated the application building in 4D to handle this case. Here is how you can build a single platform or a cross-platform application in v19.
As app users, we don’t pay much attention to the sophisticated authentication technologies that secure our applications. But they are essential to help prevent malicious people from usurping our identity. That’s why the authentication process that is included in 4D for iOS is so important to us. But many 4D for iOS users have been asking for more, and specifically, for new modern ways to login.
The new SignInWithQRCode login form template lets users log into their apps by scanning QRCode, and grants access directly to already authenticated users.
In continuous integration systems, every time code is submitted, or on an hourly basis, a compilation of the source code is automatically launched. This approach allows you to check merges on the code management server.
Starting from 4D v19, a new command allows you to launch code compilation, so you can set up this type of system.
We recently reviewed the formats of our logs to increase their readability and their compliance with automated analysis. We made these improvements in response to real-life situations we experienced, directly addressing issues that were hindering our ability to use 4D logs. In this blog post, we’ll explain in detail what changes we made so you can adjust your log analyzing tools accordingly.
As you may have noticed some time ago, 4D offers you a simple way to encrypt your data. Now, 4D also allows you to use the same algorithm as the one used for data encryption, but this time for your own needs. So now you can encrypt and decrypt any information you want, be it a single field in a table or external files.
Cookies’ abilities have grown and evolved over the years, but they have left some legacy issues. To handle this, browsers (including Safari, Chrome, Firefox, and Edge) are changing their behavior regarding the SameSite and Secure attributes for a secure-by-default model for cookies.
To prevent your web session cookie from circulating on the web pointlessly or being misunderstood by browsers because of a default value applied, you should ask if it is:
- a third-party cookie: associated with a domain name different from that of the page where the cookie is encountered. A third-party cookie is placed by a page object (e.g. an ad) originating from a domain other than the one hosting the page
- a first-party cookie: associated with the domain of the page
Depending on your use case, you should choose the appropriate value for the SameSite attribute of your web session cookie.
To reinforce security, the Secure attribute must be set for the web session cookie when the connection is secured (HTTPS) to indicate to the browser that the cookie can be sent safely.
Keep reading to learn how 4D has your back to improve privacy and security across the web.
For many years now, 4D Write Pro has made it possible to create simple or complex documents, either via programming using templates or by simply creating new documents from scratch. Starting with 4D v19, both developers and end users will be happy to use the new find (and replace) capabilities of 4D Write Pro. Using not just the interface… but also the code!
Let’s delve into the details!
The code editor’s feature set grows with every release, and 4Dv19 is no exception.
Every developer has their own special – and sometimes peculiar – taste when it comes to their code editor (font, font size, color of the elements, etc.). What looks great and boosts productivity for one developer can be an obstacle for another. That’s why 4D v19 introduces theme management.
If “creating my own theme” is on your bucket list, now is the right time to check it off! 4D v19 comes with basic themes that you can enrich and adapt to your own taste.
To build your application, you use the BUILD APPLICATION command with a set of XML keys that allow you to configure the built application. For most of you, this option is enough for application building. However, we want to make sure we meet your specific needs too, so we’ll simplify the BUILD APPLICATION command by splitting it. This will allow for more flexibility while creating applications.
A couple of months ago, we were happy to announce the ability to export 4D Write Pro documents to Microsoft Word.docx format. Now we’re thrilled to announce that the reverse operation is also possible!
Starting with 4D v19, you can import .docx documents into 4D Write Pro. Let’s have a closer look.
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