The VCL Persistence Framework comprised of a set of components, property and component editors.
The initial concept for this project started on 7 Jul 2004, but work on it didn't began until a few weeks ago. [Note: I've found further evidence that indicated I've started toying with this idea even earlier, on 25 May].
Each component within the VCL Persistence Framework has the ability to store and retrieve its value from a persistent storage, such as an INI file, the registry, a XML file or any of it's related descendents derived from a common ancestor.
The purpose of the VCL Persistence Framework is to allow me to quickly develop programs, without concerning myself with storage of the values specified in the components, since all I did to do was set it up properly initially, and the components would do the rest of the work themselves.
The components themselves behave (hopefully) like the database components written by Borland itself.
More articles about these components will be coming soon...
In 2017, with the release of Delphi 10.2 Tokyo, Embarcadero introduced a specialized implementation of the Observer pattern into the System.Classes unit. While it has been in the wild for 9 years, it remains a "hidden" architecture for many, primarily because it serves as the invisible engine behind LiveBindings. Other than live bindings, you can also use the Observer pattern as a way to update component settings to the Windows registry, an .ini file, or persist it elsewhere.
System.Classes