News

4D v18 is here

Automatically translated from English

Our most spectacular major release yet is now available! 4D v18 is bursting with advanced functionalities, upgrades, and enhancements.

This cutting-edge release opens a lot of possibilities for your 4D-based applications. Though by no means exhaustive, here’s a list of features we’ve got in store for you:

  • Project database for version control: A solution for collaborative programming, enabling you to store your code in plain text files within a source control system (e.g., Github, Perforce, etc.).
  • Encryption: Built-in data encryption tools on a per-table basis. Whether via the UI or programming, your application’s protection is at its finest.
  • 4D for iOS: A product fully integrated into 4D to easily extend your business applications to mobile.
  • ORDA: Optimized performance, extra commands, and remote datastore.
  • The 4D language: Staying compatible with the classic language, the 4D language is making great strides towards becoming object-oriented with member methods to access files (or folders, zip archives, or emails), the ability to build your own member functions and use the new formula object, enhanced debugging features, etc.
  • 4D Write Pro: Style sheets, a feature-rich toolbar, more table-related features, and the list goes on.
  • 4D View Pro: A powerful ribbon toolbar, .xlsx import/export, more commands to handle your documents by programming, and much more.

This list is far from exhaustive, see all the blog posts for 4D v18!

Tips

Binary database vs. Project database

Automatically translated from English

As you know, 4D now supports two ways to work with sources: binary and project databases. Binary databases are the 4D we all know and love, with source code in a binary file to allow team development with 4D Server, and all of the design elements (methods, forms, structure, etc.) gathered in a single, compact binary file, the “.4db” file. Project databases make it easier for distributed teams to work collaboratively by storing the source code in a source control system in separate, plain text files. Projects will not replace the 4DB, we have no plans to make the 4DB disappear. It’s about two different ways of working and developing. It’s up to you to choose what best suits your needs. Here’s a blog post to help you decide:

Product

SVG “non-scaling-stroke” attribute support

Automatically translated from English

Sometimes it’s preferable to have the lines of an object keep their original width, regardless of the applied transformation. For example, you draw a line on a map showing a user’s position and a destination. When the user zooms in on the map, you want to enlarge the map but have the line maintain its width.