Hi,
What is the best method to clean up documentation files after a class
or unit refactor was done. My xml files are all outdated now -
referencing methods or sometimes even classes that don't exist
anymore.
What is the options available to me. Lets hope I have more choices
than to recreate the
On Tue, 14 Aug 2007, Graeme Geldenhuys wrote:
Hi,
What is the best method to clean up documentation files after a class
or unit refactor was done. My xml files are all outdated now -
referencing methods or sometimes even classes that don't exist
anymore.
What is the options available
On 14/08/07, Michael Van Canneyt [EMAIL PROTECTED] wrote:
Well, makeskel has an update option. It will generate nodes for all
missing elements.
Sorry, maybe I was a bit unclear. I know it's got the update option.
So after a refactor, I update my xml with makeskel. Now my description
xml file
Graeme Geldenhuys schreef:
ps:
Will the fpdoc.css file used by FPC and Lazarus docs be included as
the default in the next FPC release? The default css file in FPC
2.0.4 look crap compared to the one used on the web.
? It's the same file.
Not in my copy. The one with 2.0.4 generates black
Vincent Snijders schreef:
Graeme Geldenhuys schreef:
ps:
Will the fpdoc.css file used by FPC and Lazarus docs be included as
the default in the next FPC release? The default css file in FPC
2.0.4 look crap compared to the one used on the web.
? It's the same file.
Not in my copy. The one
On 14/08/07, Michael Van Canneyt [EMAIL PROTECTED] wrote:
fpdoc notifies you of nodes it cannot find. The opposite (unused nodes)
has not yet been done, but should be easy to add.
I'll have to play with fpdoc some more... I'm currently writing a
little fpGUI app (just because I can smile),
