4D Data Explorer in Action
Even though the 4D Data Explorer is still in Preview version (there are certainly more features to come in the next versions), we thought we’d show you the product in action and let you discover its capabilities.
This is a web browser interface usable by the administrator as well as the developer, remotely (in a secure way with an HTTPS connection) or locally on the same machine as your opened database.
Need to check your data during development? Need to find data that could cause bugs? The Data Explorer, with its powerful query engine and intuitive web interface, is made for you!
Let’s watch the video:
Deprecated and Removed 4D features: Why and How?
For over 36 years, our main goal has been to enhance our product while ensuring the compatibility of your 4D applications. This, of course, brings change, and change can be frustrating. With this in mind, we always aim to minimize the impact on your businesses with timely announcements, and most importantly, an improved alternative to the deprecated or removed functionality to ensure a smooth transition.
3 Reasons Why We Release Early and Often
Recently we’ve been answering questions on the 4D forum about commands and functionalities that felt incomplete or were missing, such as the Mail feature.
In this blog post, we’ll go through the 4D strategy behind the decision to release versions that are not fully developed, which is summarized in the “release early, release often” paradigm.
The story behind 4D’s new Markdown-based documentation site
by Arnaud Schmitt, Head of Technical Documentation at 4D SAS
As many of you know, doc.4d.com has long been managed using an in-house 4D application. However, 4D’s documentation is currently in transition to a new architecture: a Markdown-based documentation site.
This was the topic a few weeks ago during a 4D Method meetup, where I shared our experience about creating and maintaining the new documentation site. You may find this information useful when you are browsing the 4D documentation site, or if you need to create your own documentation.