[Lazarus] nonlcl basic issue: is codetools LCL dependent?
Giuliano Colla
giuliano.colla at fastwebnet.it
Thu Jun 26 15:54:24 CEST 2014
Il 25/06/2014 15:16, Michael Schnell ha scritto:
> On 06/24/2014 09:30 AM, Giuliano Colla wrote:
>
>> Widget Types are LCL related. It's the part which actually implements
>> virtual abstract methods in the Interfaces unit.
>
> Yep.
> So it seems perfectly suitable to individually define the
> functionality of classes that share a common name.
>
[...]
Only if you implement a widgeset using the same mechanism of virtual
abstact methods, and all properties and methods are identical to those
supported by LCL, which isn't true in general. At least not for Kylix
and FpGui.
Just a trivial example: Kylix TForm has a Bitmap property to provide a
background image to the form. LCL doesn't. Either you add this property
to LCL, implement it in each widgetset, making unhappy the supporters of
"native look", or you drop this property, and do not support a feature
which is used in hundreds of applications, to provide users an easy
visual feedback.
LCL is but one way to go. It has pros and cons. But it's not the only one.
Giuliano
More information about the Lazarus
mailing list