Setting up code syntax highlighting using the Visual Studio Code extension
We recently talked about our new Visual Studio Code extension allowing VS Code to communicate with 4D for code management. The syntax highlighting was the first Language Server Protocol feature in 4D v19 R6. Let’s see how to customize your source code rendering.
A brand new Visual Studio Code extension at your disposal
4D now supports the Language Server Protocol to allow external source code editors to handle 4D code and provide them with standard functionalities such as syntax highlighting, syntax help, go to definition, or type ahead. Let’s see how to take advantage of it in Visual Studio Code.
Directory file management in merged server projects
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.
Disabling explorers on merged servers
You may want to restrict administrators from accessing the Data Explorer and the Runtime Explorer in your deployed merged servers. 4D v19 R5 enables to do so.
Here is everything you need to know.
Saving project source code without tokens
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.
Use duplicated merged client applications
As a publisher, you sometimes want to duplicate a merged client application to connect each of them to their dedicated 4D Server. Let’s see how to do this.
Opening the Runtime Explorer
The Runtime Explorer is accessible to users belonging to the group having access to Design mode. Let’s see how to use it another way.
XML invisible characters on stage!
Default End Of Line character and Byte Order Mark usage in text files have been modified in 4D v19 R2. With 4D v19 R3, 4D extends this behavior to XML files. Let’s see how.
Bcrypt support for passwords
Security is a fundamental topic for today’s business solution systems. At 4D, we understand its importance; that’s why we keep delivering features that tackle this topic.
And with 4D v19 R3, 4D now uses a stronger hashing algorithm for user passwords. Let’s find out more!
An introductory guide to 4D and Version Control Systems
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!
Contact us
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