Multiple 4D data sources, interested?

We’ve got an exciting new feature to announce in 4D v18 and the title may have already given you a hint!

This feature opens new possibilities for client/server work. Rather than being limited to the current database and requiring a permanent network connection, an application in 4D v18 can get data from another, remote 4D database that’s exposed on a 4D server!

A lot of options become available thanks to this feature. For example, you could organize your applications to work offline and only synchronize local data when remote data is reachable. Or you could consider publishing your data on multiple servers and switching from one to the other as necessary. Another option could be splitting your data model across different databases (e.g. local data, international data). What about having your data distributed in different places yet still accessible through a single 4D client code (project methods and form objects)? All of these scenarios are now possible and this blog post tells you how!


Headless 4D applications

As a 4D developer, you may have already encountered a need to develop applications without a graphical user interface (GUI), otherwise known as a headless applications. Previously in 4D, this wasn’t entirely possible to do ….  until 4D v18! In this blog post, we’ll go through some of the newly available capabilities so you can make your applications “headless”!

Why create headless applications? There are several use cases such as simulating Windows behavior on macOS, or having the Windows service behavior without using the service manager, and so on. But above all, it opens new opportunities such as developing bots with 4D.


Project databases: More than a collaboration solution

Dreaming of a way of to work collaboratively? A way to work wherever you are in the world, with team members in different locations, and no one has to question where to find the latest version of a file or project? A different way to test new features and roll them back if they don’t work out, while being able to choose a restore point from which you want to roll back instead of running a full file backup. Your dreams are becoming a reality, these scenarios are now possible thanks to 4D v18 and project databases!


How to notarize your merged 4D application

With Catalina (macOS 10.15), it’s highly recommended that you notarize applications distributed over a public network. A significant number of developers transfer their applications using a connected storage device or via file sharing, notarization isn’t required in these cases where the user already trusts the developer. The purpose of notarization is to assure users that the application isn’t malicious and is only required for applications downloaded from a website.

If you use our built-in signature feature when building your applications with 4D v18, your application is ready to be notarized. This process is conducted outside of 4D. It involves adding an electronic signature to your application and submitting your signed application to an automated inspection service. Here’s everything you need to know:


Get your macOS applications ready for notarization with 4D

Catalina (macOS 10.15) is now available and Apple has announced that the notarization of software distributed outside of the App Store has become a requirement. This may raise a few questions: what if my 4D application isn’t notarized? Will I be able to notarize it? How? Don’t panic! We’ve got you covered and this blog post provides the answers.


4D for iOS: What you need to know about iOS 13

iOS 13, first launched at the Apple’s annual Worldwide Developers Conference (WWDC 2019), to be released today, September 19. And we couldn’t be more thrilled to announce that some of the features Apple has unveiled for their latest iOS, will be available in 4D for iOS with the release of the v18! Here’s everything you need to know about the advances we have in store for you:


Convert an existing database into a Project

As of 4D v17 R5, you can create a database project. One of the greatest benefits of projects is how easy it makes collaborative work for distributed teams … by storing the source in a source control system in plain text files. Whether you’re a single developer or part of a team, this opens a new world of possibilities

But what about existing databases? Can they be converted to projects? Yes! This blog post is all about showing you how to do this and making you aware of a few things to know before proceeding.


4D Project: Embrace a new era of collaboration

4D has been a longtime supporter of team development, ever since 4D Server 1.0. The greatest benefit of working together on the same source code, is allowing both team development and team testing. However this can create some disadvantages for distributed teams since they may not be able to work on the same source.

Following a complete rewrite, 4D now supports two ways to work with sources: binary and project. Binary is the 4D we all know and love, with the source in a binary file to allow team development with 4D Server. Project makes it easier for distributed teams to work collaboratively by storing the source in a source control system in plain text files.