Component Library for Cross Platform: Difference between revisions

Revision as of 03:15, 25 January 2024

Latest revision as of 09:44, 29 July 2025

(2 intermediate revisions by one other user not shown)

Line 3:

Its aim was to replace the popular [[Microsoft Foundation Classes]] with [[Visual Component Library]] (VCL). CLX was based on [[Qt (framework)|Qt]] by [[Nokia]]{{Citation needed|reason=MasterD6 source says Trolltech not Nokia, but Norwegian is concordant|date=October 2018}}.<ref name="MasterD6"/>{{rp|196}} The [[Application programming interface|API]] of CLX almost completely followed VCL. It was envisioned that existing applications using VCL would be recompiled with CLX.

However, due to lackluster performance on Windows, subtle differences from VCL, and bugs, it did not become the expected successor to VCL. CommercialThe commercial failure of Kylix stopped further development of CLX.

In terms of [[Object-oriented programming|object-oriented]] approach, CLX forms an object hierarchy where the TObject class serves as the ''[[Superclass (computer science)|base class]]''. All other classes inherit or indirectly inherit the TObject class.

Today, many concepts that were defined with CLX have been implemented with the [[Lazarus Component Library]] (LCL) for the [[Lazarus (IDE)|Lazarus]] IDE. By docking to different [[widgetset]]s, the LCL is able to support an even larger spectrum of platforms including [[Mac OS X]] and [[Android (operating system)|Android]].

==References==

{{Reflist|2|refs=

<ref name="MasterD6">{{Cite book|title=Mastering Delphi 6|chapter=Chapter 6: Controls: VCL Versus VisualCLX|first=Marco|last=Cantù|publisher=Wiley|isbn=978-0-782-15278-4}}</ref>