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

Exploring FormatOptions properties

The FormatOptions property has the following sub-properties:

  • MapRules: A dataset may be seen as a sort of abstraction over some data storage format (in the case of a classic DBMS, it may represent a table or query result set). This abstraction is based on rows (records) and columns (fields) and each column is usually associated with a specific data type (a string, an integer number, memo text, and so on).

The way a data access library binds the native type of data to a column type can have a very significant impact on the application development and also on the evolution of the data storage through time. If you are an experienced developer, you surely have faced this before and you know how handy it can be to have a way to fine-tune the mapping rules your DAC library applies to construct datasets.

Sometimes the database architect uses some conventions to mark all integer fields with a name starting with B_ that are in fact Boolean values...