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 contains new and old (outdated) notes. After a while I have a lot of outdated nodes in the xml and would like to some cleanup. Is there a way for makeskel or some other tool to notify (generate some list) of outdate nodes (descriptions nodes that can't be matched to the source files anymore)? If 'lazde' doesn't have this feature, maybe it will be worth the effort adding it in. > We could add some map feature so it remaps nodes. > But that would mean you'll need to create the map. Nah, that sounds like work! :) Maybe we can improve 'lazde' so we can Cut, Paste and Rename nodes. That would at least help a bit. > > 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 text on a white background with a Courier font for the code. The one FPC and Lazarus used generates blue text on blue/white background with a nice font (not Courier). Peter (from tiOPF) also downloaded FPC 2.0.4 and Lazarus a few days ago and complained about the same thing. He said his HTML output looks nothing like the FPC docs or the tiOPF docs I host (which uses the css file I manually copied from the FPC website) Regards, - Graeme - _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
