Comments on: Setting up a DocBook Toolchain for documenting PHP code The Right Way (TM) http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/ il mago di eZ Tue, 10 Nov 2009 10:48:35 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: gggeek http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/comment-page-1/#comment-11316 gggeek Sat, 12 Sep 2009 22:07:03 +0000 http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/#comment-11316 Sorry, I never tried this, but it sounds a good idea. You could probably use an xslt (or even plain php) script to inject the source code into the xml at the phase of producing the final output - not optimal because you loose visibility of the code while editing the docs though... Sorry, I never tried this, but it sounds a good idea.
You could probably use an xslt (or even plain php) script to inject the source code into the xml at the phase of producing the final output – not optimal because you loose visibility of the code while editing the docs though…

]]> By: Johan http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/comment-page-1/#comment-8860 Johan Wed, 15 Apr 2009 15:59:57 +0000 http://gggeek.altervista.org/2007/07/05/setting-up-a-docbook-toolchain-for-documenting-php-code-the-right-way-tm/#comment-8860 Thanks for the tips! I'm just doing the same myself since I want to find a new way to document a fairly large PHP library using XMLMind among other things. One thing I haven't yet found a good way to do is to include external small PHP examples (highlighted) in the source XML document (in programlistings tag) without copy the source text into the document. I have tried using tags (automatic generated) and then use &link; within the programlisting tag but for some reason it doesn't quite work. The reason is that I like to have the source fully separate from the manual to make sure it can be run as part of a test suit. Does anyone know the best way of doing this? /Johan Thanks for the tips! I’m just doing the same myself since I want to find a new way to document a fairly large PHP library using XMLMind among other things.

One thing I haven’t yet found a good way to do is to include external small PHP examples (highlighted) in the source XML document (in programlistings tag) without copy the source text into the document. I have tried using tags (automatic generated) and then use &link; within the programlisting tag but for some reason it doesn’t quite work.

The reason is that I like to have the source fully separate from the manual to make sure it can be run as part of a test suit.

Does anyone know the best way of doing this?

/Johan

]]>