[Lazarus] nonlcl basic issue: is codetools LCL dependent?

[Giuliano Colla]

Il 27/06/2014 11:09, Marco van de Voort ha scritto:
> On Mon, Jun 23, 2014 at 11:48:53AM +0200, Giuliano Colla wrote:
>> implementation part is demanded to some third party Widgetset (such as
>> gtk, qt, Windows, etc.), via an Interfaces unit.
>> This is not compatible with other implementations, such as Kylix and
>> fgGui, just to mention two.
> It is compatible with Kylix, since in CLX QT is hardcoded too afaik?!!?

You're right, in Kylix CLX Qt is hardcoded. Therefore it's different 
from LCL scheme virtual/abstract - interface.
This makes it impossible to use the features of IDE Designer as it is 
for a Kylix project.
LCL scheme makes it possible to use different widgetsets at design time 
and at run time, but requires that all of them follow the same rule of 
virtual/abstract+Interface. Moreover IDE designer defaults to LCL 
classes properties and methods, and doesn't allow duplicates.If a Kylix 
class has the same name of an LCL class, you'll be unable to design. 
TForm is the first one!

If, with some kludges, you manage to use the IDE designer as it is, for 
a Kylix project, it will only be aware of LCL methods and properties, 
and you'll end up both with Kylix unsupported methods and properties, 
and with Kylix required methods and properties dropped because 
unsupported by LCL.

This sums up in being incompatible.

Giuliano