Would it be possible to create some type of config file, which sets the required values and possibly defines some functions (as with the layout)? Now it might seem to be appropriate to do some exceptions, but then if you try to integrate PHP-GTK or Smarty docs parsing, it will get difficult to patch around.
That's what I did for the first patch (a new directory with mkindex.php and mktoc.php tuned for each build type)..
As we didn't deal with gtk and smarty docs yet, I'd like to see the second patch commited. The config file can be created later (if we really find that we need it)
But duplicating mkindex.php is a damn bad idea, since there are so simple differences. A bit of abstraction in the build system might help in this case.
So, something like the second patch is okay.
If PEAR support is needed now, then commit this, and we will see something later to abstract it out.
it's not needed for a particular date :) I'm just trying to make thing happen
> I still think that if we can
convince you, it would be better to abstract some stuff out now, and leave some controllers for each project, which define what default functions, and what project specific functions need to run and in what order.
well, no need to convince me :) (/me hides his gun)
I tried to play with gtkdoc too to see how things should be abstracted, but a simple ./configure doesn't work for me (I contacted steph about this)
FYI, here's what peardoc/livedocs gives for now (patched with the second version):
http://didou.keliglia.com/php/livedocs-pear/?l=en&q=manual
As you see, the current parser is not good enough for PEAR (see "Tal" as title :/)
I'll try to see how to fix this.
didou
