The list of possible nodes is found, of course, in the FPDoc manual.
Some examples of fairly densely populated descriptions are in StdCtrls,
DBCtrls, Dialogs, and also in Controls, Graphics, and Forms. In general
the TCustom components are the most fully described. StdCtrls,
DBCtrls, Menus
Hi Mattias -
I note from the bug report 0010686 that you have fixed the immediate
problem, and on re-building Lazarus from SVN this morning I find that I
can now save short descriptions from LazDoc in the IDE, and also
things that I type in other boxes such as description.
However the
Zitat von Chris Kirkpatrick [EMAIL PROTECTED]:
Hi Mattias -
I note from the bug report 0010686 that you have fixed the immediate
problem, and on re-building Lazarus from SVN this morning I find that I
can now save short descriptions from LazDoc in the IDE, and also
things that I type in
Hi John, Joost and Adrian -
As you might know, I have been trying to get the documentation for parts
of the Lazarus Component Library (LCL) into shape, mainly by putting
information into the .XML files associated with each Unit, to enable
generation of .HTML files using FPDoc. Quite a few
Chris Kirkpatrick wrote:
Hi John, Joost and Adrian -
snip
So I should very much like to collaborate with you guys in improving
the documentation of sqldb and fc-db, as well as the stuff in the LCL.
I agree we should try to use the FPDoc approach as suggested by Joost.
snip
_
I agree with
Zitat von John [EMAIL PROTECTED]:
Chris Kirkpatrick wrote:
Hi John, Joost and Adrian -
snip
So I should very much like to collaborate with you guys in improving
the documentation of sqldb and fc-db, as well as the stuff in the LCL.
I agree we should try to use the FPDoc approach as
Explanation of some Lazarus documentation terms:
FPDoc - the command-line tool that is part of FPC and is documented in
the FPC manuals. Includes MakeSkel, for constructing a skeleton XML file
from the unit source code.
LazDE, aka Lazarus Documentation Editor - an application found in
Hi Mattias -
I have looked at LazDoc in the IDE. It is very nice in principle, and
allows us to copy inherited properties, for example. However, I cannot
save any changes that I make with LazDoc in the IDE. If I make a change
and press SAVE, then go to another property, when I come back to
