Hi,

Why is the --css-file option limited to the CHM output? Why can't I specify it for the HTML output too?

Alternatively, how do I tell fpdoc not to use the default (built-in) fpdoc.css, but rather use my version.

Regards,
- Graeme -

Graeme Geldenhuys wrote

Hi, Why is the --css-file option limited to the CHM output? Why can't I specify it for the HTML output too?

You can. It's an error in the usage message.

Michael.

Michael Van Canneyt wrote

You can. It's an error in the usage message.

Brilliant - I can confirm it works!

It is apparently an error/bug in the fpdoc documentation too.

http://www.freepascal.org/docs-html/fpdoc/fpdocsu6.html#x18-170003.2.6

Regards,
- Graeme -

I am open for different formatting for the documentation. It would be nice to have a set of 'themes'.

I'm still thinking about generating a set of 'framed' documentation pages.

Michael.

Michael Van Canneyt wrote

I am open for different formatting for the documentation. It would be nice to have a set of 'themes'.

Attached is what I worked on last night - still need a few tweaks (media support). It will be the new theme for fpGUI's class docs in the upcoming release. Formatting wise not much has changed, but it is a different theme none the less. The default fpdoc.css worked well for many years, but looks a bit dated these days.

I'm still thinking about generating a set of 'framed' documentation pages.

That should be good. I would like to tweak the existing HTML output too, adding a few more hooks to make it easier to customise with CSS. There was some things I wanted to implement in my theme but couldn't. That could also be contributed to my limited knowledge of CSS. ;-)

I have a few other fpdoc todo items too:
- Minor fixes for IPF output
- improved "declaration" section code output
- more flexible project file. eg: One file that supports multiple output formats. I will discuss this with you closer to the time. There was a few others too, but can't remember them now.

Regards,
- Graeme -