forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: Selective PDF
Date Tue, 16 Nov 2004 19:47:47 GMT
Sean Wheller wrote:
> On Tuesday 16 November 2004 19:20, Ross Gardler wrote:
>>>plugin.pdf.button.include.output=**.html, documentation/index.html
>>>So if you have a pod plugin, then either the for the
>>>pod plugin will have this defined or the main
>>>plugin.pod.button.include.output=**.html, documentation/index.html
>>>and so on for each target format ?
>>Yes, or at least that is my thinking. We have to wait a short while to
>>make sure there are no objections from anyone. We may have missed
> Ok once I know which I will add for each target format.

If we include them in fresh-site/ then all new 
projects will automatically have these properties. However, they will 
only be relevant if they install the pdf plugin. Therefore, we don't 
want to add them to fresh-site.

Similarly we don't want to add them to (same 

They will only be added to a projects file if they 
are needed. This means we need to document them in the (to be built) 
pdf-output plugin.

We will use the pdf plugin as our test site, that is we will create a 
PDF plugin and test this configuration on the documentation for that 
plugin. In other words, it will go into plugins/pdf/

However, you can't do this as we don't have the PDF plugin. You could 
make a start on building the PDF plugin and provide a patch for that, 
I'm just in the middle of doing the wiki plugin at the moment.


for (incomplete instructions on how to do this).

You could start creating the basic documentation site for the plugin, 
and if you know how, you could extract the PDF functionality from 
Forrest. This will give enough time for others to comment on our 
intentions as we need to extract the PDF into a plugin anyway.

> I don't see an issue in JIRA for this so I can attach a patch (once I know 
> which file to modify :-) ), perhaps it's named something obscure?

No there is no issue that I am aware of, just create one and link to 
this thread.

>>The next stage is where do we process these properties.
> This is the part that has me stuck.
>>Lets continue to use PDF as a use case. Currently, site2xhtml.xsl has
>>the following:
>>     |Generates the PDF link
>>     +-->
>>   <xsl:template match="div[@id='skinconf-pdflink']">
>>     <xsl:if test="not($config/disable-pdf-link) or $disable-pdf-link =
>>       <div class="pdflink" title="Portable Document Format"><a
>>href="{$filename-noext}.pdf" class="dida">
>>         <img class="skin" src="{$skin-img-dir}/pdfdoc.gif" alt="PDF
>>-icon" /><br/>
>>         PDF</a>
>>       </div>
>>     </xsl:if>
>>   </xsl:template>
>>We need to maintain this default behaviour (although we may want to
>>deprecate it).
> For now we must keep it, or it won't work. Same with the full-docbook plugin I 
> have sitting with me, it won't work until XHTML. I guess we will come across 
> this problem more often as we move more things to plugins. Personal this is 
> why I would have liked XHTML implimented first and then everything else 
> developed. At least we would not have to go back and retouch all work.

[OT] We do not need XHTML as an intermediate format to use XHTML - we 
can return to that whenever you are ready.

>>In addition, we want to consider the values of the new 
>>properties in the above template. How does this look?
>>     |Generates the PDF link
>>     +-->
> <snip/> Some good logic
> It looks sensible, as best I can tell. Will need to test it, but to have test 
> env we need pdf plugin. So I think we:
> 1. do pdf plugin
> 2. add to (whichever it is)
> 3. add your logic to site2xhtml



View raw message