Book Image

Delphi GUI Programming with FireMonkey

By : Andrea Magni
4 (1)
Book Image

Delphi GUI Programming with FireMonkey

4 (1)
By: Andrea Magni

Overview of this book

FireMonkey (FMX) is a cross-platform application framework that allows developers to create exciting user interfaces and deliver applications on multiple operating systems (OS). This book will help you learn visual programming with Delphi and FMX. Starting with an overview of the FMX framework, including a general discussion of the underlying philosophy and approach, you’ll then move on to the fundamentals and architectural details of FMX. You’ll also cover a significant comparison between Delphi and the Visual Component Library (VCL). Next, you’ll focus on the main FMX components, data access/data binding, and style concepts, in addition to understanding how to deliver visually responsive UIs. To address modern application development, the book takes you through topics such as animations and effects, and provides you with a general introduction to parallel programming, specifically targeting UI-related aspects, including application responsiveness. Later, you’ll explore the most important cross-platform services in the FMX framework, which are essential for delivering your application on multiple platforms while retaining the single codebase approach. Finally, you’ll learn about FMX’s built-in 3D functionalities. By the end of this book, you’ll be familiar with the FMX framework and be able to build effective cross-platform apps.
Table of Contents (18 chapters)
Section 1: Delphi GUI Programming Frameworks
Section 2: The FMX Framework in Depth
Section 3: Pushing to The Top: Advanced Topics

Learning about futures

Last but not least, we can find goodies in the PPL, which are futures. A future can be defined as a value that we already know we'll need in the future. The key point is getting (calculating, building, retrieving, and so on) a value that is expensive in terms of computation resources (CPU, time, network, and so on), and that we don't want to affect the main/UI thread with this burden. 

The following code shows the implementation of a future:

LFuture: IFuture<Integer>;
LFuture := TTask.Future<Integer>(
function : Integer
Sleep(5000); // Do something...
Result := 42;


The previous code example shows how a future is defined. Basically, we provide a builder function that is capable of returning our value and we wrap this function in a task.

The future implementation relies on another modern language featuregenerics. We are trying...