On 2 December 2011 03:17, Hans-Peter Diettrich wrote:
> exist. It doesn't look good when the docs do not include the most basic
> types, like Boolean, Byte, Char, Pointer etc. :-(
Those are all basic built-in types. Built into the compiler, not
defined in the RTL (as far as I know), but rather the
Hi,
I was playing around this morning with my console app that can
generate a script/batch file to generate documentation for fpGUI.
The content of the script file is every verbose because of the large
set of search path options inside each --input="..." parameter.
I'm not sure how the Makefiles
FPDoc issues many warnings about unknown link targets. Some of these
seem to result from intrinsic types, e.g. for PSmallInt the target
SmallInt does not exist. It doesn't look good when the docs do not
include the most basic types, like Boolean, Byte, Char, Pointer etc. :-(
The same problem w
michael.vancann...@wisa.be schrieb:
Perhaps linux/sockets.pp should be replaced by win/sockets.pp?
Or should the Makefile supply the Linux/Unix include directories,
instead those of the current platform (Windows)?
The latter. The paths must be appended, but I already committed a fix for
thi
On 12/01/2011 04:16 PM, Graeme Geldenhuys wrote:
Yes, I was thinking in that same direction.
My son some time ago wrote a HTML parser / Writer that creates a linked
List of objects (similar to the XML parser) .
Maybe this could be helpful.
-Michael
On 1 December 2011 15:37, Marco van de Voort wrote:
> In our previous episode, Graeme Geldenhuys said:
>> My main problem at the moment is again the Latex format.
>
> Manipulate the generated HTML?
Yes, I was thinking in that same direction.
>> maybe a better idea is to improve the LaTex-to-PDF
In our previous episode, Graeme Geldenhuys said:
> My main problem at the moment is again the Latex format.
Manipulate the generated HTML?
> It is very hard to convert LaTex to any other format (and still look
> good). This was the main reason I wanted to implement ePub support. But
> maybe a b
On 1 December 2011 13:45, Michael Schnell wrote:
>
> Never heard of same. Is this supposed to replace *.inf ?
No, ePub is a specialised HTML/XHTML archive format. A single file
used for electronic books. It is most often used on tablet pc's, smart
phones and e-Book readers like Amazon Kindle.
On Thu, 1 Dec 2011, Hans-Peter Diettrich wrote:
See Mantis #20786 for details.
The first problem was the use of single quotes in the generated fpdoc
commandline, which are not handled properly by the Windows shell. I fixed
this manually, by editing the Makefile.
Next I get the following e
On Thu, 1 Dec 2011, Marco van de Voort wrote:
In our previous episode, Hans-Peter Diettrich said:
commandline, which are not handled properly by the Windows shell. I
fixed this manually, by editing the Makefile.
Next I get the following error messages:
Afaik the docs are hardwired for Linu
In our previous episode, Hans-Peter Diettrich said:
> commandline, which are not handled properly by the Windows shell. I
> fixed this manually, by editing the Makefile.
>
> Next I get the following error messages:
Afaik the docs are hardwired for Linux. Even if you are on host windows, you
shou
On 11/30/2011 01:18 PM, Graeme Geldenhuys wrote:
I'm also working on a new ePub output format - specialized for tablet
usage.
Never heard of same. Is this supposed to replace *.inf ?
-Michael
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
Felipe Monteiro de Carvalho schrieb:
On Wed, Nov 30, 2011 at 9:14 PM, Hans-Peter Diettrich
wrote:
Now you hear some, most probably from the first user of fpdoc on Windows ;-)
If you were, then this file would not exist:
Examples which *happen* to work are not a proof for the absence of bugs
On 11/30/2011 12:33 AM, Hans-Peter Diettrich wrote:
Should we introduce a single (HTML) documentation directory, on every
target machine, where *all* package documentations can reside
side-by-side, with fixed relative references? Or should HTML
documentation be deprecated, in favor of more po
See Mantis #20786 for details.
The first problem was the use of single quotes in the generated fpdoc
commandline, which are not handled properly by the Windows shell. I
fixed this manually, by editing the Makefile.
Next I get the following error messages:
../rtl/unix/sockets.pp(20,15): Could
This is what I would worry about as well, if I used free pascal or lazarus.
Having a strict delphi mode, would bring free pascal one step closer, to
using it instead of Delphi.
There are other issues which would then remain though like:
Lazarus Forms
Lazarus Packages ?
And perhaps slightly l
On Wed, Nov 30, 2011 at 9:14 PM, Hans-Peter Diettrich
wrote:
> Now you hear some, most probably from the first user of fpdoc on Windows ;-)
If you were, then this file would not exist:
http://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/docs/html/build_html.bat?root=lazarus&view=log
I have built
On Thu, 1 Dec 2011, Graeme Geldenhuys wrote:
On 30 November 2011 22:14, Hans-Peter Diettrich wrote:
Now you hear some, most probably from the first user of fpdoc on Windows ;-)
I use fpdoc under Windows without problems. Though mostly for
generating documentation for my own projects, not F
On 30 November 2011 22:14, Hans-Peter Diettrich wrote:
> Now you hear some, most probably from the first user of fpdoc on Windows ;-)
I use fpdoc under Windows without problems. Though mostly for
generating documentation for my own projects, not FPC ones. I also use
a console utility program with
On Wed, 30 Nov 2011, Hans-Peter Diettrich wrote:
michael.vancann...@wisa.be schrieb:
You should understand the problems of Windows users. Until now they cannot
produce local documentation, due to several bugs in the Makefiles, fpdoc
and related tools. This is a bad situation for documentati
20 matches
Mail list logo
