In our previous episode, Michael Van Canneyt said:
> > I meant one project-file-that-$includes-base-filesetup, so that you can have
> > one project per backend without duplicating the main file related settings.
> >
> > Or can you have multiple backend options for different backends per project
> >
On Tue, 30 Apr 2013, Graeme Geldenhuys wrote:
On 2013-04-30 08:07, Michael Van Canneyt wrote:
Well, I would be to blame for this.
:-)
But when I do domething like that, then only the backend options would be
allowed
to differ. I see no need to put all options in backend-specific option
On Tue, 30 Apr 2013, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
I think that is better. Nearly all options have some special params (like
--auto-toc --auto-index --make-searchable etc)
These are already supported.
Everything not recognized as 'global' is a
In our previous episode, Michael Van Canneyt said:
> > I think that is better. Nearly all options have some special params (like
> > --auto-toc --auto-index --make-searchable etc)
>
> These are already supported.
>
> Everything not recognized as 'global' is added to backendoptions, a
> stringlis
On 2013-04-30 08:07, Michael Van Canneyt wrote:
> Well, I would be to blame for this.
:-)
> But when I do domething like that, then only the backend options would be
> allowed
> to differ. I see no need to put all options in backend-specific option sets:
> the input files etc. should not diffe
On Tue, 30 Apr 2013, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
A simpler solution could also be the support for an include of a separate file.
Then you could put common things (list of files) in one file, and create
top-level files per format you want to pro
In our previous episode, Michael Van Canneyt said:
> A simpler solution could also be the support for an include of a separate
> file.
> Then you could put common things (list of files) in one file, and create
> top-level files per format you want to produce.
I think that is better. Nearly all
On Mon, 29 Apr 2013, Graeme Geldenhuys wrote:
Hi,
I'm using a fpdoc project file for fpGUI documentation. The project file
idea works much better than a massive set of command line parameters. So
kudos to whoever thought of the project file idea.
Well, I would be to blame for this.
I jus
Hi,
I'm using a fpdoc project file for fpGUI documentation. The project file
idea works much better than a massive set of command line parameters. So
kudos to whoever thought of the project file idea.
I just have one question though Can the project file manage two or
more output formats? It i
