What's the difference between a Delphi application developer and a Delphi component developer?
The difference, I've read elsewhere, is that a Delphi application developer doesn't have to know OOP, and can develop a Delphi program without much effort. Consequently, it is said that, that helps Borland to sell more Delphi products, because the learning curve to using and developing a Delphi program is pretty low.
What do you think?
In other news, I have now implemented a modern hinting system for “My RSS Reader”.
The modern hinting system uses the ToolTip control as implemented by Common Controls 4.7 and 5.8. It is implemented by deriving from (or when I was programming in OWL more than 12-14 years ago, subclassing) THintWindow, and placing the new THintWindow's metaclass reference into HintWindowClass. More about the design of the new THintWindow descendant (or subclass) in the future.
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