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

Binding a component to its style

We said we have a TButton instance on our form. We learned there are (at least) four platform styles included by Embarcadero and that each style contains an entry for every standard component. What about how the component and the style definition are matched?

The matching algorithm will take the name of the class of the component (TButton), lowercase it (tbutton), strip the initial T (button), and add a conventional style suffix (buttonstyle). The resulting buttonstyle name will be used to look up an entry in the style definition for every TButton component.

A simple override for this selection mechanism is provided through the StyleLookup property (introduced in the TStyledControl class) where a different style name can be specified instead of the conventional default.

Each application has a default style (the matching platform style, by default), but we'll see in the following sections how to include a custom style and select it as default, as well...