David Crossley | 1 Jun 04:39 2007
Picon

Re: rel to CVS-Version Error in sitemap-v06.rng, datatype library

fizoblon wrote:
> 
> Hi I'm Fiz from Northern Germany and new in the Forrest-Project.
> because I've got a contract for a large Documentation in OpenOffice an
> DocBook
> for a website. After days of searching and trying I decided to use Forrest.
> It seems to be the only Framework, that fits my new Job.
> I hope I'm welcome even I shouldn't try to write something in english ;-)
> and hope you don't mind it. 

Yes you are welcome and your English is fine.

> Just for trying if there are some new options in the current CVS-Version I
> downloaded it today,

I hope that you mean "SVN = Subversion" and not the old CVS.
We migrated to SVN long ago. The old CVS is still available
but of course it is not used.

> One more question: If I have trouble with the OpenOffice-Plugin later, may I
> nerv this list with my trouble or is there another mailing list or a forum
> for this?

Yes search and ask here.

-David

fizoblon | 2 Jun 14:04 2007
Picon

Plugin OpenOffice.Org> missing CSS classes P1..Pn


WinXP, OpenOffice 2.2  German, Plugin 0.8, CVS-Source 0.9

Hi,

after missing some formatting in the output like bold, italic,left, right
and more I looked 
into the source and found
..
<p class="P1">bold</p>
<p class="instruction">Italic</p>
<p class="P3">underline</p>
<p class="Text body">left</p>
<p class="P4">middle</p>
<p class="P5">right</p>
..
I didn't check all classes, but I can't find the P1 .. Pn in the four
css-files of the project
(basic.css, screen.css, profile.css, print.css in the skin-directory) and
the text isn't formatted
as suspected.

the build runs without any errors, but gives some warnings while copying:

Warning: C:\www\ecs\docroot\build\webapp\resources not found.
..
Warning: C:\www\ecs\docroot\src\documentation\skins\common\images not found.
Warning: C:\www\ecs\docroot\src\documentation\skins\pelt\images not found.
..
Warning: C:\www\ecs\docroot\src\documentation\skins\common not found.
(Continue reading)

Gavin (JIRA | 2 Jun 14:28 2007
Picon

[jira] Commented: (FOR-1001) Broken seed site: Loss of menu/tab context on Samples-tab


    [
https://issues.apache.org/jira/browse/FOR-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500944
] 

Gavin commented on FOR-1001:
----------------------------

Agree on the remaining Issue.

The generated code produces :-

<!--+
    |start Subtabs
    +-->
<div id="level2tabs">
<a class="selected" href="../samples/index.html">Index</a><a class="selected" href="../samples/static.html">Sample2</a>
</div>
<!--+
    |end Endtabs
    +-->

So no matter how you configure skinconf to separate colors between the subtabs, they will remain the same
because both are being configured as being 'selected' .

Where does this need changing ?

Then I suggest maybe changing some default colors.

> Broken seed site: Loss of menu/tab context on Samples-tab
(Continue reading)

Brian M Dube (JIRA | 3 Jun 08:36 2007
Picon

[jira] Commented: (FOR-1000) Use locationmap to resolve XSL imports in skins


    [
https://issues.apache.org/jira/browse/FOR-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500994
] 

Brian M Dube commented on FOR-1000:
-----------------------------------

Example:
<xsl:import href="lm://transform.common.html.site.xhtml"/>

Cocoon generates an error for unknown protocol "lm" when I test this.

> Use locationmap to resolve XSL imports in skins
> -----------------------------------------------
>
>                 Key: FOR-1000
>                 URL: https://issues.apache.org/jira/browse/FOR-1000
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Skins (general issues)
>    Affects Versions: 0.8
>            Reporter: Brian M Dube
>            Priority: Minor
>             Fix For: 0.9-dev
>
>
> To create a custom skin that imports stylesheets from common, for example by copying pelt and modifying it
for a project, it is also necessary to copy the common skin because the xsl:import calls use relative
paths. The imports can be done with the help of the locationmap.
(Continue reading)

jira | 3 Jun 21:30 2007
Picon

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

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

Key         Summary
FOR-998     [PATCH] Resolve empty cells.
            https://issues.apache.org/jira/browse/FOR-998
FOR-934     i18n language override menu
            https://issues.apache.org/jira/browse/FOR-934
FOR-905     Recent change in cygwin appears to prevent the classpath for loop in the forrest command from working
            https://issues.apache.org/jira/browse/FOR-905
FOR-795     Navigation bars for easy access in long documents
            https://issues.apache.org/jira/browse/FOR-795
FOR-752     Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory
            https://issues.apache.org/jira/browse/FOR-752
FOR-652     CSS Style Sheets need cleanup, optimization and better naming of elements
            https://issues.apache.org/jira/browse/FOR-652
FOR-635     images not reliably reproduced in PDFs
            https://issues.apache.org/jira/browse/FOR-635
FOR-412     use CSS for displaying list of Changes
            https://issues.apache.org/jira/browse/FOR-412
FOR-311     OOo Headings bug causes Forrest to fail
            https://issues.apache.org/jira/browse/FOR-311
FOR-280     gather index terms from documents to create index page with links
            https://issues.apache.org/jira/browse/FOR-280

fizoblon | 4 Jun 10:59 2007
Picon

Re: Plugin OpenOffice.Org> missing CSS classes P1..Pn (unsolved)


Hi, I tried it on a linux 9.3 with Forrest 0.8 too and the result is the
same,
untill the plugin is not building a css with the classes P1 upto Pxy the
most
of the formatings will not work. Has nobody any small idea?
--

-- 
View this message in context: http://www.nabble.com/Plugin-OpenOffice.Org%3E-missing-CSS-classes-P1..Pn-tf3856731.html#a10946019
Sent from the Apache Forrest - Dev mailing list archive at Nabble.com.

Vincent Siveton | 4 Jun 14:27 2007
Picon

Forrestdoc and Maven JXR

Hi,

The Maven Team want to start a discussion about Forrestdoc and JXR projects.

Background:
Forrestdoc [1]: Forrestdoc is a Javadoc/Source code/Documentation
management system.
JXR [2]: JXR is a source cross reference generator.

It sounds that these projects are very similar.

What is the status of Forrestdoc? Any release available? Could we join
our efforts?

Thanks,

Vincent

[1] http://people.apache.org/~nicolaken/whiteboard/forrestdoc/
[2] http://maven.apache.org/jxr/

---------- Forwarded message ----------
From: Brett Porter <brett <at> apache.org>
Date: 3 juin 2007 21:55
Subject: Re: Discuss about JXR issues
To: Maven Developers List <dev <at> maven.apache.org>

It looks like that hasn't been released, and so couldn't be used as a
dependency. And a separate plugin wouldn't be able to integrate it
into JXR, would it?
(Continue reading)

Gav.... | 4 Jun 15:27 2007
Picon

RE: Forrestdoc and Maven JXR


> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton <at> gmail.com]
> Sent: Monday, 4 June 2007 8:27 PM
> To: dev <at> forrest.apache.org
> Cc: dev <at> maven.apache.org
> Subject: Forrestdoc and Maven JXR
> 
> Hi,
> 
> The Maven Team want to start a discussion about Forrestdoc and JXR
> projects.
> 
> Background:
> Forrestdoc [1]: Forrestdoc is a Javadoc/Source code/Documentation
> management system.
> JXR [2]: JXR is a source cross reference generator.
> 
> It sounds that these projects are very similar.

I believe both originated from the same code at Alexandria.

> 
> What is the status of Forrestdoc? Any release available? Could we join
> our efforts?

I don't think Forrestdoc has been worked on very much in the last couple of 
years, apart from some general maintenance as part of the rest of the
peoject.

(Continue reading)

Thorsten Scherler (JIRA | 5 Jun 08:44 2007
Picon

[jira] Commented: (FOR-820) tools/forrestdoc needs general tidy up and some documentation to encourage its use


    [
https://issues.apache.org/jira/browse/FOR-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501468
] 

Thorsten Scherler commented on FOR-820:
---------------------------------------

We need to review and see which points are gone:
http://marc.info/?l=forrest-dev&m=107633288925954&w=2
Things to do to make it usable:

0 - make a code scanner so that this can be applied to any project
     without effort
1 - interlink javasrc and javadocs
2 - make javadocs from the xml format (skin)
2 - better uml page
3 - use the javadoc skin to make vizant docs
4 - add source views for other formats
6 - major overhaul of jsdoc

After this:

7 - integrate all in a single navigation - database of references
8 - output also to javahelp format
9 - make plugins for different languages

> tools/forrestdoc needs general tidy up and some documentation to encourage its use
> ----------------------------------------------------------------------------------
>
(Continue reading)

Thorsten Scherler | 5 Jun 08:57 2007
Picon

RE: Forrestdoc and Maven JXR

On Mon, 2007-06-04 at 21:27 +0800, Gav.... wrote:
> 
> > -----Original Message-----
> > From: Vincent Siveton [mailto:vincent.siveton <at> gmail.com]
> > Sent: Monday, 4 June 2007 8:27 PM
> > To: dev <at> forrest.apache.org
> > Cc: dev <at> maven.apache.org
> > Subject: Forrestdoc and Maven JXR
> > 
> > Hi,
> > 
> > The Maven Team want to start a discussion about Forrestdoc and JXR
> > projects.
> > 
> > Background:
> > Forrestdoc [1]: Forrestdoc is a Javadoc/Source code/Documentation
> > management system.
> > JXR [2]: JXR is a source cross reference generator.
> > 
> > It sounds that these projects are very similar.
> 
> I believe both originated from the same code at Alexandria.

http://issues.apache.org/jira/browse/FOR-820 has a nice link 
http://marc.theaimsgroup.com/?l=forrest-dev&m=114082527806288

Yes both are using Alexandria and working together seems to be a topic
before as well.

> 
(Continue reading)


Gmane