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

Learning about data binding

Historically, data binding in VCL has always had a TDataSet instance as subject. The data has always been stored in a TDataSet descendant and manipulated through the TDataSet interface (every experienced Delphi developer can list most of the method names of TDataSet, such as Edit, Post, Cancel, Prior, and Next). A TDataSet instance can be seen as a list (or array) of records, representing some dataset with a rectangular shape (rows and columns). The dataset has a state (a current record, a modality such as browsing versus editing, some filtering and/or sorting conditions, and so on) and acts like what today would be called a model for the data (including extended metadata and constraints).

Once we had a place to store data, the problem of surfacing this data to the UI became apparent. Delphi had a set of standard components used to manipulate strings, dates, multiple-choice selections, and a set of classes (components) to compose the UI in order...