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

Synchronous versus asynchronous execution

Generally speaking, multithreaded programming is one of the most difficult topics to master as a developer. As human beings, we are intrinsically used to thinking sequentially and many programming languages (like Pascal) have been designed to be used in an imperative, synchronous, deterministic paradigm. We usually design our code thinking in terms of a sequence and making the assumption that steps are not overlapping (and that they follow the first-in-first-out approach, for example).

Let's try to use a real-world example of a sequential operation that we feel is naturally sequential and where the need for synchronization is completely transparent (as we are used to automatically managing underlying complexity as human beings). Think about serving yourself a glass of water. The sequence seems pretty straightforward:

  1. Put the glass on the table.
  2. Open the bottle.
  3. Pour water into the glass.
  4. Close the bottle.
  5. Get the glass.
  6. Drink the glass of...