Component Library for Cross Platform: Difference between revisions
imported>Bubba73 mNo edit summary |
imported>Onel5969 m Disambiguating links to Object-orientation (link changed to Object-oriented programming) using DisamAssist. |
||
| Line 5: | Line 5: | ||
However, due to lackluster performance on Windows, subtle differences from VCL, and bugs, it did not become the expected successor to VCL. The commercial failure of Kylix stopped further development of CLX. | However, due to lackluster performance on Windows, subtle differences from VCL, and bugs, it did not become the expected successor to VCL. The commercial failure of Kylix stopped further development of CLX. | ||
In terms of [[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. | 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]]. | 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]]. | ||
Latest revision as of 09:44, 29 July 2025
Component Library for Cross Platform (CLX) (pronounced clicks), is a cross-platform visual component-based framework for developing Microsoft Windows and Linux applications.[1][2] It was developed by Borland for use in its Kylix, Delphi, and C++ Builder software development environment.
Its aim was to replace the popular Microsoft Foundation Classes with Visual Component Library (VCL). CLX was based on Qt by NokiaScript error: No such module "Unsubst"..[3]Template:Rp The 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. The commercial failure of Kylix stopped further development of CLX.
In terms of object-oriented approach, CLX forms an object hierarchy where the TObject class serves as the 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. By docking to different widgetsets, the LCL is able to support an even larger spectrum of platforms including Mac OS X and Android.
References
<templatestyles src="Reflist/styles.css" />
Script error: No such module "Check for unknown parameters".
Script error: No such module "Navbox". Script error: No such module "Navbox".