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 the DRY principle

One of the most impactful strategies you can set up in your application flow is to provide the user with some common UI elements throughout the application, no matter what state the application is in. Think about some borders or some graphic elements acting as branding for the general look and feel of the app. The actual content may change but the frame, that is, around the main spot, may be the same and lets the user stay in a familiar environment all the time. This way, the user will feel at home all the time and will be more prone to focus on the actual content as it is the thing that really changes before their eyes.

The same is true for transitions across views, that is, if you provide the user with a way to go from state A to state B (meaning the transition is allowed), then you implement the transition using an animation (possibly meaningful). It would be very convenient to keep the same convention when going from state B to state C. Obviously...