In code kitchens, I usually spend some time with the database settings, especially with the Compatibility settings. Often certain settings don’t follow best practices and during discussions with the application developer, I hear “oh, I never changed these” or “I’m not sure about the impact, so better not touch them”.
Since they could drastically impact the performance or behavior of your applications, we’ve begun a series of blog posts to discuss some of these “secret” settings.
In the first episode of this trilogy, we demonstrated the basics of ORDA using list boxes, entities, and entity selections. Today, we’re going a bit deeper by running some queries that will take advantage of recursive relationships. We’ll also have a quick look at how to display list boxes nicely using the “meta info expression” property.
Your iOS app is complete and you’re ready to deploy? Now it’s time for you to choose the appropriate Apple Developer Program. Apple provides various programs for you to choose from: for App Store deployment, in-house deployment, or just for testing.
Don’t panic, we’ve got you covered! If you’re still wondering which Apple Developer Program best fits your needs, then keep reading.
We can all agree that ORDA is a great 4D V17 feature. A kind of revolution in the way of thinking and programming. 4D databases will never be seen the same way as before.
ORDA allows you to conceive advanced applications in less time, with more readable and clean code. To show you the power of ORDA we’ve prepared a series of tips for you, divided into three episodes. In this first episode, we’ll demonstrate how links should now be considered more as entities and entity collections, and we’ll show you how listboxes can now be based on entity selections, rather than selections or arrays.
We know that sometimes you want to change the properties of multiple methods without having to open the property dialog for each method.
For example, you want to set all methods to “Can be run in preemptive mode” status, then compile your database. So with compilation errors, you get an overview of the methods to modify to be preemptive.
Using the METHOD GET NAMES command to retrieve the list of methods from your database, and then using the METHOD SET ATTRIBUTES command to modify the attributes, lets you modify them all at the same time!
Do you need to create a 4D View Pro document using code, without any user interface? It’s possible! Because 4D View Pro documents are objects, it’s very easy to create off-screen documents. You can create a new document in a variable of object type and manipulate it through its properties. When your document is ready, you can register it in your database, in a file, or display it directly in a 4D View Pro area.
ORDA was one of the major announcements of 4D Summit 2018, opening a world of new possibilities in 4D. To learn more about ORDA and its benefits, check out this post to see how ORDA will change the way you work.
Humans have different taste preferences. For instance, some people prefer white over all other colors, while others find black to be more majestic … hence any new color trend tagged as ‘the new black’!
In order to accommodate different preferences, 4D enables you to personalize the method editor theme!
In the 4D preferences dialog, you can set several parameters for the editor such as the color of the background or each type of code element (i.e., commands and comments).
Thanks to these different options, you can completely customize the method editor to your taste. Whether you’re a fan of light or dark themes, 4D’s got you covered!
Here’s what a dark theme looks like:
Imagine you have a list of formulas containing table names and some fields … then days later you decide to rename your tables. Now your formulas are no longer valid, which is totally understandable!
Well, good news: the new Parse formula command allows your formulas to remain valid when renaming 4D language or structure elements.