Simplifying Data‑Aware UI in Delphi with LiveBindings
Learn how Delphi LiveBindings let you declaratively link UI controls to data, cutting boilerplate code while keeping the UI responsive and maintainable.
Loading…
ReadMeFeed / Community knowledge
#vcl
Real questions. Useful conversations. Find the people who know your stack.
delphiUsing LiveBindings in RAD Studio to Wire VCL Controls to a ClientDataSet
Learn how to bind a TEdit to a dataset field with LiveBindings, see the setup steps, a worked example, and the trade‑offs to consider.
Connecting a VCL Application to SQL Server Using FireDAC in RAD Studio
Learn how to link a VCL form to SQL Server with FireDAC, run a parameterized query, and show results in a grid while handling errors and cleaning up resources.
Using RAD Studio LiveBindings Designer to Bind VCL Controls to Data Without Boilerplate
Learn how RAD Studio’s LiveBindings Designer lets you bind VCL/FireMonkey controls to datasets visually, cutting boilerplate code while keeping full two‑way data sync.
Reduce UI Boilerplate with RAD Studio LiveBindings in Delphi VCL
Learn how LiveBindings lets you declaratively sync TEdit, TLabel and other controls with data model properties, cutting manual event‑handler code.
Using Delphi LiveBindings to Keep VCL Controls in Sync with Data
Learn how to bind a TEdit to a TDataSet field with LiveBindings, reducing boilerplate code while understanding the trade‑offs.
Move Long‑Running Work Off the VCL Main Thread Using Delphi’s TTask and TThread.Queue
Learn how to keep a VCL/FMX form responsive by offloading blocking work to TTask and marshaling UI updates safely with TThread.Queue.
Choosing Delphi Generics for Type‑Safe Collections in VCL and FireMonkey
Learn how Delphi generics provide type‑safe collections and algorithms with zero runtime overhead, see a reusable cache example, and verify specialization via the map file.
VCL dual‑project versus FireMonkey single‑source for Windows/macOS RAD Studio applications
When targeting both Windows and macOS with RAD Studio, a developer can either maintain two separate VCL projects—one compiled for each OS—or adopt a single FireMonkey codebase that builds for both platforms. The goal is to choose the approach that satisfies the need for native Windows look‑and‑feel and direct Win32 API access while keeping overall maintenanc