Component Library for Cross Platform: Difference between revisions

Content deleted Content added
Undid revision 842146998 by 176.80.0.94 (talk) Article vandalised to inconsistent state ... which isn't the way to go about things ... probable response to the deprod.
m Disambiguating links to Object-orientation (link changed to Object-oriented programming) using DisamAssist.
 
(19 intermediate revisions by 10 users not shown)
Line 1:
'''Component Library for Cross Platform''' ('''CLX)''') (pronounced clicks), is a cross-platform visual component-based framework for developing [[Microsoft Windows]] and [[Linux]] applications.<ref name="Blong-1"/><ref name="LBNL-1"/> It iswas developed by [[Borland]] for use in its [[Kylix programming tool|Kylix]], [[Delphi (programming language)|Delphi]], and [[C++ Builder]] software development environment.
{{Unreferenced|date=December 2009}}
'''Component Library for Cross Platform (CLX)''' (pronounced clicks), is a cross-platform visual component-based framework for developing [[Microsoft Windows]] and [[Linux]] applications. It is developed by [[Borland]] for use in its [[Kylix programming tool|Kylix]], [[Delphi programming language|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 (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 lacklustrelackluster performance on Windows, subtle differences from VCL, and bugs, it didn'tdid 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]].
 
==See alsoReferences==
{{Reflist|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>
 
<ref name="LBNL-1">{{cite web|title=Cross Platform Development using Delphi and Kylix|date=22 October 2002|url=https://escholarship.org/uc/item/3502t2p
|first1=J.L.|last1=McDonald|first2=H.|last2=Nishimura|first3=C.|last3=Timossi|publisher=[[Lawrence Berkeley National Laboratory]]
|url-status=live|archive-url=https://web.archive.org/web/20181007144645/https://escholarship.org/uc/item/3502t2p2|archive-date=7 October 2018|df=dmy-all}}</ref>
 
<!-- Self Pub/blog -->
 
<ref name="Blong-1">{{cite web|title=VCL versus CLX|url=http://www.blong.com/Conferences/DCon2001/VCLvsCLX/VCLvsCLX.htm|access-date=7 October 2018
|website=BLong|first=Brian|last=Long
|url-status=live|archive-url=https://web.archive.org/web/20180322035403/http://www.blong.com/Conferences/DCon2001/VCLvsCLX/VCLvsCLX.htm|archive-date=22 March 2018|df=dmy-all}}</ref>
 
}}
{{Pascal programming language family}}
{{Widget toolkits}}
Line 17 ⟶ 31:
[[Category:Borland]]
[[Category:Component-based software engineering]]
[[Category:Pascal (programming language) libraries]]
[[Category:Computer libraries]]