[Lazarus] nonlcl design basic issue

[Mattias Gaertner]

On Sun, 15 Jun 2014 18:45:27 +0200
Giuliano Colla <giuliano.colla at fastwebnet.it> wrote:

>[...]
>  1. Surrounding with appropriate $IFDEF LCL / $ELSE the sources of my
>     widgetsets to differentiate what should be visible at design time
>     from what should be visible at run-time.

Pro: code navigation is easier (e.g. jumping between
active implementation and interface)
Con: you can only work in one part at a time (many codetools will only
work in the active IFDEFs). You have to switch often the active build
mode.


>  2. Going the same way as LCL, and taking advantage of an "interfaces"
>     unit, which provides the actual implementation of virtual methods.

Pro: You don't need build modes.
Con: You often have to search the implementation of abstract base
methods.


Mattias