So by now, you know that projects come with a tremendous benefit: the ability to use Git (the revision control system) and GitHub (the hosting service) to get your 4D application up and running in a more productive development environment.
Newbie or full-fledged senior developer version control has been a staple in every work environment where multiple resources collaborate to participate in what could be called a software chain of production.
To help you get familiar with Git, we’ve made available many resources at your disposal. This blog post is a compilation of everything we’ve provided on this topic… so far. If you feel lost and don’t know where to start, keep reading; we’ve included:
- other blog posts,
- a detailed guide,
- a top-rated summit video,
- and even a training course.
Projects introduced the new directory.json file containing users, groups and permissions. It allows authentication, restrictions, permissions on several parts of the application, through settings or code. Let’s see the new improvements about this file usage in merged server projects.
Commands, constants, tables and fields are stored with their tokens in the project source code files (4dm files). This allows 4D to rename them automatically. But sometimes, you would like these source code files to be stored without tokens for a better readability with a version control system or an external code editor, or for better code sharing between projects. Let’s see how to make 4D store source code without these tokens.
Classes were introduced with 4D v18 R3. They allow you to organize your business logic and separate it from the UI part more quickly.
Classes are composed of several functions of varying lengths, so it’s not always easy to find the function you want to modify, or to move from one function to another. You can use the explorer, which displays classes and functions, but when you’re coding in the editor window, you don’t want to waste time changing windows.
With 4D v19 R4, the list of functions in your class is displayed in the code editor toolbar, allowing you to easily jump to a specific function.
For many years, 4D has allowed you to develop binary databases as part of a team with a 4D Server. This way of developing is straightforward, but many developers asked us to be more efficient on source code management to deliver better traceability. 4D has heard them and developed Project mode to fit this need. This mode opened a new era of collaboration thanks to version control systems!
by Mourad Aouinat, Software Engineer at 4D Morocco
In a previous blog post, we saw how easy setting up a REST API using 4D. In this blog post, we will leverage the powerful 4D REST API in combination with React to build a To-Do app that includes features to open todos, create new ones, modify existing ones, and features for bulk modification and bulk deletion.
Since 4D v19, you can start the compilation of a project with a simple command. You might be wondering what you can use this for!
Your team may consist of several developers, so why not automate the compilation at each code push on your source control server? It is always easier to identify an error when it is quickly detected.
Another case is when your project consists of several components. You can write a method that compiles, builds, and then copies the component to the host database.
This blog will discuss the different technical points that are very useful to create your own automation tools, along with an example application.
Project mode allows you to easily track changes with Git, the most popular version control system. But often, you don’t want to track all the files of your project in the Git repository. 4D now offers you the possibility to define what not to track in your new projects.
by guest author Michael Höhne, 4D developer (Munich, Germany)
There’s a feature in 4D v18 R5 that may have been overlooked, or at least hasn’t gotten much attention so far: Form macros. To be honest, I hadn’t spent much time on them either, until recently. In this blog post, I’ll show you a macro that saves a lot of time when applying naming conventions to list box columns, column headers, and footers. You can easily change it to fit your needs. A dedicated repo is also available on Github.
If you’re a fan of macros in the code editor, then 4D v18 R5 has some good news for you … because now macros are also available in the form editor!
Let me start by telling you how useful macros can be for you. Have you ever needed to use formatting or naming rules in your application, then apply them to each new form? Or maybe you’ve had to work on existing forms created by someone else, and always need to do the exact same checks and analyses before getting started. If you’ve ever encountered one of these scenarios, then 4D v18 R5 is for you because it gives you the ability to create macros and save time on predictable, repetitive tasks.