Tips

Tips & Tricks for your 4D Apps – June Edition

Automatically translated from English

by Add Komoncharoensiri, Director of Technical Services at 4D Inc

 

Here we go with another set of tips and tricks.

As you know, 4D Knowledge Base is a library of information about the 4D technology where weekly tech tips and monthly technotes are actively published. If you missed the last tips on the KB, that’s fine; here is a compilation from the past few weeks.

This blog post covers 16 tips:

Tips

GitHub 4D Awesome List — Call for Contributions

Automatically translated from English

To stay competitive in the software industry, one should always seek innovation and build momentum for change.

In that spirit, 4D has always given you the right technology to grow and expand. Project mode is one example that comes with a tremendous benefit: the ability to use Git to get your 4D application up and running in a more productive development environment.

So we decided to create a 4D Awesome list, where we gather all the collective wisdom in one place to make 4D developers’ life a little easier.

If you’re a Git/GitHub user and have a fantastic project that you believe could help fellow developers, you might want to contribute to the 4D Awesome list, where awesome projects live!

This blog post explains the concept of an Awesome list and how you can contribute.

Tips

4D and Git: From Beginner to Expert

Automatically translated from English

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.
News

An introductory guide to 4D and Version Control Systems

Automatically translated from English

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!

Tips

How to take advantage of GitHub actions with 4D

Automatically translated from English

Your project is now on a source control system. This means that managing several versions of your software, monitoring changes, and integrating corrections or new features is much simpler now.

Why not also take advantage of continuous integration?

Starting with 4D v19, you can launch the compilation of your project with a command. As a result, you now have all the building blocks needed to automate your integration chain.

This blog post will give you an example of automation with the GitHub manager and GitHub Actions.

Product

gitignore and 4D: a useful feature for Git users

Automatically translated from English

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.

Tips

Project databases: Git. Commit. Pull. Push & more

Automatically translated from English

In a previous blog post, we introduced you to Git (a version control system) and Github (a cloud-based hosting service) and how you can share your 4D code with other developers. In this blog post, we’ll go a bit further by exploring some scenarios a developer may encounter, such as cloning a remote repository, ignoring already committed files, and solving merge conflicts.