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 the anatomy of a style

So far, we have learned that FMX has the capability to apply different styles to the same application. A style is composed of a list of definitions (one for each UI element, that is, component) that are built as a composition of basic elements (like shapes or images) and/or other styled elements, making the whole mechanism really powerful and extensible.

If you are an experienced VCL developer, you can see the style definition as a sort of DFM file, where the structure of components is defined together with property values determining specific characteristics of each element. We never addressed the fact it is not trivial to provide a complete definition of the visual asset of a component.

This becomes even harder while keeping in consideration that this definition should be sophisticated enough to deliver a proper version of the component for each supported platform (up to five different platforms!) and considering all the surrounding difficulties...