Thanks for your time explaining it all Mattias. The reason I am interested in the LazDoc (part of IDE), is because I am trying to convince the tiOPF (Delphi) developers to rather use the fpdoc format, for documentation compared to embedded docs between the code. Writing a LazDoc type add-in for Delphi is what I am proposing, instead of using the external LazDoc Editor. Lazarus just rocks, compared to Delphi! ;-) I think I am slowly but surely convincing those Delphi developers to move to FPC and Lazarus.
- auto create missing fpdoc entries (e.g. after adding a method to the source). Basically the same as makeskel does, but on the fly for single entries. This is started for attributes and simple elements, but not yet for complex things like classes, methods, types, ... .
So what happens when you do the opposite? Eg: I refactored a class and removed a method not needed anymore. My fpdoc xml had documentation for that method, but now that method doesn't exist anymore. Will makeskel notify me that the method is now missing? What happens to the documentation in the xml file?
- use package/project fpdoc help when pressing F1. At the moment you have to manually register it via design time packages. The idea is: As soon as the lazdoc search path is set for a package: use it.
That would be neat! Creating the design time doc packages are really easy and use them a lot. It works perfectly! -- Graeme Geldenhuys Location: S 34° 03.168' E018° 49.342' http://tinyurl.com/y6lc26 There's no place like 127.0.0.1 _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
