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:
2019 has been a successful year for us here at 4D and it’s all thanks to our partners, customers, and community! Last year we made a Happy New Year video, this year we’re keeping it simple … all of us at 4D wish all of you a very Happy New Year! We’re looking forward to another great year in 2020!
As another year and another decade come to an end, it’s time to take a look back with 10 of our most-read posts. From project databases to encryption, to performance optimization, to advanced ORDA and programming capabilities … 2019 had it all! Here are the topics that grabbed your attention in 2019.
A very detailed blog post has been published on Users and Groups in project databases. In this post, we’re providing a video about the key points to remember.
So you’ve been testing out project databases … maybe you’ve created one or perhaps you’ve converted an existing binary application. Now, it’s time for us to show you how to use Git (the revision control system) with Github as the hosting service for your 4D application.
Blog post by guest author Joel Levy, a 4D developer at Sweetwater:
4D is the heartbeat of Sweetwater Sound. Our application harmoniously interconnects the diverse needs of over 700 concurrent users. We’re always seeking out more developers to fulfill the needs of a constantly growing company. Here’s a look into the strategies that Sweetwater uses to onboard developers new to the 4D platform.
Since the delivery of 4D v18, a series of blog posts on how to convert and develop with project databases have been published. What about components? This blog post answers that question.
PROCESS 4D TAGS has been enhanced with each 4D version and the latest additions as 4DCODE have drastically increased the use cases. What was previously a single line of code, is now often many lines, even pages, of 4D code.
In 4D v18, we shipped a cool feature allowing you to easily manipulate tables with new commands and standard actions. We’ve got even more good news (especially for those who prefer UI over coding): we’ve extended these new capabilities to the 4D Write Pro widget interface. Now, a new tab lets you manipulate tables directly from the widget!
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.
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