You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2004/12/08 13:54:29 UTC

[JIRA] Created: (FOR-409) PDF: should be able to change font size and style in skinconf.xml

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-409

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-409
    Summary: PDF: should be able to change font size and style in skinconf.xml
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Core operations
   Versions:
             0.6

   Assignee: 
   Reporter: Olivier Jacques

    Created: Wed, 8 Dec 2004 6:53 AM
    Updated: Wed, 8 Dec 2004 6:53 AM
Environment: Windows XP SP2

Description:
In skinconf.xml, we should be able to change font size and style for the PDF output.
As there are several font sizes in a PDF output, this should be a "relative", not an "absolute" font size.
Something like:
  <!-- Settings specific to PDF output. -->
  <pdf>
    <fonts>
      <size>small</size>
      <family>sans-serif</family>
    </fonts>
  </pdf>

Size can be: tiny, small, normal, large, xlarge
Family can be: serif, sans-serif, cursive, fantasy, or monospace



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml

Posted by is...@cocoondev.org.
The following comment has been added to this issue:

     Author: Johannes Schaefer
    Created: Wed, 8 Dec 2004 7:08 AM
       Body:
I suggested an enhanced <pdf> section as well, 
see
  http://issues.cocoondev.org/browse/FOR-275

Maybe it would be good to have pdfconf.xml
and consequently htmlconf.xml? 
The "skin" concept seems to go away anyway ...
BTW: How are output-plugins configured?
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-409?page=comments#action_11930

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-409

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-409
    Summary: PDF: should be able to change font size and style in skinconf.xml
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Core operations
   Versions:
             0.6

   Assignee: 
   Reporter: Olivier Jacques

    Created: Wed, 8 Dec 2004 6:53 AM
    Updated: Wed, 8 Dec 2004 7:08 AM
Environment: Windows XP SP2

Description:
In skinconf.xml, we should be able to change font size and style for the PDF output.
As there are several font sizes in a PDF output, this should be a "relative", not an "absolute" font size.
Something like:
  <!-- Settings specific to PDF output. -->
  <pdf>
    <fonts>
      <size>small</size>
      <family>sans-serif</family>
    </fonts>
  </pdf>

Size can be: tiny, small, normal, large, xlarge
Family can be: serif, sans-serif, cursive, fantasy, or monospace



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[JIRA] Updated: (FOR-409) PDF: should be able to change font size and style in skinconf.xml

Posted by is...@cocoondev.org.
The following issue has been updated:

    Updater: Dave Brondsema (mailto:brondsem@apache.org)
       Date: Wed, 9 Mar 2005 6:20 PM
    Changes:
             Component changed to Plugin: pdf-output
             Component changed from Core operations
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org//browse/FOR-409?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-409

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-409
    Summary: PDF: should be able to change font size and style in skinconf.xml
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Plugin: pdf-output
   Versions:
             0.6

   Assignee: 
   Reporter: Olivier Jacques

    Created: Wed, 8 Dec 2004 6:53 AM
    Updated: Wed, 9 Mar 2005 6:20 PM
Environment: Windows XP SP2

Description:
In skinconf.xml, we should be able to change font size and style for the PDF output.
As there are several font sizes in a PDF output, this should be a "relative", not an "absolute" font size.
Something like:
  <!-- Settings specific to PDF output. -->
  <pdf>
    <fonts>
      <size>small</size>
      <family>sans-serif</family>
    </fonts>
  </pdf>

Size can be: tiny, small, normal, large, xlarge
Family can be: serif, sans-serif, cursive, fantasy, or monospace



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Re: Configuring output plugins (was Re: [JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml)

Posted by Ross Gardler <rg...@apache.org>.
scott hutinger wrote:
> Ross Gardler wrote:
> 
>> scott hutinger wrote:
>>
>>> Ross Gardler wrote:
>>>
>>>> issues@cocoondev.org wrote:
>>>>
>>>> From FOR-409
>>>>
>>
>> ...
>>
>>>> OK, so how do we configure output-plugins? Here is a suggestion to 
>>>> get us started:
>>>
>>>
>>
>> ...
>>
>>> I think possibly another pdf plugin would need to be required when 
>>> doing things like a 1 to 1 file mapping with changes going on per 
>>> file.  I think a standard plugin for pdf output, and then someone may 
>>> need to create another pdf output to do more specialized things.
>>
>>
>>
>> Sorry, I'm not following you. Are you suggesting that we create a 
>> different plugin for every use case? Surely, a single configurable 
>> plugin that covers the majority of use-cases would be more sensible.
>>
>> Sure, there may be advanced use cases requiring editing of stylesheets 
>> and the like, but that it poweruser stuff. For the maojoority of users 
>> a configurable plugin would be just fine.
>>
> No, it's just that some PDF's might need to be handled differently than 
> the standard pdf.  I was thinking in terms of having a documentation 
> build in with the website build.  Two (somewhat) different items.  Would 
> the current pdf plugin allow some other process to be used in specific 
> instances?

Ahhh, that is why I was confused. This thread is about where to put the 
configuration information for a plugin. Not about whether one plugin can 
be a catch-all for all use cases. However...

> For instance if a  file  'doc1' that has a stylesheet 
> associated with it, shouldn't the plugin use that stylesheet instead of 
> the standard settings?  I'm a bit uncertain as to what method would be 
> best.  I agree that normally 1 setting for the pdf generation would be 
> the norm.  But in instances where it wouldn't be the norm, shouldn't it 
> be easy for the user to have a file associated with what the pdf output 
> would be for specific documents?

This kind of setup was discussed in a separate thread and a solution has 
been proposed (but not implemented). Search the archives for selective 
PDF for background.

Basically, the idea is that we can say this file should have PDF 
generated, that file shouldn't. This could be used in your use case (in 
conjunstion with Thorsten previous comments in this thread).

>>> Or possibly settings for specific files(user supplied- or a list of), 
>>> and a default setting.  Possibly choose you pdf output such as skin 
>>> for the default output.
>>
>>
>>
>> I'm totally lost here I'm afraid, could you explain some more.
>>
> I think the automatic over-ride of the standard plugin with 'this 
> document has a stylesheet associated with it' would make everything work 
> without needing another pdf-stylesheet plug in.  Although I may be 
> wrong.  Should it be associated with another plugin?  I'm uncertain.

Yes, this has some parallels with Thorstens interpretation of what you 
wrote and I think his comments illustrate how to achieve what you are 
suggesting.

>  Or 
> is this way out of line?

Nothing is out of line, a little off topic maybe, but not out of line ;-)

Ross

Re: Configuring output plugins (was Re: [JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml)

Posted by scott hutinger <s-...@wiu.edu>.
Ross Gardler wrote:

> scott hutinger wrote:
>
>> Ross Gardler wrote:
>>
>>> issues@cocoondev.org wrote:
>>>
>>> From FOR-409
>>>
>
> ...
>
>>> OK, so how do we configure output-plugins? Here is a suggestion to 
>>> get us started:
>>
>
> ...
>
>> I think possibly another pdf plugin would need to be required when 
>> doing things like a 1 to 1 file mapping with changes going on per 
>> file.  I think a standard plugin for pdf output, and then someone may 
>> need to create another pdf output to do more specialized things.
>
>
> Sorry, I'm not following you. Are you suggesting that we create a 
> different plugin for every use case? Surely, a single configurable 
> plugin that covers the majority of use-cases would be more sensible.
>
> Sure, there may be advanced use cases requiring editing of stylesheets 
> and the like, but that it poweruser stuff. For the maojoority of users 
> a configurable plugin would be just fine.
>
No, it's just that some PDF's might need to be handled differently than 
the standard pdf.  I was thinking in terms of having a documentation 
build in with the website build.  Two (somewhat) different items.  Would 
the current pdf plugin allow some other process to be used in specific 
instances?   For instance if a  file  'doc1' that has a stylesheet 
associated with it, shouldn't the plugin use that stylesheet instead of 
the standard settings?  I'm a bit uncertain as to what method would be 
best.  I agree that normally 1 setting for the pdf generation would be 
the norm.  But in instances where it wouldn't be the norm, shouldn't it 
be easy for the user to have a file associated with what the pdf output 
would be for specific documents?

>> Or possibly settings for specific files(user supplied- or a list of), 
>> and a default setting.  Possibly choose you pdf output such as skin 
>> for the default output.
>
>
> I'm totally lost here I'm afraid, could you explain some more.
>
I think the automatic over-ride of the standard plugin with 'this 
document has a stylesheet associated with it' would make everything work 
without needing another pdf-stylesheet plug in.  Although I may be 
wrong.  Should it be associated with another plugin?  I'm uncertain.  Or 
is this way out of line?

scott

> Ross
>

Re: Configuring output plugins (was Re: [JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml)

Posted by Thorsten Scherler <th...@apache.org>.
El mié, 08-12-2004 a las 23:42, Ross Gardler escribió:
> scott hutinger wrote:
> > Ross Gardler wrote:
> > 
> >> issues@cocoondev.org wrote:
> >>
> >> From FOR-409
> >>
> 
> ...
> 
> >> OK, so how do we configure output-plugins? Here is a suggestion to get 
> >> us started:
> 
> ...
> 
> > I think possibly another pdf plugin would need to be required when doing 
> > things like a 1 to 1 file mapping with changes going on per file.  I 
> > think a standard plugin for pdf output, and then someone may need to 
> > create another pdf output to do more specialized things.
> 
> Sorry, I'm not following you. Are you suggesting that we create a 
> different plugin for every use case? Surely, a single configurable 
> plugin that covers the majority of use-cases would be more sensible.
> 
> Sure, there may be advanced use cases requiring editing of stylesheets 
> and the like, but that it poweruser stuff. For the maojoority of users a 
> configurable plugin would be just fine.

:)

I am not sure but I reckon that would be actually a use case for
forrest:templates. One could implemend this power user functionality as
new fbits for the pdf. That way we will have *one* pdf plugin that can
be extended on a use case basis.

NOTE: The forrest:templates are still in the conceptual phase because I
still did not found time to implemend a prototyp. I hope I will have a
working example on the end of this year in 0.7-dev.

> 
> > Or possibly 
> > settings for specific files(user supplied- or a list of), and a default 
> > setting.  Possibly choose you pdf output such as skin for the default 
> > output.
> 
> I'm totally lost here I'm afraid, could you explain some more.
> 

I think I know what Scott is trying to say. Expressed in code (with
forrest:templates in the back of my head) I would guess it is something
like this:

forrest:templates:
<forrest:view output-format="fo" name="customPdf">
  <forrest:hook name="intro">
   <forrest:nugget name="grouplogo"/>
   <forrest:call-template name="customFunctions"/>
  </forrest:hook>
</forrest:view>

site.xml:
<site label="MyProj" href=""
xmlns="http://apache.org/forrest/linkmap/1.0" tab="">

  <about label="About">
    <index label="Index" href="index.html" description="Welcome to
MyProj" view="customPdf"/>
  </about>
</site>

Then the power user can write his/her own <forrest:template/> where
(s)he implemends new functionalities for e.g. PDF.

HTH
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)

Re: Configuring output plugins (was Re: [JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml)

Posted by Ross Gardler <rg...@apache.org>.
scott hutinger wrote:
> Ross Gardler wrote:
> 
>> issues@cocoondev.org wrote:
>>
>> From FOR-409
>>

...

>> OK, so how do we configure output-plugins? Here is a suggestion to get 
>> us started:

...

> I think possibly another pdf plugin would need to be required when doing 
> things like a 1 to 1 file mapping with changes going on per file.  I 
> think a standard plugin for pdf output, and then someone may need to 
> create another pdf output to do more specialized things.

Sorry, I'm not following you. Are you suggesting that we create a 
different plugin for every use case? Surely, a single configurable 
plugin that covers the majority of use-cases would be more sensible.

Sure, there may be advanced use cases requiring editing of stylesheets 
and the like, but that it poweruser stuff. For the maojoority of users a 
configurable plugin would be just fine.

> Or possibly 
> settings for specific files(user supplied- or a list of), and a default 
> setting.  Possibly choose you pdf output such as skin for the default 
> output.

I'm totally lost here I'm afraid, could you explain some more.

Ross

Re: Configuring output plugins (was Re: [JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml)

Posted by scott hutinger <s-...@wiu.edu>.
Ross Gardler wrote:

> issues@cocoondev.org wrote:
>
> From FOR-409
>
>> The following comment has been added to this issue:
>>
>>      Author: Ross Gardler
>>     Created: Wed, 8 Dec 2004 7:33 AM
>>        Body:
>> The configuration of output-plugins has not yet been finalised as 
>> there is
>
> > still experimentation with the replacement for skins.
>
>>
>> Right now the configuration remains in skinconf.xml, which is *not* the 
>
> > right place since that will mean skinconf.xml will have entries for
> > plugins that are not relevent.
>
>>
>> Perhaps we should have an interim solution. I'll start a thread in 
>> the lists
>
> > and link it back here once it appears in the archives.
>
> OK, so how do we configure output-plugins? Here is a suggestion to get 
> us started:
>
> Each plugin provides a default pluginconf.xml which contains things 
> like font size, page size, page-orientation (in the PDF plugin).
>
> <pluginconf>
>   <org.apache.forrest.plugin.pdf-output>
>     <font>
>       <size>small</size>
>       <family>serif</family>
>     </font>
>     <page-orientation>portrait</page-orientation>
>     ...
>   </org.apache.forrest.plugin.pdf-output>
> </pluginconf>
>
> The values in this file can be overridden by a pluginconf.xml file in 
> the project.home. For example:
>
> <pluginconf>
>   <org.apache.forrest.plugin.pdf-output>
>     <font>
>       <size>small</size>
>       <family>serif</family>
>     </font>
>     <page-orientation>portrait</page-orientation>
>     ...
>   </org.apache.forrest.plugin.pdf-output>
>
>   <org.apache.forrest.plugin.text-output>
>     <tab-width>4</tab-width>
>   </org.apache.forrest.plugin.text-output>
> </pluginconf>
>
> It will not be possible to put all the skinconf.xml stuff in this file 
> as the skin will not know to look for it. For example, we could not 
> use this file to turn on/off the PDF link in HTML pages, we'll have to 
> wait for Fbits for this.
>
> Ross
>
I think possibly another pdf plugin would need to be required when doing 
things like a 1 to 1 file mapping with changes going on per file.  I 
think a standard plugin for pdf output, and then someone may need to 
create another pdf output to do more specialized things.  Or possibly 
settings for specific files(user supplied- or a list of), and a default 
setting.  Possibly choose you pdf output such as skin for the default 
output.

scott

scott

Configuring output plugins (was Re: [JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml)

Posted by Ross Gardler <rg...@apache.org>.
issues@cocoondev.org wrote:

 From FOR-409

> The following comment has been added to this issue:
> 
>      Author: Ross Gardler
>     Created: Wed, 8 Dec 2004 7:33 AM
>        Body:
> The configuration of output-plugins has not yet been finalised as there is
 > still experimentation with the replacement for skins.
> 
> Right now the configuration remains in skinconf.xml, which is *not* the 
 > right place since that will mean skinconf.xml will have entries for
 > plugins that are not relevent.
> 
> Perhaps we should have an interim solution. I'll start a thread in the lists
 > and link it back here once it appears in the archives.

OK, so how do we configure output-plugins? Here is a suggestion to get 
us started:

Each plugin provides a default pluginconf.xml which contains things like 
font size, page size, page-orientation (in the PDF plugin).

<pluginconf>
   <org.apache.forrest.plugin.pdf-output>
     <font>
       <size>small</size>
       <family>serif</family>
     </font>
     <page-orientation>portrait</page-orientation>
     ...
   </org.apache.forrest.plugin.pdf-output>
</pluginconf>

The values in this file can be overridden by a pluginconf.xml file in 
the project.home. For example:

<pluginconf>
   <org.apache.forrest.plugin.pdf-output>
     <font>
       <size>small</size>
       <family>serif</family>
     </font>
     <page-orientation>portrait</page-orientation>
     ...
   </org.apache.forrest.plugin.pdf-output>

   <org.apache.forrest.plugin.text-output>
     <tab-width>4</tab-width>
   </org.apache.forrest.plugin.text-output>
</pluginconf>

It will not be possible to put all the skinconf.xml stuff in this file 
as the skin will not know to look for it. For example, we could not use 
this file to turn on/off the PDF link in HTML pages, we'll have to wait 
for Fbits for this.

Ross

[JIRA] Commented: (FOR-409) PDF: should be able to change font size and style in skinconf.xml

Posted by is...@cocoondev.org.
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Wed, 8 Dec 2004 7:33 AM
       Body:
The configuration of output-plugins has not yet been finalised as there is still experimentation with the replacement for skins. 

Right now the configuration remains in skinconf.xml, which is *not* the right place since that will mean skinconf.xml will have entries for plugins that are not relevent.

Perhaps we should have an interim solution. I'll start a thread in the lists and link it back here once it appears in the archives.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-409?page=comments#action_11932

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-409

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-409
    Summary: PDF: should be able to change font size and style in skinconf.xml
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Core operations
   Versions:
             0.6

   Assignee: 
   Reporter: Olivier Jacques

    Created: Wed, 8 Dec 2004 6:53 AM
    Updated: Wed, 8 Dec 2004 7:33 AM
Environment: Windows XP SP2

Description:
In skinconf.xml, we should be able to change font size and style for the PDF output.
As there are several font sizes in a PDF output, this should be a "relative", not an "absolute" font size.
Something like:
  <!-- Settings specific to PDF output. -->
  <pdf>
    <fonts>
      <size>small</size>
      <family>sans-serif</family>
    </fonts>
  </pdf>

Size can be: tiny, small, normal, large, xlarge
Family can be: serif, sans-serif, cursive, fantasy, or monospace



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira