So your application has been developed and you’re ready for the next step. 4D lets you:
- generate a compiled database that no longer contains any interpreted code,
- generate a standalone application that can be double-clicked, (i.e., merged with 4D Volume Desktop, 4D’s database engine),
- generate client/server applications with automatic updates of client and server parts.
4D provides libraries to help you develop applications. One of these libraries is standard and contains preconfigured form objects and widgets, while other libraries are custom. The standard library is “read-only” and its behavior doesn’t change when developing project databases (with the exception of minor, cosmetic interface differences). You also have the ability to create your own custom libraries to save your own form objects or group of objects. In this case, a few changes have been made to make them even more powerful. The following is everything you need to know about these changes:
In this blog post, we showed you how to convert a binary database into a project database. Once everything is ready and the conversion has successfully completed, you can start working with your project database. However, some questions may arise: are all the files in the database useful? It’s obvious that the”.4DB” structure file is no longer needed. Can I delete other files?
Here’s everything you need to know after the conversion.
Classic 4D binary structures let you define style sheets to specify the font, font size, and text style to use in your forms for both the macOS and Windows platforms. Project databases let you go even further by letting you define the properties of a 4-state button or specify the color and border of all line objects or even set the header height of all of an application’s list boxes! Inspired by the grammar and syntax of CSS, 4D adapted it to meet the specific needs of the forms in 4D project databases. Thanks to style sheets, you can configure all of the properties to create truly visually appealing forms. This blog post shows you how!
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.
Project databases, the headliner of the 4D v18 release, allow distributed teams to work collaboratively by storing an application’s code in a source control system, in text files containing everything from the database structure to the user interface, including forms, menus, user settings, or any required resources. And since a project database is made of text-based files, you’ll have several folders and files, stored within a single parent database folder. In this blog post, we’ll go through the architecture of a project database to give you a better understanding of this new type of database.
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!
There have been requests to modify the 4D Server administration dialog, with some customers wanting to remove information and others wanting to add customized information. This AdminWindow component shows you how to do just that. You can use it “as is” or modify it to fit your needs.
As of 4D v17 R5, you can create a database project. One of the greatest benefits of projects is how easy it makes collaborative work for distributed teams … by storing the source in a source control system in plain text files. Whether you’re a single developer or part of a team, this opens a new world of possibilities.
But what about existing databases? Can they be converted to projects? Yes! This blog post is all about showing you how to do this and making you aware of a few things to know before proceeding.
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