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 actions

Actions and action lists were introduced in version 4, and I have used them largely in VCL projects. Actions are a great yet simple way to properly divide application code from the presentation layer, providing an abstraction of something that can be executed and an easy way to bind the execution trigger to one or more UI elements.

The fact that abstraction is available for manipulation at design time is a great benefit in terms of the RAD approach. But at the same time, it keeps your code cleaner than having it spread out through event handlers of your UI elements.

Additional features include the ability to define a hint text and an image of the action (helping to achieve a visual continuity throughout your UI) and to define when the action is enabled and/or visible in a single code point (the OnUpdate event handler).

If you are an experienced Delphi developer, you will be happy to know that actions have been refactored in order to be shared...