headers
Tim Williams | 1 Jul 2006 02:25
Picon

Re: svn commit: r418419 - in /forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery: resources.xmap src/java/org/apache/forrest/reading/PersistentImageReader.java

On 6/30/06, rgardler <at> apache.org <rgardler <at> apache.org> wrote:
> Author: rgardler
> Date: Fri Jun 30 16:30:50 2006
> New Revision: 418419
>
> URL: http://svn.apache.org/viewvc?rev=418419&view=rev
> Log:
> add a paramter to define the location to store the persistent files, this makes the plugin work on windoes
which was failing without it (also remove an unused method.)

Thanks for the cleanup Ross, my mess is horribly embarrassing.  As
many do, I had plans of coming back to do some cleaning... Sorry...
--tim
Permalink | Reply | 1 comment |
headers
Ross Gardler | 1 Jul 2006 02:32
Picon
Favicon
Gravatar

Re: svn commit: r418419 - in /forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery: resources.xmap src/java/org/apache/forrest/reading/PersistentImageReader.java

Tim Williams wrote:
> On 6/30/06, rgardler <at> apache.org <rgardler <at> apache.org> wrote:
> 
>> Author: rgardler
>> Date: Fri Jun 30 16:30:50 2006
>> New Revision: 418419
>>
>> URL: http://svn.apache.org/viewvc?rev=418419&view=rev
>> Log:
>> add a paramter to define the location to store the persistent files, 
>> this makes the plugin work on windoes which was failing without it 
>> (also remove an unused method.)
> 
> 
> Thanks for the cleanup Ross, my mess is horribly embarrassing.  As
> many do, I had plans of coming back to do some cleaning... Sorry...

That's the way of open source - lets have none of those apology things 
around here - otherwise I'll have to apologise for the great many 
partially complete plugins in whiteboard, I'd rather keep kidding myself 
someone might find them useful ;-)

Ross
Permalink | Reply | 0 comments |
headers
Gump | 1 Jul 2006 10:49
Picon
Favicon

[GUMP <at> vmgump]: Project forrest (in module forrest) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project forrest has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 158 runs.
The current state of this project is 'Failed', with reason 'Configuration Failed'.
For reference only, the following projects are affected by this:
    - forrest :  Apache Forrest is an XML standards-oriented documentation fr...

Full details are available at:
    http://vmgump.apache.org/gump/public/forrest/forrest/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: cocoon unknown to *this* workspace
 -INFO- Failed to extract fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/forrest/forrest/rss.xml
- Atom: http://vmgump.apache.org/gump/public/forrest/forrest/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 27000001072006, vmgump.apache.org:vmgump-public:27000001072006
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gump | 1 Jul 2006 11:13
Picon
Favicon

[GUMP <at> vmgump]: Project forrest-test (in module forrest) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project forrest-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 158 runs.
The current state of this project is 'Failed', with reason 'Configuration Failed'.
For reference only, the following projects are affected by this:
    - forrest-test :  Apache Forrest is an XML standards-oriented documentation fr...

Full details are available at:
    http://vmgump.apache.org/gump/public/forrest/forrest-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: jing unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-asciiart unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-batik unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-chaperon unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-fop unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-html unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-linkrewriter unknown to *this* workspace

To subscribe to this information via syndicated feeds:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gump | 2 Jul 2006 10:49
Picon
Favicon

[GUMP <at> vmgump]: Project forrest (in module forrest) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project forrest has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 161 runs.
The current state of this project is 'Failed', with reason 'Configuration Failed'.
For reference only, the following projects are affected by this:
    - forrest :  Apache Forrest is an XML standards-oriented documentation fr...

Full details are available at:
    http://vmgump.apache.org/gump/public/forrest/forrest/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: cocoon unknown to *this* workspace
 -INFO- Failed to extract fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/forrest/forrest/rss.xml
- Atom: http://vmgump.apache.org/gump/public/forrest/forrest/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 29000002072006, vmgump.apache.org:vmgump-public:29000002072006
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gump | 2 Jul 2006 11:13
Picon
Favicon

[GUMP <at> vmgump]: Project forrest-test (in module forrest) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project forrest-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 161 runs.
The current state of this project is 'Failed', with reason 'Configuration Failed'.
For reference only, the following projects are affected by this:
    - forrest-test :  Apache Forrest is an XML standards-oriented documentation fr...

Full details are available at:
    http://vmgump.apache.org/gump/public/forrest/forrest-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: jing unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-asciiart unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-batik unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-chaperon unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-fop unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-html unknown to *this* workspace
 -ERROR- Bad Dependency. Project: cocoon-block-linkrewriter unknown to *this* workspace

To subscribe to this information via syndicated feeds:
(Continue reading)

Permalink | Reply | 0 comments |
headers
jira | 2 Jul 2006 13:32
Picon
Favicon

[jira] Subscription: FOR-open-with-patch

Issue Subscription
Filter: FOR-open-with-patch (7 issues)
Subscriber: rgardler

Key         Summary
FOR-811     shine and polish the pelt theme so that it closely resembles the pelt skin
            http://issues.apache.org/jira/browse/FOR-811
FOR-795     Navigation bars for easy access in long documents
            http://issues.apache.org/jira/browse/FOR-795
FOR-652     CSS Style Sheets need cleanup, optimization and better naming of elements
            http://issues.apache.org/jira/browse/FOR-652
FOR-635     images not reproduced in PDFs, if sources are in xdocs/images directory
            http://issues.apache.org/jira/browse/FOR-635
FOR-412     use CSS for displaying list of Changes
            http://issues.apache.org/jira/browse/FOR-412
FOR-311     OOo Headings bug causes Forrest to fail
            http://issues.apache.org/jira/browse/FOR-311
FOR-280     gather index terms from documents to create index page with links
            http://issues.apache.org/jira/browse/FOR-280
Permalink | Reply | 0 comments |
headers
Thorsten Scherler | 2 Jul 2006 20:47
Picon
Favicon
Gravatar

Re: Moving FO generation to an internal plugin

El vie, 30-06-2006 a las 13:12 +0100, Ross Gardler escribió:
> Currently our PDF generation is split between skins and the PDF output 
> plugin. The reason for this is because the PDF plugin uses the FO 
> generated by the skin. But why? The skin is really about HTML generation 
> not FO.

right

> 
> I propose moving the FO generation out of skins and into an internal 
> plugin. This will have the benefit that we can work on the FO generation 
> independently of skins and therefore move it to a design more suitable 
> for reuse within the Dispatcher.
> 

right

> An alternative would be to move the FO generation into the PDF plugin, 
> but this doe not make sense since FO can be used to generate other print 
> based formats as well (RTF for example). I feel FO should be an 
> alternative internal format to XDocs for generation of print based 
> formats at the output stage.

> Since I have an semi-immediate need to extend FO generation so that 
> multiple page definitions are possible. It makes more sense to me to do 
> this extension within a whiteboard plugin rather than in the skins.
> 

cool. Yeah, go for it.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thorsten Scherler | 2 Jul 2006 20:35
Picon
Favicon
Gravatar

Re: WM2006 - New internal format for the dispatcher

El vie, 30-06-2006 a las 08:06 -0400, Tim Williams escribió:
> On 6/28/06, Thorsten Scherler <thorsten <at> apache.org> wrote:
...
> So these "internal" formats act essentially like input plugins except
> the output isn't necessarily an xdoc?  

Not all of them. 
For the *.internal, yes internal plugins produce xdocs so should the
internal contracts. 

...on the other hand we have other internal contracts in skins which do
not produce xdocs. book-to-menu.xsl and tab-to-menu.xsl this produces
internal markup used for generating the navigation contracts.

> Either way, I don't see how
> modularizing content could be a bad thing, go for it.
> 

:)

> I think that it doesn't "feel right" might be because you're naming
> them generic "internal1", "internal2", etc.  Other view/ <at> types are
> format-specific (e.g. html), right?  Why not stick with something like
> that?
> 

Actual internal is treated as "format". You can reach it via requesting
*.internal instead of *.html.

Picking up the *-to-menu.xsl they should go into internal-navigation and
(Continue reading)

Permalink | Reply | 1 comment |
headers
Thorsten Scherler | 2 Jul 2006 21:09
Picon
Favicon
Gravatar

Re: WM2006 - New internal format for the dispatcher

El vie, 30-06-2006 a las 13:45 +0100, Ross Gardler escribió:
> Tim Williams wrote:
> > So these "internal" formats act essentially like input plugins except
> > the output isn't necessarily an xdoc?  Either way, I don't see how
> > modularizing content could be a bad thing, go for it.
> 
> I did not respond to Thorsten post because, to put it simply, I did not 
> understand it. I read it to mean the same as Tim outlines above, but 
> figured this can't be the case since Thorsten had argued against 
> different internal formats in the past, since it goes against the grain 
> of what Forrest is intended to do.
> 

The thing is that we have internal code (as outlined in the other mail)
that is not xdocs but used in e.g. skins and the dispatcher. 

> (interesting that this has overlapped with my proposal of using FO as an 
> alternative internal format, maybe the reasoning is similar, I just 
> don't see it yet.)
> 

Actually one can extend the dispatcher for FO and one can create FO
contracts in an internal plugin. That has the benefit that one can
easily change the FO output for a page with a structurer. PDF and RTF
may need slightly different FO contracts to work optimal, they can
provide them through their implementation of the FO contract.

...and yes interesting that this has overlapped with your proposal.

> So, is Tims interpretation correct, if so, why do we now need to support
(Continue reading)

Permalink | Reply | 0 comments |

Gmane