[Lazarus] Documentation style

[Mattias Gaertner]

On Sun, 24 Jul 2011 23:52:44 +0100
Hans-Peter Diettrich <DrDiettrich1 at aol.com> wrote:

> Mattias Gaertner schrieb:
> 
> > The base units are independent of the widgetset units and the widgetset
> > units use the base units. So the package of widgetset units must use
> > the package of the base units.
> > Theoretically: If the base package would be named 'LCL', then
> > all existing projects would no longer work, because they misses the
> > widgetset units.
> 
> Why then have separate packages at all, when every GUI application 
> depends on both?

There are two type of output directories.

 
> >>From the users point of view the LCL split is the same as if
> > a big package was split into two. The upper package keeps the original
> > name for compatibility. Compilation works, but fpdoc links get into
> > trouble.
> 
> Building old projects (examples...) now fails, because these depend on 
> LCL, not on LCLbase :-(

For example?

 
> > This is because the inheriting of packages is not (yet) implemented for
> > fpdoc. It's not a big task to implement this for the IDE code hints,
> > but I don't know yet about the rest of fpdoc. I can take a look after
> > my vacation.
> > 
> > In other words:
> > Eventually both fpdoc links "#LCL.Controls" and "#LCLBase.Controls"
> > should work. But of course #LCLBase.Controls is more correct.
> 
> IMO "#LCL.Controls" and "#Widgetsets.whateverelse" would be more 
> appropriate.

An example for widgetsets: #LCL.gtk2wsstdctrls.

Mattias