Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-27 Thread Marco van de Voort
On Sat, Dec 20, 2014 at 07:06:09PM -0300, silvioprog wrote: Yes, I want it too, and this is a very nice option (I use a similar approach in other IDEs). The documentation generated by the FPDoc is not responsive (e.g: http://goo.gl/bCJoPM), i.e., it does not open well on a mobile device.

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread Mattias Gaertner
On Fri, 19 Dec 2014 18:58:01 -0300 silvioprog silviop...@gmail.com wrote: Hello, What is the most recomended tool to make documentation?: 1. http://wiki.lazarus.freepascal.org/LazDoc; 2. http://wiki.lazarus.freepascal.org/Lazarus_Documentation_Editor. I'm writting a new component and I

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread Graeme Geldenhuys
On 2014-12-19 21:58, silvioprog wrote: What is the most recomended tool to make documentation?: I simply use my favourite text editor (EditPad Pro) and code templates. I don't use indentation in the XML files because unfortunately that screws with some fpdoc output formats where spaces are kept

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread Mattias Gaertner
On Sat, 20 Dec 2014 11:18:36 + Graeme Geldenhuys mailingli...@geldenhuys.co.uk wrote: On 2014-12-19 21:58, silvioprog wrote: What is the most recomended tool to make documentation?: I simply use my favourite text editor (EditPad Pro) and code templates. I don't use indentation in the

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread Graeme Geldenhuys
On 2014-12-20 11:29, Mattias Gaertner wrote: What does it not allow exactly? The built-in editor does very weird indentation, and there is no option to switch indentation off completely. Here is a quick example I just created with the built-in editor. Also note that the built-in editor simply

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread leledumbo
I'm writting a new component and I want to use a doc creator tool available in own Lazarus My recommendation: fpdoceditor.png http://free-pascal-lazarus.989080.n3.nabble.com/file/n4039867/fpdoceditor.png I don't really care about the generated XML as long as it's compilable. I edit from this

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread silvioprog
On Sat, Dec 20, 2014 at 8:18 AM, Graeme Geldenhuys mailingli...@geldenhuys.co.uk wrote: On 2014-12-19 21:58, silvioprog wrote: What is the most recomended tool to make documentation?: I simply use my favourite text editor (EditPad Pro) and code templates. I don't use indentation in the XML

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread silvioprog
On Sat, Dec 20, 2014 at 9:18 AM, Graeme Geldenhuys mailingli...@geldenhuys.co.uk wrote: On 2014-12-20 11:29, Mattias Gaertner wrote: What does it not allow exactly? The built-in editor does very weird indentation, and there is no option to switch indentation off completely. Here is a quick

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread silvioprog
On Sat, Dec 20, 2014 at 3:25 PM, leledumbo leledumbo_c...@yahoo.co.id wrote: I'm writting a new component and I want to use a doc creator tool available in own Lazarus My recommendation: fpdoceditor.png http://free-pascal-lazarus.989080.n3.nabble.com/file/n4039867/fpdoceditor.png I

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread Graeme Geldenhuys
On 2014-12-20 22:06, silvioprog wrote: The documentation generated by the FPDoc is not responsive (e.g: http://goo.gl/bCJoPM), i.e., it does not open well on a mobile device. That's down to your choice of CSS style sheets - not a fault of FPDoc. Simply specify a different stylesheet and the

Re: [Lazarus] FPDoc Editor vs Lazarus Documentation Tool

2014-12-20 Thread silvioprog
On Sat, Dec 20, 2014 at 7:21 PM, Graeme Geldenhuys mailingli...@geldenhuys.co.uk wrote: On 2014-12-20 22:06, silvioprog wrote: The documentation generated by the FPDoc is not responsive (e.g: http://goo.gl/bCJoPM), i.e., it does not open well on a mobile device. That's down to your choice