Mattias Gaertner ha scritto:
[...]
For example the KOL package is a visual component library
similar to the LCL optimized for smart linking. Because the unit names
and class names are the same you can use lazarus to create/edit KOL
forms. The trick is that the user (here: programmer) does not use all
LCL properties, but only the small subset the KOL controls provide.
Find declaration and compilation use the KOL units, but the RTTI is
provided by the LCL.
IOW, if I properly set the paths, both for IDE and for compile, if my
components have the same class name as the original LCL, and their unit
name is the same, if I'm careful to touch only published properties
which are common to both LCL and my library, it should work. The IDE
will show LCL components on an LCL form, but when i run the program I
should see my components on my form.
It is planned to register your own designers for non LCL components,
but this has low priority for me, so don't expect anything soon.
I don't expect anything more than a few hints if I get stuck. I'm just
experimenting, and it's quite possible that nothing useful comes out.
There's already enough work for developers in the main line, I believe,
and side issue should wait.
However if something comes out which might be useful to someone else,
I'll share my results with Lazarus users.
Thanks a lot
Giuliano
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
