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

Introducing animations and transitions

Modern UIs have plenty of animations. Today, many visual elements are enriched due to transitions, which means that lateral panels, menus, and more are now closed and opened through fancy, smooth visual transitions. It has not always been like that, though.

Basically, if we reduce our programming world to the iterative and discrete model, we can understand what it would mean to change the size of a panel from 300 pixels down to 80 pixels. Most programmers would come up with some kind of loop code instead of a single step to change the value, as the following snippet of (pseudo) code tries to exemplify:

// one step change:
MyPanel.Width := 80;

// multi-step change:
while MyPanel.Width > 80 do
MyPanel.Width := MyPanel.Width -1;

From the preceding code, you can see that a number of under-the-hood aspects are involved here. For example, it may not be granted that assigning a new value to the Width property will cause the component to redraw itself...