Without sugarcoating it, 4D v17 R5 is 64-bit only! It’s no secret that many features, such as preemptive processes, new cache manager, 4D View Pro, and more are already only available in 64-bit. The bright side is that focusing on 64-bit systems makes it possible for us to incorporate more modern technologies and feature sets, as well as update many libraries. This change also brings new opportunities and in this blog post we’ll focus on the updated libraries and the positive impact on your 4D applications.
4D already provides commands to handle files and folders, but what about new commands that take advantage of the power of object notation?
Objects have changed the way many 4D developers write code, making it more generic, flexible, easier, and faster. Now this wave of change is extended to files and folders. In this blog post, we’ll show you how easy it is to manipulate an object in order to retrieve the attributes of a file or folder (rather than calling several commands and storing the information in multiple variables). Things are getting a lot easier!
In addition to the existing toolbar, we’re proud to announce the addition of a very powerful ribbon-style toolbar to enhance the 4D View Pro user interface. Just select an option in the Property List and you’re off and running!
As a developer or end user, you know how convenient hyperlinks can be. Without them, you would need to know the URL for every page on the internet! They let you turn your text or pictures into links to allow easy transitions from one place (e.g., a 4D Write Pro document) to another (typically a website).
What if links could offer more? What if they could launch the execution of 4D code or simply move the cursor to a different area in the same document? They can!
With v17 R5, 4D for iOS is shipped with a cool feature: Pull-to-refresh. It’s a very useful gesture, since all you need to do, to refresh your data, is scrolling to the top of the screen, then sliding your finger down. With this very intuitive feature, your app content is updated in a snap.
As promised in a previous post, each R-release includes more advances related to email functionality, unlocking its hidden power.
4D v17 R5 provides an interesting new feature for email logs. Sometimes during development everything works fine but when you deploy to the customer, there’s a problem delivering emails. Discovering where the failure occurs can be difficult, since the communication is encrypted and you often don’t have access to the SMTP server log files. The problem is very likely related to your SMTP server, but how can you be sure? Simply start the SMTP log in your application! This log contains a record of all the actions performed, including those stopping the connection. Even better, this log shows the communications with the SMTP server in plain, non-encrypted text, making it easier to analyze.
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.
4D has been a longtime supporter of team development, ever since 4D Server 1.0. The greatest benefit of working together on the same source code, is allowing both team development and team testing. However this can create some disadvantages for distributed teams since they may not be able to work on the same source.
Following a complete rewrite, 4D now supports two ways to work with sources: binary and project. Binary is the 4D we all know and love, with the source in a binary file to allow team development with 4D Server. Project makes it easier for distributed teams to work collaboratively by storing the source in a source control system in plain text files.
In a previous blog post, we announced new data encryption tools for your 4D databases. Now it’s time to get our hands dirty and learn more about these tools which were designed to be as automatic as possible.
A 4D object field is a persistent database field type, stored as binary content. Previously, reading this type of field by an ODBC driver wasn’t possible. Until today.
Before, an error was returned when trying to read an object field. This prevented the completion of simple Select * from myTable requests, which could be frustrating for users who only wanted to browse the content of a table.
Good news! The SQL engine has been updated to allow 4D object fields to be read.
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