ORDA has its share of features with 4D v17 R5, including various ways to write generic code.
Writing generic code allows you to centralize your code to facilitate updating it. Not only does it enable you to write reusable code that can be used in different use cases, freeing you from having to reinvent the wheel again and again, it also lets you add extra functionalities on top of what you’ve already done.
View settings are used to define how a document should be displayed. Until 4D v17 R5, these settings could only be modified using the contextual menu or standard actions. Now they can also be set and get within an object using new commands, as we explained in this blog post. But you can do even more, because these settings can be saved and re-applied afterward! You’ll definitely appreciate having your settings saved!
The New formula command is available since 4D v17 R3. So far you might have thought of assigning a formula as a method to an object or building smart objects that can calculate values or do anything you need. That’s really great, and there’s more than meets the eye!
I had a great demonstration from Vincent de Lachaux – Developer and expert 4D – on how he uses this command. For this blog post, I compiled different scenarios from that demo to give you insight on a different dimension of this command.
Do you need to access your 4D data from a web page but don’t have a designer in your team? Are you uncomfortable designing the pages yourself because deep down you believe that it’s full of complicated and unwritten rules? Well, have you ever thought about Bootstrap?
In this blog post, we’ll look at how to take advantage of Bootstrap’s framework to design web pages in no time! We’ll also provide you with a database example to see how it can be combined with 4D transformation tags.
4D Write Pro has no default interface because it’s meant to be embedded in your application. Therefore, it needs to fit your user interface design and provide just the right amount of features for your use case(s). We decided to provide you an easy way to create your own interface with Standard Actions. Since starting from scratch is not always easy, we’ve made widgets available that you can use directly. Better yet, if you’re a partner, you can even customize them (i.e., remove features, change the order/organization of tabs, buttons, etc.)!
In this blog post, we’ll go through the interface possibilities offered by 4D Write Pro.
We began a series of blog posts on compatibility settings and the secret options that can drastically help improve the performance and behavior of your applications (QUERY BY FORMULA, Transactions and period and comma). This final post of the series will give an overview of the remaining settings.
We’ve received comments on the forum and TAOW about features that previously existed in the 4D Write plug-in but seem to be missing in 4D Write Pro. Yet, they’ve been available for a long time!
In this blog post, we’ll go through a list of existing abilities in 4D Write Pro that seem to have gone unnoticed. In another words, 4D Write Pro features you didn’t know existed.
After all, 4D Write Pro is not limited to WP commands!
Thanks to 4D v17 R3, you can export your structure file in multiple text files. For example, with only a few lines of code you can create a copy of your database every morning. You can use this to keep track of the history or to send your database to a colleague and see the changes when they’re done working on it.
We provide you a ready-to-use component with only two methods: one to configure the data to be exported, and the other to export your database.
4D Write Pro has become a mature product with a lot of functionalities, surpassing the 4D Write plug-in in many areas (tables and bookmarks, for example). Furthermore, 4D Write Pro is 64-bits compliant, which is great since most operating systems will soon be 64-bits only. Migrating your documents from 4D Write to 4D Write Pro is a “must do”. In order to help you and your customers’ migrations, we’ve simplified the migration process with a ready-to-use component!
Welcome to our ongoing series about compatibility settings and “hidden” features for improved performance. In the first post, we looked at the QUERY BY FORMULA command and its impact on an application’s behavior. The second post was about the “Use period and comma as placeholders” compatibility option to avoid running into “the numbers are displayed as >>>>>>>>>” hassle.
In this third installment, we’re going to explore Nested Transactions.
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