Book Image

Delphi Cookbook - Third Edition

By : Spinetti, Daniele Teti
Book Image

Delphi Cookbook - Third Edition

By: Spinetti, Daniele Teti

Overview of this book

Delphi is a cross-platform integrated development environment (IDE) that supports rapid application development on different platforms, saving you the pain of wandering amid GUI widget details or having to tackle inter-platform incompatibilities. Delphi Cookbook begins with the basics of Delphi and gets you acquainted with JSON format strings, XSLT transformations, Unicode encodings, and various types of streams. You’ll then move on to more advanced topics such as developing higher-order functions and using enumerators and run-time type information (RTTI). As you make your way through the chapters, you’ll understand Delphi RTL functions, use FireMonkey in a VCL application, and cover topics such as multithreading, using aparallel programming library and deploying Delphi on a server. You’ll take a look at the new feature of WebBroker Apache modules, join the mobile revolution with FireMonkey, and learn to build data-driven mobile user interfaces using the FireDAC database access framework. This book will also show you how to integrate your apps with Internet of Things (IoT). By the end of the book, you will have become proficient in Delphi by exploring its different aspects such as building cross-platforms and mobile applications, designing server-side programs, and integrating these programs with IoT.
Table of Contents (12 chapters)

Communication made easy with Delphi Event Bus

A typical Delphi application tends to be composed of many layers, modules, or structures, such as Forms, Views, Presenters, Data Modules, and Services. Effective communication between these components can become difficult if they are tightly coupled together.

In the lower level of your app architecture, such as the Data Module, when an action happens, you might want to send data to a higher level, such as the view (Form). To do this, you might want to create a listener interface, async tasks, or callbacks. All of these will work, but they have some major drawbacks:

  • Direct or tight coupling of components
  • Inflexible, changes are expensive
  • Boilerplate code
  • Propagation through all layers
  • Repetition of code
  • Difficulty in testing
  • Increased risk of bugs

All of these things are brilliantly solved by modern model-view-whatever (MVW) frameworks...