In a previous version of 4D for iOS, we introduced Many to One relations. 4D v18 completes the list of relations available in 4D for iOS by allowing you to easily build the most complete apps with the most engaging user experience you can get on a mobile phone!
Project databases, available in beta in the latest 4D v 17 R-Releases, are now available for production in 4D v18! Among the many changes in 4D v18 is the way user and groups are managed … it’s become much easier, especially deployment. This post will briefly highlight everything you need to know about these changes.
With the VP PRINT and VP EXPORT DOCUMENT commands, you can now print a document or create a PDF version of it. However, in order to create an appealing document for your customer, you not only need to print a document, but also add headers, footers, define the zoom, define the paper orientation, and so on. With 4D v18, it’s all possible thanks to the VP SET PRINT INFO command that allows you to define these attributes and more in your document!
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!
4D v18 introduces a new architecture for files and folders to keep your deployed macOS package and Windows application folders intact. In a nutshell, the logs folder and all user-based settings, including 4D backup settings, are now stored next to the data file. In fact, the settings exist twice; one next to the structure to use as default settings for new data files, and one beside the data file, storing user changes.
As a result, the folder containing the structure can be read-only, since nothing is modified inside (*). Deployment becomes easier because the structure folder can simply be replaced, nothing within it needs to be copied beforehand.
(*) only in project databases. In binary databases the user & password tables are stored in the structure, so the folder must not be read-only.
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.
4D v17 R5 marked the start of beta testing for a new type of 4D database: project databases. In 4D v18, we’re thrilled to announce that project databases are now in final release. It’s time to take advantage of the power of the 4D development platform combined with the versatility of a lightweight and distributed format!
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!
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.
A few weeks ago, we introduced action parameters so you could better interact with your 4D for iOS apps. They let you add, edit and delete records from your iOS device using edition forms. Well things are becoming even more interesting in 4D v17 R6, because now you can add pictures!
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