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

Understanding differences between synchronous versus asynchronous modes

As stated before, dialogs are asynchronous (async), this practically means the execution flow will not wait for the user to handle the dialog (close the message, respond to a question, prompt some values) before proceeding to the next instruction.

This simple yet very significant difference across the mobile and desktop worlds can be difficult to get, especially by experienced developers. You may be really acquainted with the synchronous (sync) model for dialogs. I've seen developers using dialogs for decades to pause the execution flow (ShowMessage debugging, anyone?), and relying on such behavior has a significant impact on your application design.

In very simple terms, on desktop platforms, the call to ShowMessage doesn't return control until the user closes the dialog, that is, you are assured that the next line of code you wrote after the ShowMessage call isn't executed until the user...