Product

Ease your developer’s life with list boxes

Automatically translated from English
Our main objective is to make developers’ lives easier, day after day, and list boxes are one 4D’s most used and powerful form objects that serve this purpose. We all know that list boxes trigger many events, that’s why in 4D v18 R2 we’ve enhanced the Form event command to return even more information when list box events are triggered.
 
Want to let go of your old tricky code for guessing which row, column, or header you clicked or put your mouse on? Let us show you a smoother and smarter way to do it!
Product

Take control of your work area

Automatically translated from English

Want to adapt your application’s interface to your end user’s system preferences? Want to make sure your application’s interface isn’t obscured by the macOS dock or menu, or by the Windows taskbar? In this blog post, we’ll show you how!

News

4D v18 R2 Beta starts today

Automatically translated from English

We’re pleased to announce the launch of beta testing for 4D v18 R2! So what new features does this R-release have to offer?

 

  • As part of the ongoing development for project databases, the Form Editor‘s UX has been greatly enhanced to instantly let you know if views are used. Plus, many additional actions have been added to simplify form design.
  • You asked for a way to prevent an application’s interface from being obscured by the macOS dock/menu or the Windows taskbar, and 4D delivers! Now, you have control of your work area.
  • For the first part of feature to receive emails, a new command and several methods are at your disposal to locally download emails and remove them from your email server. 
  • 4D Write Pro? Managing formulas inside your documents and the ability to delete pictures in a snap are the order of the day. 
  • What about your 4D View Pro documents? There’s now a whole set of commands to help you… from adding and removing rows and columns, to defining their size, visibility, and header labels.
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: