RE: [jira] [Commented] (FOR-1188) ant test failure on forrest

[Cyriaque Dupoirieux]

Hi Sjur,

Can you wait few days before to consider the issue as solved ?
I still have the problem with ProjectInfo Plugin (I think this is the 
culprit because it is the only one to use svnHelper...)

* [3/35][0/0] 0.16s  2.0Kb   linkmap.dispatcher.css
X [0] cours/attestation.htmlBROKEN: 
D:\Cyriaque\Perso\forrest\main\webapp\.\D:\Cyriaque\Perso\Em
m\Site 
Internet\build\tmp\D:\Cyriaque\Perso\forrest\build\plugins\svnHelper.xmap 
(Syntaxe du nom de fichier, de r├®pertoire ou de volume inc
orrecte)


Regards,
Cyri@que,

Pensez à l'environnement avant d'imprimer !
Before printing, think about ENVIRONMENTAL responsibility!


-Message d'origine-
De : Sjur N. Moshagen (Commented) (JIRA) [mailto:j...@apache.org]
Envoyé : mardi 20 mars 2012 14:28
À : dev@forrest.apache.org
Objet : [jira] [Commented] (FOR-1188) ant test failure on forrest


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

Sjur N. Moshagen commented on FOR-1188:
---

We updated the forrest installation to the latest svn, and that solved the 
issue. I am tempted to close this bug as solved - any thoughts?

> ant test failure on forrest
> ---
>
> Key: FOR-1188
> URL: https://issues.apache.org/jira/browse/FOR-1188
> Project: Forrest
>  Issue Type: Bug
>  Components: Compile
>Affects Versions: 0.8
>Reporter: Rajith Gunasinghe
>
> Dear all
> I was going to edit perfectly working plugin 
> "org.apache.forrest.plugin.input.projectInfo". Before that i tried to test it 
> using "ant test" command. Then below bug arrised. I have included 
> "antworks-miporter.jar" and "xml-common-resolver.jar".
> Please help me
> Rajith
> D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.projectInf
> o>ant test
> Buildfile:
> D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.projectIn
> fo\build.xml
> init-build-compiler:
> echo-init:
>  [echo]
>  [echo]   
> --
>  [echo]
>  [echo]   Using Apache Ant version 1.8.0 compiled on February 1 2010
>  [echo]   Build file 
> D:\Projects\forrest\plugins\org.apache.forrest.plug
> in.input.projectInfo\build.xml
>  [echo]   Use 'build.[sh|bat] -projecthelp' to see other options.
>  [echo]   Build system home C:\apache-ant-1.8.0
>  [echo]   Build number 12
>  [echo]   Project Name Forrest plugin build file
>  [echo]   Java Version 1.6
>  [echo]   Timestamp 201003311350
>  [echo]
>  [echo]   
> --
>  [echo]
> init:
> clean:
>[delete] Deleting directory
> D:\Projects\forrest\build\plugins\org.apache.forr
> est.plugin.input.projectInfo
> compile:
> jar:
> local-deploy:
>  [echo] Locally deploying org.apache.forrest.plugin.input.projectInfo
>  [copy] Copying 43 files to
> D:\Projects\forrest\build\plugins\org.apache.for
> rest.plugin.input.projectInfo
> build:
> docs:
>  [echo] Building Docs for
> org.apache.forrest.plugin.input.projectInfo
> check-java-version:
>  [echo] This is apache-forrest-0.8
>  [echo] Using Java 1.6 from C:\Program Files\Java\jdk1.6.0_18\jre
>  [echo] Using Apache Ant version 1.8.0 compiled on February 1 2010
> from C:\a
> pache-ant-1.8.0
> init-props:
> echo-settings-condition:
> echo-settings:
> check-skin:
> init-proxy:
> fetch-skins-descriptors:
> fetch-skin:
> unpack-skins:
> init-skins:
> fetch-plugins-descriptors:
>  [echo] Fetching plugins descriptor:
> http://forrest.apache.org/plugins/plugi
> ns.xml
>   [get] Getting: http://forrest.apache.org/plugins/plugins.xml
>   [get] To:
> D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.proj
> ectInfo\build\tmp\plugins-1.xml
>   [get] local file date : Wed Mar 24 13:38:56 IST 2010
>   [get] Not modified - so not downloaded
>  [echo] Fetching plugins descriptor:
> http://forrest.apache.org/plugins/white
> board-plugins.xml
>   [get] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
>   [get] To:
> D:\Projects\forrest\plugins\org.apache.forrest.plugin.input.proj
> ectInfo\build\tmp\plugins-2.xml
>   [get] local file date : Thu Mar 04 15:05:34 IST 2010
>   [get] Not modified - so not downloaded
>  [echo] Plugin list loaded from
> http://forrest.apache.org/plugins/plugins.xm
> l.
>  [echo] Plugin list loaded from
> http://forrest.apache.org/plugins/whiteboard
> -plugins.xml.
> init-plugins:
>  [copy] Copying 1 file to
> D:\Projects\forrest\plugins\org.apache.forrest.plu
> gin.input.projectInfo\build\tmp
>  [copy] Copying 1 file to
> D:\Projects\forrest\plugins\org.apache.forrest.plu
> gin.input.projectIn

Re: [Vote] Release Plan for Forrest 0.90

[Cyriaque Dupoirieux]

+1

Salutations,
Cyriaque


Le 14/12/2010 03:52, Brian M Dube a écrit :

On Tue, Dec 14, 2010 at 10:15:03AM +1100, David Crossley wrote:

Please vote on this release plan.

According to our guidelines,
http://forrest.apache.org/guidelines.html#actions
"A lazy majority vote requires
3 binding +1 votes and more binding +1 votes than -1 votes".

As usual anyone is encouraged to vote, just the votes
of PMC members are binding.

+1

-Brian

Re: Merging back the dispatcher

[Cyriaque Dupoirieux]

le 22/04/2010 12:24 Ross Gardler a écrit :
> On 22/04/2010 00:54, Tim Williams wrote:
>   
>> On Mon, Dec 7, 2009 at 6:19 PM, Tim Williams  wrote:
>> 
>>> On Sun, Dec 6, 2009 at 9:38 PM, David Crossley  wrote:
>>>   
 Tim Williams wrote:
 
> reason I ask, is that we have FOR-1198 and FOR-796 both as "blockers"
>   
 No such issue. Rather FOR-1108 and FOR-796.
 
>>> Arghh, typo, Thanks David.  So, are we leaving dispatcher in the
>>> whiteboard for now?
>>>   
>> Hate to be a nag, but... are we leaving dispatcher in the whiteboard
>> for the 0.9 release?  It's complicated b/c we have [at least] two
>> things working at odds here:  1) dispatcher has come to be in popular
>> use despite its status and 2) being in the whiteboard, it wouldn't
>> make it in the actual release.
>>
>> So, thoughts?
>> 
> I've wanted dispatcher in core since the 0.8 release for this very reason.
>
> However, now I'm only an observer here I'll refrain from arguing for or 
> against, just settle with pointing out that I think it would be a 
> mistake to leave it out of 0.9 unless it were to delay the release 
> unreasonably (ahem).
>
> If it doesn't go in I would want to see a 0.10 within months with 
> dispatcher in.
>   
I agree with you Ross,
I think forrest needs a new release to make it clear that forrest is not
dead...
But we should also think about a R0.10 planned ASAP.
(We discussed this one or two years ago and decided at this time that it
should be great to be able to plan new releases every 3 or four months...)

Saluations,
Cyriaque,
> Ross
>
>   

Re: Dispatcher Specific characters problem

[Cyriaque Dupoirieux]

le 07/04/2010 13:50 Thorsten Scherler a écrit :
> On 31/03/2010, at 11:48, Cyriaque Dupoirieux wrote:
>
>   
>> Hi,
>>
>>I have problems with the dispatcher which generate strange
>> charachters - generally  instead of   which should be a blank if I
>> remember...
>>These characters drive me to a second error during pdf generation :
>> [Fatal Error] :6:25: Invalid byte 2 of 3-byte UTF-8 sequence.
>>
>>I tried to remove   from
>> forrest\build\plugins\org.apache.forrest.plugin.internal.dispatcher\themer\themes\common\html\branding-fontsize.contract.xml
>> to make a test and then it's OK, the special characters are not generated.
>>
>>I wonder if I am the only one and if my machine needs a specific
>> configuration or if we should remove these characters from the dispatcher.
>> 
> It should work fine, however I must admit that I have not tested the pdf part 
> very well.
>
> I will try this week and report back.
>   
It seems that there are some problems with encoding format (cf. previous
thread "forrest-sample-2 FAILED and build test failed: Could not resolve
locat <http://article.gmane.org/gmane.text.xml.forrest.devel/27677>")
This occurs for some dispatcher intermediate files and on Windoze.
I am going to check in a Mandriva Linux when I have time...


Salutations,
Cyriaque

> salu2
>
> Thorsten Scherler 
> Open Source Java 
>
>   

Dispatcher Specific characters problem

[Cyriaque Dupoirieux]

Hi,

I have problems with the dispatcher which generate strange
charachters - generally  instead of   which should be a blank if I
remember...
These characters drive me to a second error during pdf generation :
[Fatal Error] :6:25: Invalid byte 2 of 3-byte UTF-8 sequence.

I tried to remove   from
forrest\build\plugins\org.apache.forrest.plugin.internal.dispatcher\themer\themes\common\html\branding-fontsize.contract.xml
to make a test and then it's OK, the special characters are not generated.
   
I wonder if I am the only one and if my machine needs a specific
configuration or if we should remove these characters from the dispatcher.

My tests have been done on Windows XP environment...


-- 
Salutations,
Cyriaque

Re: [VOTE] - Upgrade Java Version to 1.5

[Cyriaque Dupoirieux]

+1,

le 04/03/2010 01:02 Gav... a écrit :
> Hi All,
>
> This vote is to move 'trunk' to using java version 1.5.
> This also means advising users/devs that this is the minimum required
> version and that testing on versions of Java earlier than 1.5 will not be
> supported.
>
> Parts of the current trunk, including 'Dispatcher' do not work or do not
> work well with Java 1.4.x
>
> I have tested current trunk and dispatcher with Java 1.5 and it works well
> FOR ME. Java 1.6 also works fine.
>
> I propose that we move to Java 1.5 on trunk immediately following a
> successful vote. I also propose that before voting, that devs TEST Java 1.5
> on trunk and in their own current usage. Only vote for this change if you
> are happy that things will continue to work or will begin to work well for
> YOU.
>
> This vote for moving to Java 1.5 is to last until at least after the next
> release, so that we have at least one official release using the minimum
> Java 1.5 spec.
>
> Please take your time and vote when your ready, this vote will run for ONE
> WEEK beginning now and ending on 11th March 2010 12PM (noon) GMT time.
>
> [ ] - +1 Yes let's make the move.
>
> [ ] - +/-0 I don't mind either way.
>
> [ ] - -1 I strongly object and here are my reasons ...
>
> Thanks All
>
> Gav..
>
>
>   

Re: Java Version (was RE: Can't get Dispatcher working at all windows/linux from trunk)

[Cyriaque Dupoirieux]

le 02/03/2010 11:44 Thorsten Scherler a écrit :
> On Sat, 2010-02-27 at 07:37 -0500, Tim Williams wrote:
>   
>> On Sat, Feb 27, 2010 at 7:08 AM, Gav...  wrote:
>> 
>>>
>>>   
 -Original Message-
 From: David Crossley [mailto:cross...@apache.org]
 Sent: Monday, 22 February 2010 8:11 PM
 To: dev@forrest.apache.org
 Subject: Re: Can't get Dispatcher working at all windows/linux from
 trunk

 
>>> 
>>>   
 As said before, one of the issues is the agreed Java base version.
 See the "build.compiler.vm" parameter in our build.xml
 and instructions in the Release documentation and recent discussion
 in these dev archives.

 -David
 
>>> Seems to me, from my tests at least on linux/windows, it is the only issue
>>> in
>>> getting dispatcher working. All of the plugins would need checking too I
>>> guess.
>>>
>>> so how about we get on and vote for moving to 1.5 immediately and for the
>>> next
>>> release, deciding after then to perhaps move to 1.6 ?
>>>   
>> +1
>> 
> +1
>
>   
+1,
Salutations,
Cyriaque,
> ...but as David always says: this is not a vote thread, but the issue
> needs one.
>
> salu2
>   

Re: Can't get Dispatcher working at all windows/linux from trunk

[Cyriaque Dupoirieux]

le 22/02/2010 15:53 Gav... a écrit :
>
>   
>> -Original Message-
>> From: Thorsten Scherler
>> 
>>> ... SNIP ...
>>>   
>>
>> D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apac
>> he.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\pl
>> ugins\org.apache.forrest.plugin.input.projectInfo
>> 
>>> (Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
>>>   
>>
>> Hmm that reminds me on a bug that gavin had and fixed. It was something
>> about the locationmap and add a certain location, but I am not
>> remembering the issue anymore. ...but AFAIR there was a comment in the
>> code somewhere about it.
>>
>> Gavin do you remember?
>> 
> I looked, seems like the problem encountered in FOR-1108 - in fact Cyriaque 
> commented
> the exact same problem in October 2008. Look at the SVN tab on that issue to 
> see
> what was done to cure that.
>
> Cyriaque, are you using a year old trunk? Any reason not to update?
>
> Gav...
>
Ho ? I am going to check if I have a local copy modified - and then not
up-to-date with the trunk
I try this morning and tell you,

Salutations,
Cyriaque,

Re: Can't get Dispatcher working at all windows/linux from trunk

[Cyriaque Dupoirieux]

le 22/02/2010 11:48 Thorsten Scherler a écrit :
> On Mon, 2010-02-22 at 20:22 +1000, Gav... wrote:
>   

... SNIP ...
>>> I did *not* get it working. I needed to go back to before
>>> the Dispatcher merge. I did 'svn up' to r882421 2009-11-20.
>>>   
>> Ah right, ok, same as what I did then, 'somebody' must have it working 
>> and it needs to be sorted soon otherwise it doesn't belong in trunk.
>> 
> Hmm, I will try now as well. Can you post the exception that you got
> again, please
>> As said before, one of the issues is the agreed Java base version.
>> See the "build.compiler.vm" parameter in our build.xml
>> and instructions in the Release documentation and recent discussion
>> in these dev archives.
>> 
>> Yep, I read briefly but need to go back in case I missed something.
>>
>> One thing is for sure, the forward momentum of this project depends on this
>> being resolved, and soon. We should vote on a minimum version of java soon, 
>> then work on fixing it for that version - as tried and tested as much as I 
>> have, dispatcher for me doesn't work in any of them.
>> 
> I personally prefer to use 1.6 as minimum since 1.4 and 1.5 are not
> officially supported anymore. However to make the dispatcher work with
> 1.4 is not that hard since it is mostly generic compilation exception. 
>
> salu2
>   
I agree, I don't see the use to be compliant with old java versions...
I have lots of problems to make the dispatcher work again and it may be
why I am very silent at the moment.
I hope I can help if someone can give me some clues...
Here are the problems I met with the dispatcher plugin generation with
build.compiler.vm=1.5 :

...

Cocoon will report the status of each document:
  - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).


cocoon 2.1.12-dev
Copyright (c) 1999-2007 Apache Software Foundation. All rights reserved.

^int/
^examples/
* [1/26][26/29]   12.671s 10.1Kb  linkmap.html
* [3/24][0/0] 0.125s 2.0Kb   linkmap.dispatcher.css
X [0] changes.html  BROKEN:
D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apache.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
X [0] todo.html BROKEN:
D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apache.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
* [6/21][0/0] 0.093s 1.2Kb   themes/leather-dev.css
X [0]
how/howto-dispatcher-contracts.html   BROKEN:
D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apache.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\plugins\svnHelper.xmap
(Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
* [8/38][19/19]   0.266s 18.4Kb  themes/pelt.screen.css
* [9/37][0/0] 0.234s 347b   
themes/images/roundcorner-b-l-15-bgFF-stroke4A6D8C-fg4A6D8C.png
* [10/36]   [0/0] 0.047s 201b   
themes/images/roundcorner-b-r-5-bgFF-stroke4A6D8C-fg4A6D8C.png
X [0] int/index.htmlBROKEN:
D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apache.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\plugins\svnHelper.xmap
(Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
* [14/32]   [0/0] 4.687s 6.6Kb   images/project.png
* [15/31]   [0/0] 0.063s 316b   
themes/images/roundcorner-b-r-15-bgFF-stroke4A6D8C-fg4A6D8C.png
* [16/30]   [0/0] 0.047s 214b   
themes/images/roundcorner-t-r-5-bg294563-strokeB5C7E7-fgB5C7E7.png
* [17/29]   [0/0] 0.047s 385b   
themes/images/roundcorner-t-r-15-bgFF-stroke4A6D8C-fg4A6D8C.png
* [18/28]   [0/0] 0.093s 1.2Kb   themes/pelt.print.css
X [0] dispatcher-glossary.html 
BROKEN:
D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apache.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\plugins\svnHelper.xmap
(Syntaxe du nom de fichier, de rÚpertoire ou de volume incorrecte)
* [21/25]   [0/0] 0.047s 321b   
themes/images/roundcorner-b-l-15-bg294563-stroke4A6D8C-fg4A6D8C.png
* [24/22]   [0/0] 0.047s 296b   
themes/images/roundcorner-b-r-15-bg294563-stroke4A6D8C-fg4A6D8C.png
X [0] examples/index.html   BROKEN:
D:\duc\forrest\main\webapp\.\D:\duc\forrest\whiteboard\plugins\org.apache.forrest.plugin.internal.dispatcher\build\tmp\D:\duc\forrest\build\plugins\svnHelper.xmap

Re: Dispatcher problem with forrest seed

[Cyriaque Dupoirieux]

le 24/12/2009 06:28 Brian M Dube a écrit :
> On Tue, Dec 22, 2009 at 05:14:00PM +1100, David Crossley wrote:
>   
>> Cyriaque Dupoirieux wrote:
>> 
>>> I don't succeed to generate the basic forrest seed with the dispatcher.
>>>   
>> I just tried a fresh seed site, and no such problems here
>> (Macintosh with either java-1.5 or 1.4.2).
>> 
> I've rebuilt and I see the same issue on Linux with OpenJDK 1.6.0.
>   
You have the same configuration than I. I also have a JDK 1.6 It may be
the problem.
I set the build.compiler.vm=1.5 in my forrest.properties but the problem
remains.

>   
>> Also the forrestbot on the zone server is not reporting such problems
>> (Solaris 10 with java-1.4.2).
>> 
> That is odd. I thought I had rebuilt when I first read Cyriaque's
> report, but I'm sure that I have three times now. I'll step back in
> svn until I build cleanly again, but probably not tonight.
>
>   
I have also done this, error messages are still there.

>> Oh, have you re-built Forrest in 'main' after the merge
>> of the Dispatcher branch recently? See mail here around
>> December 2 to December 5.
>>
>> -David
>> 
> This last bit doesn't belong in this thread, but I noticed it while
> looking into this issue and I'm being lazy. The icon-b.png
> error. Maybe not everyone experiences it, but I believe it has been
> brought up before. While looking at the issue of this thread, I
> noticed build/images/icon-b.png, while the rest of the build is under
> build/site. Surely that's the cause of the NullPointer(FileNotFound)
> exception that Java throws, but there's a larger problem involved. We
> cannot, must not, may not *write* in the filesystem outside the
> expected target. I think this issue has been raised in the past.
> I'll try to look into it; this is merely the lazy documentation
> of what I've found.
>   
This is weird, the /site/samples-b/linking.html page shows the
icon-b.png in the example 5 (generated without the dispatcher)
I think we should change the name of every images used in these examples
(like 1, 2, 3 and so on.) to be able to find more quickly the problem.
In the list, 3 examples use the icon-a.png...

I think this error is old,


Happy Christmas, and read you next year...


Salutations,
Cyriaque
> Brian
>   

Dispatcher problem with forrest seed

[Cyriaque Dupoirieux]

Hi,

I don't succeed to generate the basic forrest seed with the dispatcher.
I get the following errors :
...
* [7/56][3/35]10.86s 10.2Kb  samples-b/usemap.html
X [0] themes/images/round
The attribute "transform" of the element  is invalid
* [10/55]   [2/34]1.563s 10.4Kb  samples-b/faq.html
X [0] themes/images/round
The attribute "transform" of the element  is invalid
* [12/56]   [3/22]1.281s 7.8Kb   samples-a/index.html
...

or :

* [62/48]   [0/0] 0.313s 2.0Kb   samples-c/index.dispatcher.css
[Fatal Error] :6:25: Invalid byte 2 of 3-byte UTF-8 sequence.
X [0] samples-b/svg.pdf BROKEN:
Invalid byte 2 of 3-byte UTF-8 sequence.
[Fatal Error] :6:25: Invalid byte 2 of 3-byte UTF-8 sequence.
X [0] samples-b/no-dtd.pdf  BROKEN:
Invalid byte 2 of 3-byte UTF-8 sequence.
* [67/43]   [0/0] 0.11s  5.1Kb   themes/common.css
...

I want to be back in the forrest development, so if someone could help ;)

Salutations,
Cyriaque,

Problem with odt input plugin

[Cyriaque Dupoirieux]

[Original Subject was : RE: [important] developers need to assist each
other]
>> -Original Message-
>> From: Cyriaque Dupoirieux [mailto:cyriaque.dupoiri...@pco-innovation.com]
>> Sent: Friday, 6 March 2009 8:16 PM
>> To: dev@forrest.apache.org
>> Subject: Re: [important] developers need to assist each other
>> 
>> le 05/03/2009 21:59 Thorsten Scherler a écrit :
>> > On Wed, 2009-02-18 at 18:48 +1100, David Crossley wrote:
>> >
>> > I hope that people will give me support (as they always did) when
>> > I shortly will merge back the dispatcher rewrite and volunteer to
>> > get a long overdue forrest 0.9 release out.
>> >
>> I really would like to help in that task.
> 
> Excellent, I'll be around too (fwiw).
> 
>> I have several problems to solve with my own site, that is why I am not
>> very verbose at the moment :
>> 
>> * odt plugin does not manage pictures as it should, I think this is
>>   due to a change in the file format since the 3.0.1, but I have to
>>   investigate
> 
> Remind me, which ODT plugin do you use ? the input.odt ?

I use the org.apache.forrest.plugin.input.odt...

But with the latest test I have done, the problems I have occur only
during the pdf generation.

Something like :

ERROR - I/O error while loading image: null
ERROR - Image not found:
cocoon://samples/samples/openDocumentEmbeddedImages/zip-firefox.odt/file-Pictures/111C004A32685BF6.png

And the image is not in samples/samples but samples...

I have to look at what is the intermediate format generated by the plugin...

Salutations,
Cyriaque,

> 
>> 
>> 
>> --
>> Salutations,
>> Cyriaque

Re: [important] developers need to assist each other

[Cyriaque Dupoirieux]

le 05/03/2009 21:59 Thorsten Scherler a écrit :
> On Wed, 2009-02-18 at 18:48 +1100, David Crossley wrote:
> ...
>   
>> However, recently i notice that people are not being
>> answered on the dev list. For example both Tim and Thorsten
>> have issues that need assistance.
>> 
>
> I did not found time to answer this mail till now.
> Thank you David for your good intention. 
>
> Actually only some quite specific mails from me have not found 
> any answers but I understand this. 
>
> I hope that people will give me support (as they always did) when 
> I shortly will merge back the dispatcher rewrite and volunteer to 
> get a long overdue forrest 0.9 release out.
>   
I really would like to help in that task.
I have several problems to solve with my own site, that is why I am not
very verbose at the moment :

* odt plugin does not manage pictures as it should, I think this is
  due to a change in the file format since the 3.0.1, but I have to
  invetigate
* php generation does work any more since the new coccoon version...

And since my site is based on odt and often uses php...

Anyway, I'll be there to help,

Salutations,
Cyriaque,
> I would love to help to port forrest to cocoon 2.2 again since it solves
> some common integration problems quite nicely. However due to time constrains
> I cannot take the lead on this but I have ported some forrest components 
> to cocoon 2.2 blocks a while ago and it is not hard to port the rest. 
> It only takes up lots of time for a single person to move the whole code 
> to blocks. 
>
>   
>> Remember that anyone who is subscribed to this
>> dev mail list should assist. Not just ASF committers.
>> 
>
> That is so true.
>
> salu2
>   


-- 
Salutations,
Cyriaque
PCO Cyriaque DUPOIRIEUX
Consultant
Consultant //
Tel> +33 (0)5 34 60 44 13 
Mob>+33 (0)6 30 29 17 07PCO Innovation
Immeuble BUROLINES
2 ter, rue Marcel DORET
31700 BLAGNAC - France
Tel > + 33 (0)5 34 60 59 75
Fax > + 33 (0)5 34 60 44 10
http://www.pco-innovation.com <http://www.pco-innovation.com/>

CONFIDENTIALITE : Ce message et les éventuelles pièces attachées sont
confidentiels. Si vous n'êtes pas dans la liste des destinataires,
veuillez informer l'expéditeur immédiatement et ne pas divulguer le
contenu à une tierce personne, ne pas l'utiliser pour quelque raison que
ce soit, ne pas stocker ou copier l'information qu'il contient sur un
quelconque support. Tout droits réservés.
/CONFIDENTIALITY : This e-mail and any attachments are confidential and
may be privileged. If you are not a named recipient, please notify the
sender immediately and do not disclose the contents to another person,
use it for any purpose or store or copy the information in any medium.
All rights reserved. / //
P   

Pensez à l'environnement avant d'imprimer !/
Before printing, think about ENVIRONMENTAL responsibility!/

RE : svn commit: r732245 - in /forrest/trunk: plugins/org.apache.forrest.plugin.input.PhotoGallery/ plugins/org.apache.forrest.plugin.input.projectInfo/ plugins/org.apache.forrest.plugin.input.simplif

[Cyriaque Dupoirieux]

Why several 2008 and some 2009 ?
Should be 2009 for every copyright, no ?


Salutations,
Cyriaque Dupoirieux,
(Happy new year by the way ;-) )

De : cross...@apache.org [cross...@apache.org]
Date d'envoi : mercredi 7 janvier 2009 08:02
À : s...@forrest.apache.org
Objet : svn commit: r732245 - in /forrest/trunk: 
plugins/org.apache.forrest.plugin.input.PhotoGallery/ 
plugins/org.apache.forrest.plugin.input.projectInfo/ 
plugins/org.apache.forrest.plugin.input.simplifiedDocbook/ 
plugins/org.apache.forrest.plugin.input.wiki/...

Author: crossley
Date: Tue Jan  6 23:02:12 2009
New Revision: 732245

URL: http://svn.apache.org/viewvc?rev=732245&view=rev
Log:
Ensure that all plugins which had edits during 2008, now have 2008 copyright 
year. Browsed via viewvc.

Modified:

forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery/NOTICE.txt
forrest/trunk/plugins/org.apache.forrest.plugin.input.projectInfo/NOTICE.txt

forrest/trunk/plugins/org.apache.forrest.plugin.input.simplifiedDocbook/NOTICE.txt
forrest/trunk/plugins/org.apache.forrest.plugin.input.wiki/NOTICE.txt
forrest/trunk/plugins/org.apache.forrest.plugin.output.POD/NOTICE.txt
forrest/trunk/plugins/pluginTemplate/NOTICE.txt

forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.baetle/NOTICE.txt

forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.foaf/NOTICE.txt

forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.input.odt/NOTICE.txt

forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.NoteTaking/NOTICE.txt

Modified: 
forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery/NOTICE.txt
URL: 
http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery/NOTICE.txt?rev=732245&r1=732244&r2=732245&view=diff
==
--- 
forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery/NOTICE.txt 
(original)
+++ 
forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery/NOTICE.txt 
Tue Jan  6 23:02:12 2009
@@ -1,5 +1,5 @@
 Apache Forrest
-Copyright 2002-2007 The Apache Software Foundation.
+Copyright 2002-2008 The Apache Software Foundation.

 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).

Modified: 
forrest/trunk/plugins/org.apache.forrest.plugin.input.projectInfo/NOTICE.txt
URL: 
http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.input.projectInfo/NOTICE.txt?rev=732245&r1=732244&r2=732245&view=diff
==
--- 
forrest/trunk/plugins/org.apache.forrest.plugin.input.projectInfo/NOTICE.txt 
(original)
+++ 
forrest/trunk/plugins/org.apache.forrest.plugin.input.projectInfo/NOTICE.txt 
Tue Jan  6 23:02:12 2009
@@ -1,5 +1,5 @@
 Apache Forrest
-Copyright 2002-2007 The Apache Software Foundation.
+Copyright 2002-2008 The Apache Software Foundation.

 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).

Modified: 
forrest/trunk/plugins/org.apache.forrest.plugin.input.simplifiedDocbook/NOTICE.txt
URL: 
http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.input.simplifiedDocbook/NOTICE.txt?rev=732245&r1=732244&r2=732245&view=diff
==
--- 
forrest/trunk/plugins/org.apache.forrest.plugin.input.simplifiedDocbook/NOTICE.txt
 (original)
+++ 
forrest/trunk/plugins/org.apache.forrest.plugin.input.simplifiedDocbook/NOTICE.txt
 Tue Jan  6 23:02:12 2009
@@ -1,5 +1,5 @@
 Apache Forrest
-Copyright 2002-2007 The Apache Software Foundation.
+Copyright 2002-2008 The Apache Software Foundation.

 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).

Modified: forrest/trunk/plugins/org.apache.forrest.plugin.input.wiki/NOTICE.txt
URL: 
http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.input.wiki/NOTICE.txt?rev=732245&r1=732244&r2=732245&view=diff
==
--- forrest/trunk/plugins/org.apache.forrest.plugin.input.wiki/NOTICE.txt 
(original)
+++ forrest/trunk/plugins/org.apache.forrest.plugin.input.wiki/NOTICE.txt Tue 
Jan  6 23:02:12 2009
@@ -1,5 +1,5 @@
 Apache Forrest
-Copyright 2002-2007 The Apache Software Foundation.
+Copyright 2002-2008 The Apache Software Foundation.

 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).

Modified: forrest/trunk/plugins/org.apache.forrest.plugin.output.POD/NOTICE.txt
URL: 
http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.output.POD/NOTICE.txt?rev=732245&r1=732244&r2=732245&view=diff
=

Re: svn commit: r725650 - /forrest/branches/dispatcher_rewrite/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java

[Cyriaque Dupoirieux]

Thosten,

Are you working on the main branch or are you developing in another
one ?
Because, as you know, I use the dispatcher and I would like to use
the version you are working on...

Salutations,
Cyriaque,

le 11/12/2008 11:44 [EMAIL PROTECTED] a écrit :
> Author: thorsten
> Date: Thu Dec 11 02:44:33 2008
> New Revision: 725650
>
> URL: http://svn.apache.org/viewvc?rev=725650&view=rev
> Log:
> Using the config to determine whether we are allowed to parse properties
>
> Modified:
> 
> forrest/branches/dispatcher_rewrite/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java
>
> Modified: 
> forrest/branches/dispatcher_rewrite/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java
> URL: 
> http://svn.apache.org/viewvc/forrest/branches/dispatcher_rewrite/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java?rev=725650&r1=725649&r2=725650&view=diff
> ==
> --- 
> forrest/branches/dispatcher_rewrite/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java
>  (original)
> +++ 
> forrest/branches/dispatcher_rewrite/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java
>  Thu Dec 11 02:44:33 2008
> @@ -237,8 +237,6 @@
>  
>private HashMap localParams;
>  
> -  private boolean allowXml;
> -
>private String currentProperty;
>  
>private InputStream dataStream;
> @@ -259,7 +257,7 @@
>  config = new WritableDispatcherBean();
>  config.setStaxHelper(new StAX());
>  // are we allowing xml properties?
> -allowXml = configuration.getChild("allowXml").getValueAsBoolean(false);
> +boolean allowXml = 
> configuration.getChild("allowXml").getValueAsBoolean(false);
>  config.setAllowXmlProperties(allowXml);
>  // set the prefix for the contract resolving
>  contractUriPrefix = configuration.getChild("contractUriPrefix").getValue(
> @@ -401,9 +399,7 @@
>  } else if (Captions.NS.equals(uri)) {
>// we are in the dispatcher ns
>try {
> -/*
> - * We are in the dispatcher ns.
> - */
> +// We are in the dispatcher ns.
>  getLogger().debug("Starting dispatcher element: " + raw);
>  if (Captions.STRUCTURE_ELEMENT.equals(name)) {
>// we are in a structurer definition
> @@ -458,7 +454,7 @@
>contractProcessingEnd();
>  } else if (Captions.PROPERTY_ELEMENT.equals(name) && 
> this.includeNodes) {
>// we are inside a property end element
> -  if (allowXml) {
> +  if (config.isAllowXmlProperties()) {
>  String property = null;
>  try {
>//XMLizable endSAXRecording = super.endSAXRecording();
> @@ -692,7 +688,7 @@
>  }
>  currentProperty = id;
>  // if we allow xml properties we will just record them
> -if (allowXml) {
> +    if (config.isAllowXmlProperties()) {
> // just start the recording
>prefixString = "<"+raw+attributesString+">";
>startSerializedXMLRecording((XMLUtils.createPropertiesForXML(true)));
>
>
>   


-- 
Salutations,
Cyriaque
PCO Cyriaque DUPOIRIEUX
Consultant
Consultant //
Tel> +33 (0)5 34 60 44 13 
Mob>+33 (0)6 30 29 17 07PCO Innovation
Immeuble BUROLINES
2 ter, rue Marcel DORET
31700 BLAGNAC - France
Tel > + 33 (0)5 34 60 59 75
Fax > + 33 (0)5 34 60 44 10
http://www.pco-innovation.com <http://www.pco-innovation.com/>

CONFIDENTIALITE : Ce message et les éventuelles pièces attachées sont
confidentiels. Si vous n'êtes pas dans la liste des destinataires,
veuillez informer l'expéditeur immédiatement et ne pas divulguer le
contenu à une tierce personne, ne pas l'utiliser pour quelque raison que
ce soit, ne pas stocker ou copier l'information qu'il contient sur un
quelconque support. Tout droits réservés.
/CONFIDENTIALITY : This e-mail and any attachments are confidential and
may be privileged. If you are not a named recipient, please notify the
sender immediately and do not disclose the contents to another person,
use it for any purpose or store or copy the information in any medium.
All rights reserved. / //
P   

Pensez à l'environnement avant d'imprimer !/
Before printing, think about ENVIRONMENTAL responsibility!/

[jira] Commented: (FOR-984) validate-sitemap target fails relaxng validation on some JDK 1.6: missing datatypes

[Cyriaque Dupoirieux (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650951#action_12650951
 ] 

Cyriaque Dupoirieux commented on FOR-984:
-

I have tested what David wanted :

Environment : Windows XP

java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)

forrest validate :
... 
validate-xdocs:
Warning: Reference forrest.cp has not been set at runtime, but was found during
build file parsing, attempting to resolve. Future versions of Ant may support
 referencing ids defined in non-executed targets.
31 file(s) have been successfully validated.
...validated xdocs

validate-skinconf:
1 file(s) have been successfully validated.
...validated skinconf

validate-sitemap:
...validated project sitemap

validate-skinchoice:
...validated existence of skin 'pelt'

BUILD SUCCESSFUL
Total time: 8 seconds


> validate-sitemap target fails relaxng validation on some JDK 1.6: missing 
> datatypes
> ---
>
> Key: FOR-984
> URL: https://issues.apache.org/jira/browse/FOR-984
> Project: Forrest
>  Issue Type: Improvement
>  Components: Core operations, Launch 'forrest'
>Affects Versions: 0.8, 0.9-dev
>Reporter: Schumarer
> Fix For: 0.9-dev
>
> Attachments: log.txt
>
>
> Doing 'forrest' fails at the validate-sitemap task. Missing the RELAX NG 
> datatype library ...
> validate-sitemap:
> D:\apache-forrest-0.8rc\main\webapp\resources\schema\relaxng\sitemap-v06.rng:72:31:
> error: datatype library "http://www.w3.org/2001/XMLSchema-datatypes"; not 
> recognized
> People should be able to work around that by editing their forrest.properties 
> configuration to expose the "forrest.validate.sitemap" property and set it to 
> "false". Might need to do the same for the "forrest.validate.stylesheets" 
> property.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (FOR-1108) Dispatcher, Cocoon 2.1 and Windows

[Cyriaque Dupoirieux (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642909#action_12642909
 ] 

Cyriaque Dupoirieux commented on FOR-1108:
--

Test with txt output plugin...

If I access (forrest run) to the index.txt I get :
Internal Server Error
   Message: null
   Description: No details available.
   Sender: org.apache.cocoon.servlet.CocoonServlet
   Source: Cocoon Servlet
   Request URI
  index.txt
   cause
   
D:\duc\forrest\main\webapp\D:\duc\forrest\plugins\org.apache.forrest.plugin.output.Text\build\tmp\D:\duc\forrest\build\plugins\org.apache.forrest.plugin.output.Text
 (Syntaxe du nom de fichier, de répertoire ou de volume incorrecte)
request-uri
  /index.txt
and if I comment the xsl parameter in the output.xmap :
  

  
  





  

  
Then it generates something...


> Dispatcher, Cocoon 2.1 and Windows
> --
>
> Key: FOR-1108
> URL: https://issues.apache.org/jira/browse/FOR-1108
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations, Plugin: internal.dispatcher
>Affects Versions: 0.9-dev
>Reporter: Ross Gardler
>Priority: Blocker
> Fix For: 0.9-dev
>
> Attachments: core.log, test.log, test_dispatcher_site.zip, 
> testRunWithDebug.log
>
>
> Since the update to Cocoon 2.1 Forrest and Dispatcher have broken on windows.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (FOR-1108) Dispatcher, Cocoon 2.1 and Windows

[Cyriaque Dupoirieux (JIRA)]

[ 
https://issues.apache.org/jira/browse/FOR-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640114#action_12640114
 ] 

Cyriaque Dupoirieux commented on FOR-1108:
--

Exact,

The problem, with the dispatcher comes from the line :
  
in the internal.xmap.

If I change the order of the  tags, the file not found is the first tag 
encoutered (ls.xmap in my case...)

So it is clearly the "mounts" in general. I am sure that the skinned site 
generation has the same problem.

No we have to investigate to understand why the src of the file to be mounted 
is translated to a very strange url :
X [0] linkmap.html  BROKEN: 
D:\duc\forrest\main\webapp\.\D:\duc\viewSitePerso\build\tmp\D:\d
\forrest\build\plugins\ls.xmap (Syntaxe du nom de fichier, de rÚpertoire ou de 
volume incorrecte)
Total time: 0 minutes 6 seconds,  Site size: 0 Site pages: 0

I have an installation on windows so If someone has an idea, I can test it.

> Dispatcher, Cocoon 2.1 and Windows
> --
>
> Key: FOR-1108
> URL: https://issues.apache.org/jira/browse/FOR-1108
> Project: Forrest
>  Issue Type: Bug
>  Components: Core operations, Plugin: internal.dispatcher
>Affects Versions: 0.9-dev
>Reporter: Ross Gardler
>Priority: Blocker
> Fix For: 0.9-dev
>
> Attachments: core.log, test.log, test_dispatcher_site.zip, 
> testRunWithDebug.log
>
>
> Since the update to Cocoon 2.1 Forrest and Dispatcher have broken on windows.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[forrest seed] problem with dispatcher

[Cyriaque Dupoirieux]

Hi,

I have not been working with my site for a long time, and now I
cannot generate it again.
I have tried to generate a newly seeded site configured for the
dispatcher and I get :


cocoon 2.1.12-dev
Copyright (c) 1999-2007 Apache Software Foundation. All rights reserved.

X [0] linkmap.html  BROKEN:
D:\duc\forrest\main\webapp\.\D:\duc\ForrestSeed\build\tmp\D:\duc\forrest\build\plugins
\dataModel.xmap (Syntaxe du nom de fichier, de rÚpertoire ou de volume
incorrecte)
Total time: 0 minutes 2 seconds,  Site size: 0 Site pages: 0
Java Result: 1

  Copying broken links file to site root.

Copying 1 file to D:\duc\ForrestSeed\build\site

BUILD FAILED
D:\duc\forrest\main\targets\site.xml:183: Error building site.




Do I have to try the new Dispatcher branch or is there something I
haven't understood ?

Thank you,

-- 
Salutations,
Cyriaque

Re: ODT plugins - we should unify them

[Cyriaque Dupoirieux]

le 17/09/2008 12:03 Thorsten Scherler a écrit :
> On Wed, 2008-09-17 at 19:37 +1000, Gavin wrote:
>   
>>> -Original Message-
>>> From: Thorsten Scherler [mailto:[EMAIL PROTECTED]
>>> Sent: Wednesday, 17 September 2008 7:21 PM
>>> To: dev@forrest.apache.org
>>> Subject: ODT plugins - we should unify them
>>>
>>> Hi all,
>>>
>>> some other aired this concern before but latest user thread revealed
>>> that we should reduce the number of plugins around OO.
>>>
>>> Can't we unify them into one?
>>>   
>> Which are we talking about, the OpenOffice.org output and the OOo output ?
>>
>> If so , the first is OpenOffice v1 and second is OpenOffice.org V2 and is
>> based more on the OpenDocument format whereas version 1 is not.
>> One outputs sxw and the other outputs odt.
>>
>> Despite the names, it would be like merging Word and Excel together.
>>
>> I suppose we can put the stylesheets etc all under one roof, and be able to
>> output eiter sxw or odt depending on the users needs.
>>
>> I need to concentrate on Version 2, rather than the 6 years obsolete version
>> 1. But can look into it another time.
>> 
>
> Personally I think the legacy code should be moved to whiteboard (with a
> BIG Deprecated warning).
>
> I can see:
> plugins/org.apache.forrest.plugin.input.OpenOffice.org
> whiteboard/plugins/org.apache.forrest.plugin.input.odt
>   
Hum, why do you want to deprecate this one ?
This is the current opendocument format used by OpenOffice.org.

Cyriaque,
> whiteboard/plugins/org.apache.forrest.plugin.OpenOffice.org-output
> whiteboard/plugins/org.apache.forrest.plugin.output.OOo
>
> salu2
>
>   
>> Gav...
>>
>> 
>>> salu2
>>> --
>>> Thorsten Scherler thorsten.at.apache.org
>>> Open Source Java  consulting, training and solutions
>>>
>>>
>>> --
>>> No virus found in this incoming message.
>>> Checked by AVG.
>>> Version: 7.5.524 / Virus Database: 270.6.21/1668 - Release Date: 9/12/2008
>>> 6:56 AM
>>>   
> --
> Thorsten Scherler thorsten.at.apache.org
> Open Source Java  consulting, training and solutions
>
>   


-- 
Salutations,
Cyriaque
PCO Cyriaque DUPOIRIEUX
Consultant
Consultant //
Tel> +33 (0)5 34 60 44 13 
Mob>+33 (0)6 30 29 17 07PCO Innovation
Immeuble BUROLINES
2 ter, rue Marcel DORET
31700 BLAGNAC - France
Tel > + 33 (0)5 34 60 59 75
Fax > + 33 (0)5 34 60 44 10
http://www.pco-innovation.com <http://www.pco-innovation.com/>

CONFIDENTIALITE : Ce message et les éventuelles pièces attachées sont
confidentiels. Si vous n'êtes pas dans la liste des destinataires,
veuillez informer l'expéditeur immédiatement et ne pas divulguer le
contenu à une tierce personne, ne pas l'utiliser pour quelque raison que
ce soit, ne pas stocker ou copier l'information qu'il contient sur un
quelconque support. Tout droits réservés.
/CONFIDENTIALITY : This e-mail and any attachments are confidential and
may be privileged. If you are not a named recipient, please notify the
sender immediately and do not disclose the contents to another person,
use it for any purpose or store or copy the information in any medium.
All rights reserved. / //
P   

Pensez à l'environnement avant d'imprimer !/
Before printing, think about ENVIRONMENTAL responsibility!/

[jira] Created: (FOR-1102) Odt plugin does not manage tables correctly

[Cyriaque Dupoirieux (JIRA)]

Odt plugin does not manage tables correctly
---

 Key: FOR-1102
 URL: https://issues.apache.org/jira/browse/FOR-1102
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.odt
Affects Versions: 0.9-dev
Reporter: Cyriaque Dupoirieux
 Fix For: 0.9-dev


The intermediate format generated for tables with the Odt input plugin is 
inherited from the 
org.apache.forrest.plugin.input.odt/resources/stylesheets/common/odt_to_xhtml.xsl
 style sheet and is far from Xdoc format.
The genereted HTML page is a table because HTML tags are correct but the table 
layout is not applied.
Something like the following is generated as intermdiate format :


  




  
  

  
Jeu

  
  
Emulateur
  
  
Etat
  
  
Commentaires
  



  Ultima I


  http://sourceforge.net/projects/ultima-java/"; 
target="_blank">ultima-java


  Inachevé


  Emulateur java

  



Furthermore, if used with the pdf plugin the following error occurs :

ERROR - Ignoring property: number-columns-repeated="NaN" (No conversion 
defined NaN; property:'number-columns-repeated')
WARN - Mismatch: table-body (http://www.w3.org/1999/XSL/Format) vs. flow 
(http://www.w3.org/1999/XSL/Format)
WARN - Mismatch: table-body (http://www.w3.org/1999/XSL/Format) vs. 
page-sequence (http://www.w3.org/1999/XSL/Format)
WARN - Mismatch: table-body (http://www.w3.org/1999/XSL/Format) vs. root 
(http://www.w3.org/1999/XSL/Format)

I think it would be simple to correct this, my problem is do we have to update 
the common style sheet or is it better to correct the odt-to-forrest-xhtml.xsl ?


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Problem with pdf generation with odt entry

[Cyriaque Dupoirieux]

Hi,

   I think that there is a problem of compliance between the pdf plugin 
and the odt plugin.

   The pdf plugin does not find images with the following error :
[Fatal Error] :-1:-1: Premature end of file.
WARN - No ImageReader found for 
cocoon://accueil/openDocumentEmbeddedImages/zip-accueil.odt/file-Pictures/1078002D5F742175.jpg
ERROR - No ImageReader for this type of image 
(cocoon://accueil/openDocumentEmbeddedImages/zip-accueil.odt/file-Pictures/1078002D5F742

175.jpg)
ERROR - Image not available: 
cocoon://accueil/openDocumentEmbeddedImages/zip-accueil.odt/file-Pictures/1078002D5F742175.jpg


I am not sure where it tries to find the images, but I don't think it 
searches it in the good location...


Do I create a FOR or is it simple to solve ?

--
Salutations,
Cyriaque

Build test not working ?

[Cyriaque Dupoirieux]

Hi,

   I can't make a build clean; build; build test on my environment.
   I get the following error :

* [55/29]   [2/34]21.349s 12.0Kb  samples-b/locationmap/index.html
X [0] 
samples-b/locationmap/D:\duc\forrest\build/test_skinned_site/src/documentation/content/xdocs/rewrite.index
BROKEN: No pipeline matched request: 
samples-b/locationmap/D:\duc\forrest\build/test_skinned_site/src/documentation/content/xdocs/rewrite.index
* [58/26]   [0/0] 0.093s 8.2Kb   
samples-c/showonlywhenselected/page1.pdf


   and further the following one :

* [74/19]   [0/0] 0.032s 199b
skin/images/rc-t-l-5-1header-2tab-unselected-3tab-unselected.png
ERROR - Error with opening URL 
'http://www.google.com/logos/Logo_40wht.gif': Connection timed out: connect

ERROR - Image not available: http://www.google.com/logos/Logo_40wht.gif
* [75/18]   [0/0] 42.37s 15.8Kb  samples-b/embedded_html.pdf

   The first error seems to indicate that a pipeline has changed.
   For the second one, I am behind a proxy and the proxy is taken into 
account by the main build file, but it does not seem to be taken into 
account with the pdf plugin...


   If one of you has an idea, I can try to correct this...
--
Salutations,
Cyriaque

Re: Usage of content-author etc

[Cyriaque Dupoirieux]

le 02/04/2008 16:23 Gav a écrit :

Hi All,

I was looking at trying to finish off FOR-797

(A moving target being in the Whiteboard, some of them will need
doing again ...)

Looking at content-author.ft it simply states to put the contract
in the view somewhere.

So I added :-



..into 'pelt-html.content.panel.xml' 


Nothing shows up, looking at the source of the page
the comments are there but no content inbetween.

looking at the code of the contract, it is looking for
a div class="author" somewhere, so I added one, but still
can not see where an actual authors name is supposed to
come from or in fact where it is supposed to appear.
  
Add authors in your header : 
http://forrest.apache.org/dtdx/document-v20.dtdx.html#authors

I have converted some other contracts and work fine, as I want
to make sure all contracts work before committing, any hints
on this probably brain-dead simple one would be great :)


I also think we should create a test view, either a page or few pages
containing all these contracts so they can be tested on forrest-sample-2
- any changes elsewhere that break any of these will then be hightlighted.




Gav...


  

Re: [Dispatcher] Problem with i18n and pdf

[Cyriaque Dupoirieux]

le 08/10/2007 08:58 Sjur Moshagen a écrit :
> Hi,
>
> Den 4. okt. 2007 kl. 15.15 skrev Cyriaque Dupoirieux:
>
>> Hi,
>>
>> I don't know how to translate the hard coded strings in the
>> dispatcher fo generation.
>> I tried to translate "Table of Content" by adding a translation in
>> the
>> org.apache.forrest.plugin.internal.dispatcher/resources/stylesheets/common/translations/CommonMessages_.xml
>>
>>
>> But it does not work...
>>
>> An idea ?
>
> Yes, I have had it working for some time, but had forgot to commit it.
> Unfortunately, when i svn-up-ed before commiting the change, the pdf
> generation broke completely:
>
> Internal Server Error
> ...
> cause
> master-reference 'book' for fo:page-sequence matches no
> simple-page-master or page-sequence-master
Ho ? I have the same problem with one of my numerous files and am
currently also looking at this problem.
If I understand what's my problem, I tell you.

Salutations,
Cyriaque,

>
> I have to solve that one first.
>
> But back to the idea about the original problem:
>
> The issue is caused by there being no i18n processing defined in:
>
> plugins/org.apache.forrest.plugin.output.pdf/output.xmap
>
> Adding i18n to that file should solve it. I will commit the required
> modifications as soon as I get pdf working here again (I would like to
> verify that it works with HEAD before commiting - I haven't updated my
> svn in quite some time).
>
> Best regards,
> Sjur
>
>
>

[Dispatcher] Problem with i18n and pdf

[Cyriaque Dupoirieux]

Hi,

I don't know how to translate the hard coded strings in the
dispatcher fo generation.
I tried to translate "Table of Content" by adding a translation in
the
org.apache.forrest.plugin.internal.dispatcher/resources/stylesheets/common/translations/CommonMessages_.xml

But it does not work...

An idea ?
-- 
Salutations,
Cyriaque,

Re: [jira] Commented: (FOR-812) Remove dependency of projectInfo on skinconf.xml

[Cyriaque Dupoirieux]

le 20/07/2007 14:34 Gavin (JIRA) a écrit :
> [ 
> https://issues.apache.org/jira/browse/FOR-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514189
>  ] 
>
> Gavin commented on FOR-812:
> ---
>
> Cyriaque, is your fix suitable to be added now ?
>   
Yes it should still work even if it is one year old :-) .
Beware, we had a deep discution on this and I don't know what to think
of it now :
http://marc.theaimsgroup.com/?l=forrest-dev&w=2&r=1&q=b&s=430032)

Salutations,
Cyriaque,

>   
>> Remove dependency of projectInfo on skinconf.xml
>> 
>>
>> Key: FOR-812
>> URL: https://issues.apache.org/jira/browse/FOR-812
>> Project: Forrest
>>  Issue Type: Sub-task
>>  Components: Plugin: input.projectInfo
>>Affects Versions: 0.8
>>Reporter: Ross Gardler
>>Priority: Blocker
>> Fix For: 0.9-dev
>>
>>
>> The dispatcher will remove the file skinconf.xml. However, the projectInfo 
>> plugin uses it to get the URL for the issue tracker.
>> We should chage the projectInfo plugin so that this value is provided by a 
>> plugin property.
>> 
>
>   

Re: [Proposal] decide the future of forrestdoc

[Cyriaque Dupoirieux]

I didn't even know this tool existed.

So I can't help on this point and let you devide what is best for the
project...


Salutations,
Cyriaque,

le 11/07/2007 08:03 David Crossley a écrit :
> The Apache Forrest project needs to decide the future
> of "forrestdoc":  trunk/whiteboard/forrestdoc/
>
> When the Apache Jakarta Alexandria project became defunct,
> this code was saved and given a home at Apache Forrest.
> After some initial work, no development was done in the
> subsequent years. There was some hope that it would be
> turned into a Forrest plugin, but that has not eventuated.
> The code is not used at all by 'forrest'.
>
> See background http://issues.apache.org/jira/browse/FOR-820
>
> Recently the Apache Maven project expressed some interest [2].
> There were some murmurs by two very busy Forrest developers.
> However this did not spur the Forrest project to explore
> what to do with the code.
>
> It has no community built around it at Forrest.
>
> I am concerned that the Forrest project is too thin to be
> able to support this tool. We need to focus on our core
> and our plugins.
>
> Today Vincent provided some patches.
>
> I am very concerned that this makes an obscure part of
> Forrest whiteboard available in the Maven repositories,
> while Forrest has no other presence there. This could
> cause confusion for our main users.
>
> I propose that Forrest ask the Maven project to take the
> code as-is over to Maven JXR, then split it up as they see fit.
>
> What do other Forrest developers think?
>
> [1] http://issues.apache.org/jira/browse/FOR-820
>
> [2] Re: Forrestdoc and Maven JXR
> http://marc.info/?t=11809600927
>
>
>
>   

Re: [proposal] Dispatcher - remove xdocs location [depreciated] for structurer matches

[Cyriaque Dupoirieux]

Ok, let's start to clean up the location map.



Salutations,
Cyriaque,

le 14/06/2007 14:53 Thorsten Scherler a écrit :

Hi all,
 
since FOR-1010 was showing we need to get rid of some matching in the

locationmap of the dispatcher.

I would like to remove all matches in the locationmap that are marked as
[depreciated] for quite some time now.

salu2
  

Re: new committer and PMC member: Brian Dube

[Cyriaque Dupoirieux]

Welcome Brian as official committer and PMC member Brian.

We are glad you had accepted to continue with us - and I am sure we are going 
to make a good work all together.

Salutations,
Cyriaque,

Re: [jira] Created: (FOR-997) Can't using as "for-loop"

[Cyriaque Dupoirieux]

Hu ? Are you sure it's a Forrest Issue ?

Salutations,
Cyriaque,


le 03/05/2007 16:43 Masato Nagai (JIRA) a écrit :

Can't using  as "for-loop"


 Key: FOR-997
 URL: https://issues.apache.org/jira/browse/FOR-997
 Project: Forrest
  Issue Type: Bug
  Components: XML grammars & validation
Affects Versions: 0.8
Reporter: Masato Nagai


I would like to use following one to transform xml.

 
  


But I have error message "Can not convert #BOOLEAN to a NodeList!".



  

[jira] Commented: (FOR-612) Editing an Open Office document causes it to fail to render in dynamic environments

[Cyriaque Dupoirieux (JIRA)]

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

Cyriaque Dupoirieux commented on FOR-612:
-

Ross,

I have closed the following issues because I have no more the problems :
https://issues.apache.org/jira/browse/FOR-495
https://issues.apache.org/jira/browse/FOR-613

Maybe we can close this as well ?


> Editing an Open Office document causes it to fail to render in dynamic 
> environments
> ---
>
> Key: FOR-612
> URL: https://issues.apache.org/jira/browse/FOR-612
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6, 0.7
> Environment: "forrest run"
>Reporter: Ross Gardler
>
> When running in a dynamic environment editing an Open Office document will 
> prevent it from rendering on a page refesh. If you stop forrest and run again 
> it renders fine. I suspect this is a problem with the zip generator. An 
> alternative approach to reading the OOo source is provided in the 
> SXWGenerator found in the Resume plugin. This generator should be moved to 
> the OOo plugin and this issue tested.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (FOR-495) Problem with Cocoon cache when regenerating *.sxw sources

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyriaque Dupoirieux closed FOR-495.
---

Resolution: Cannot Reproduce

> Problem with Cocoon cache when regenerating *.sxw sources
> -
>
> Key: FOR-495
> URL: https://issues.apache.org/jira/browse/FOR-495
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.7
> Environment: Any
>Reporter: Cyriaque Dupoirieux
>
> Modification of sxw sources are not taken into account if you do not delete 
> the cocoon cache.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (FOR-613) Updated OOo document not taken into account in static generation

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyriaque Dupoirieux closed FOR-613.
---

Resolution: Cannot Reproduce

> Updated OOo document not taken into account in static generation
> 
>
> Key: FOR-613
> URL: https://issues.apache.org/jira/browse/FOR-613
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.8
> Environment: Any
>Reporter: Cyriaque Dupoirieux
>
> I realise that I need to delete the cocoon cache to regenerate page which 
> sources are in sxw format.
> If I don't do this, modifications are never taken into account...
> (The cache problem is just my opinion...)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Skin plugin

[Cyriaque Dupoirieux]

le 23/04/2007 06:01 David Crossley a écrit :

Brian M Dube wrote:
  

Is anyone working on moving skins to a plugin? I'm going to have a go at it.



Fantastic. Yes we have talked about this before.

Thank heaven that we documented this. I was very pleased
to see http://forrest.apache.org/docs/dev/status-themes.html
where we talk about a future framework to enable any
"theme engine". We even link to a mail discussion.
I still need to re-read that.

Moving the skins functionality out is one aspect
of cleaning up the core.

So i hope that various developers can help with this.
It is in everyone's interest, even if they don't
want to use skins. We need to slim our core.
  

Exact,

I am not yet clear about your main aim. Is it to move
the existing functionality out of the core and leave it
at that (a legacy system)? Or is it to create a framework
as described above which would enable future development
of skins functionality as well as dispatcher.
  

I think you are talking about the two steps we need to climb.
First let's extract skin functionnality into a plugin and then it will 
be clearer in our mind to create the framework.

I would be keen to help with either.

I am also trying to gauge whether there is community
inclination to support further skins development.
  
I will not help on skin development any more - but I will help on the 
extraction of the core !


  
I'm thinking of emulating the dispatcher to have a plugin for skin 
functionality and a plugin to house the skins. This also got me thinking 
about a separate plugin for each skin.



I like the idea about a separate plugin for the
skins functionality. Not sure yet what would go there.
I presume this would be the "skinit" pipelines from
the main/webapp/*.xmap sitemaps. These have become rather
complex and might need to be re-written.

Not sure what to do about the different skins.
There would be a similar discussion in the archives about
when the Dispatcher work established the f.a.o.themes.core
plugin.

Would there be equivalent to the current skins/common/ ?
  

I think that the way the dispatcher has been implemented can help :
One plugin is the core - org.apache.forrest.plugin.internal.dispatcher,
And one houses the different look and feel - org.apache.forrest.themes.core
(Which at the moment contains three themes : common, pelt and coat)

The skin should OMHO have the same architecture :
One plugin for the generation and one plugin with all skins just like 
dispatcher themes.


  

Thoughts?



Here are some more quick thoughts ...

Let us continue to express our needs for a little
while on this dev list, before launching into the
actual development.

There is some of the current skins stuff that can be
re-used, while some aspects might need to be re-designed.

Perhaps the first version would just move the existing stuff.

I am not clear about the best approach. If we need
to change some of the way skins work, then should we
make a clean implementation and create a new skin that
closely resembles the default "pelt" skin? We have warned
people to be careful about creating their own skins.
Are we able to support older style skins? On the other hand
perhaps the existing functionality is fine to create a new
skins framework via plugins.
  
Ok, just to finish, this work must be planned in Jira to be able to 
breakdown the work.
Some issues may be used and grouped in a roadmap - if we change the some 
titles.

Here are some I have found, maybe I missed some others :

https://issues.apache.org/jira/browse/FOR-808
https://issues.apache.org/jira/browse/FOR-809
https://issues.apache.org/jira/browse/FOR-987

Salutations,
Cyriaque,


-David


  

Re: svn commit: r530712 - in /forrest/trunk/site-author/content/xdocs: docs_0_80/howto/howto-buildPlugin.xml docs_0_90/howto/howto-buildPlugin.xml

[Cyriaque Dupoirieux]

le 23/04/2007 07:04 David Crossley a écrit :

As i explained in another email last week. We only update the
version of the document in the docs_0_90 and not the old stuff.

-David

  

Ok,

(but it is not a new feature I have documented, but an old one that 
should have been before...)


I will not do it again :-[ ,

Salutations,
Cyriaque,

Author: cdupoirieux
Date: Fri Apr 20 02:23:42 2007
New Revision: 530712

URL: http://svn.apache.org/viewvc?view=rev&rev=530712
Log:
Tiles are Panels now (FOR-975)

Modified:

forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml

forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml

Modified: 
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
URL: 
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml?view=diff&rev=530712&r1=530711&r2=530712
==
--- 
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml 
(original)
+++ 
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml 
Fri Apr 20 02:23:42 2007
@@ -476,7 +476,7 @@
   defining the contents and look and feel of a site.
 
 
-  Plugins can expose contracts, resources and tiles for use in
+  Plugins can expose contracts, resources and panels for use in
   structurer files used within Dispatcher-based sites. In order to do
   this you should develop your contracts as normal and place them in
   PLUGIN_HOME/resources/themes. However, this, by itself,
@@ -498,10 +498,10 @@
 
   
 
-
+
   
-
-
+
+
   
 ]]>
 

Modified: 
forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml
URL: 
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml?view=diff&rev=530712&r1=530711&r2=530712
==
--- 
forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml 
(original)
+++ 
forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml 
Fri Apr 20 02:23:42 2007
@@ -476,7 +476,7 @@
   defining the contents and look and feel of a site.
 
 
-  Plugins can expose contracts, resources and tiles for use in
+  Plugins can expose contracts, resources and panels for use in
   structurer files used within Dispatcher-based sites. In order to do
   this you should develop your contracts as normal and place them in
   PLUGIN_HOME/resources/themes. However, this, by itself,
@@ -498,10 +498,10 @@
 
   
 
-
+
   
-
-
+
+
   
 ]]>
 






  

Re: [Announce] Apache Forrest 0.8

[Cyriaque Dupoirieux]

le 18/04/2007 13:15 David Crossley a écrit :

Thorsten Scherler wrote:
  

Ross Gardler wrote:


[APPLAUSE]

Well done everyone.

*Especially* David
  

Yeah, thanks everyone and praise to the RM.



Thanks for the thanks, and thanks to everyone else.

-David


  

This is the first Release I am PMC, Youpi !
Thanks everyone,

Salutations
Cyriaque,

[jira] Commented: (FOR-984) Forrest doesn't work properly with Sun's JDK 1.6

[Cyriaque Dupoirieux (JIRA)]

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

Cyriaque Dupoirieux commented on FOR-984:
-

I have the following warning (build.sh) with the java 1.5.0_11 on Mandriva 
Linux Free 2007 :

init:

  --

  Using Apache Ant version 1.6.5 compiled on May 16 2006
  Build file /home/windchill/Desktop/forrest/main/build.xml
  Use 'build.[sh|bat] -projecthelp' to see other options.
  Build system home /home/windchill/Desktop/forrest/tools/ant
  Build number 1
  Project Name Forrest build file
  Java Version 1.5  
  Timestamp 200704170207
  This is: apache-forrest 0.8

  --


compile:
Created dir: /home/windchill/Desktop/forrest/build/classes
Compiling 32 source files to /home/windchill/Desktop/forrest/build/classes
/home/windchill/Desktop/forrest/main/java/org/apache/forrest/locationmap/lm/LocationMap.java:256:
 warning: [deprecation] 
compose(java.lang.Object,org.apache.avalon.framework.component.ComponentManager)
 in org.apache.avalon.framework.container.ContainerUtil has been deprecated
ContainerUtil.compose(context, new WrapperComponentManager(m_manager));
 ^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning

I think this may help, some APIs are deprecated in the 1.5 so they should not 
be used with 1.6...


> Forrest doesn't work properly with Sun's JDK 1.6
> 
>
> Key: FOR-984
> URL: https://issues.apache.org/jira/browse/FOR-984
> Project: Forrest
>  Issue Type: Improvement
>  Components: Core operations, Launch 'forrest'
>Affects Versions: 0.8-dev, 0.9
>Reporter: Schumarer
> Fix For: 0.9
>
> Attachments: log.txt
>
>
> Hi, 
> This problem is quite easy to reproduce. First, install Sun's JDK 1.6 
> (whatever version until 1.6.0_01-b06 ) define your %JAVA_HOME% on that JDK.
> When you seed a new projet, there is no problem and it works. 
> When you do a "forrest run", it works too, but when you do a "forrest" it 
> doesn't work anymore. I'll try to attach a full log.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [Vote] please vote for the release using RC2

[Cyriaque Dupoirieux]

My test results of the RC2...

My first configuration :

java -version
 java version "1.4.2_08"
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
 Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)

System
 Windows XP Professional
 Version 2002 Service Pack 2

Everything seems Ok : build test and my own site were fully generated.

My second configuration :
==
java -version
 java version "1.5.0_11"
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
 Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)

System
   Mandriva Linux 2007 Free
   Linux 2.6.17-5mdv #1 SMP Wed Sep 13 14:32:31 EDT 2006 i686 
Intel(R) Pentium(R) 4 CPU 3.00GHz GNU/Linux

   under Gnome 2.16

Everything seems Ok : build test and my own site were fully generated.



So I vote +1 :-) .


Salutations,
Cyriaque,


So my decision is that we will stick with RC2.

-David


  

Re: Welcome to Apche Forrest as part of GSoC

[Cyriaque Dupoirieux]

le 16/04/2007 14:54 Schumarer a écrit :



> It would be *really* helpful if you could start writing a FAQ about
> getting started as a Forrest developer (perhaps your first question
> would be how - or perhaps you can find it in our docs, it is
there ;-)


Hi,
(whispering) I wanted to ask that question but I was so shy that I 
didn't dare to. Now, you just lead me the way.(whispering)

Hi, please dare,


Are you (developers) using an IDE to develop Forrest? How do you test 
that your feature is working? Which langage?
I don't use any IDE, I use simple text editors - such like Gvim under 
Windows and vi - yes indeed - under Linux.
To compile, test... I only use command lines - and sometimes, some 
scripts which automates what I often do...


Salutations,
Cyriaque,
(BTW, I am french on so are my systems...)



Does any Forrest source editor exist or we have to use our own xml 
editor ?


I've got a lot of questions about forrest but as I'm a new user i dare 
not ask them


Thx

 


>
> Finally, you are here to enjoy yourselves, so have fun!
>
> Ross and Gavin
> GSoC Mentors for Apache Forrest
>

Re: [Poll] your interest in plugins to be deployed

[Cyriaque Dupoirieux]

Gav a écrit :
  

-Original Message-
From: David Crossley [mailto:[EMAIL PROTECTED]
Sent: Thursday, 12 April 2007 12:10 PM
To: [EMAIL PROTECTED]
Subject: Re: [Poll] your interest in plugins to be deployed

Oh, while doing that if you can dream up any new
plugins that might be useful, then please create
an issue in our Jira Issue tracker.
http://forrest.apache.org/issues.html

Use these settings ...
  Component: Plugins: Potential new
  Type: New Feature

-David



Just wanted to bounce this one around before creating an issue.

I would like a mySQL plugin, I see we have a database plugin, but has no
mySQL functionality. Can this be extended, so the database plugin has
options so you choose or configure which database to use, or would a
separate plugin for each type be better?

I would also like PHP input and output functionality. I can't see any other
way of doing it, PHP code as input (in an .xml file?) and the PHP enabled
file must be .php extension of course to be parsed server-side. Thoughts
on a plugin for this?
  
Don't need a plugin to do this, just add a match in your sitemap.xmap 
such like :


   
 
 


And use in the source the process-instruction tags to integrate your php 
code in the file :




HTH,
Salutations,
Cyriaque,


Immediate use case for both would be a login facility, use PHP to interact
with mySQL database.

Gav...

  

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.26/748 - Release Date: 4/5/2007
3:33 PM




  

Re: the progress with the release

[Cyriaque Dupoirieux]

David Crossley a écrit :

Keeping this "progress" thread happening ...

We fixed some quite serious problems with the
deployment of plugins. Thanks to those who helped
with the testing and fixing.

So far we do not need another release candidate.

People are still encouraged to test on sites that
have more complex needs.

If there are whiteboard plugins thyat you want
to be deployed up-to-date, then don't forget to ask.

-David


  

My results...

My configuration :

java -version
  java version "1.4.2_08"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
  Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)

System
  Windows XP Professional
  Version 2002 Service Pack 2

Forrest Bar :
=
The forrest bar of our site is not the latest one.

Proxy configuration :
==
I forgot to configure my proxy host and port.
The build test apparently worked, both sites Skinned and Dispatcher were 
generated and only the pdf plugin was in the build/plugins directory.

After a recursive diff, I can tell you this :
Both sites are identical but the following files :

  * forrest.properties
  * .\build\tmp\pluginlist2fetchbuild.xml
  * .\build\tmp\projfilters.properties
  * .\build\tmp\cocoon-work\cache-dir\cocoon-ehcache-1.data
  * .\build\tmp\cocoon-work\cache-dir\cocoon-ehcache-1.index
  * .\build\webapp\WEB-INF\logs\core.log
  * .\build\webapp\WEB-INF\logs\error.log

After proxy configuration, I had no problem with forrest test (skinned 
site and dispatcher site)

For my personal site, the Odt plugin is not found (need to be deployed ?)


I will check under Mandriva Linux 2007 when I have time...

Regards,
Cyriaque,

Re: calling all developers, test release candidate

[Cyriaque Dupoirieux]

le 12/04/2007 16:17 Ross Gardler a écrit :

schumarer schumarer wrote:

Well,

I've been testing (basic tests) forrest for the last hour and 
everything works fine on my Windows plateform with Service Pack2.

Sun's JDK 1.4.2_14
Sun's JDK 1.5.0_11

With these 2 versions of java, everything is ok :-)


Thanks for the report. This is really useful

Yes indeed,



But when I use Sun's JDK 1.6.0, I get this error :


This is even more useful.

Do we need to fix this or shall we release with a "does not work in 
JDK 1.6.0" warning?


Note, after this release I am going to propose a rapid release cycle 
and David hinted at such when we started on this approach. With that 
in mind I propose we release with this known limitation. What do 
others think.

I am Ok for both : rapid release and add a warning...

Salutations,
Cyriaque,


Ross

[jira] Created: (FOR-980) RSS - Current_changes rss shows the whole changes.rss

[Cyriaque Dupoirieux (JIRA)]

RSS - Current_changes rss shows the whole changes.rss
-

 Key: FOR-980
 URL: https://issues.apache.org/jira/browse/FOR-980
 Project: Forrest
  Issue Type: Improvement
  Components: Plugin: input.projectInfo
Affects Versions: 0.8-dev
Reporter: Cyriaque Dupoirieux
Priority: Minor
 Fix For: 0.9


The current_changes pages shows the changes.rss file.
It should display a specific current_changes.rss...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (FOR-979) RSS - Description starts with the title, which makes unnecessary repeatitions

[Cyriaque Dupoirieux (JIRA)]

RSS - Description starts with the title, which makes unnecessary repeatitions
-

 Key: FOR-979
 URL: https://issues.apache.org/jira/browse/FOR-979
 Project: Forrest
  Issue Type: Improvement
  Components: Plugin: input.projectInfo
Affects Versions: 0.8-dev
Reporter: Cyriaque Dupoirieux
Priority: Minor
 Fix For: 0.9


The description of an item repeats the title which take lot a place in small 
frames (with aggregators such as Netvibes or Bloglines...)
ex : 
Dispatcher improvment
Dispatcher improvment by CD : Big work on...


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (FOR-978) RSS should use url instead of relative path (Problem with site such as Netvibes)

[Cyriaque Dupoirieux (JIRA)]

RSS should use url instead of relative path (Problem with site such as Netvibes)


 Key: FOR-978
 URL: https://issues.apache.org/jira/browse/FOR-978
 Project: Forrest
  Issue Type: Bug
  Components: Plugin: input.projectInfo
Affects Versions: 0.8-dev
Reporter: Cyriaque Dupoirieux
 Fix For: 0.9


When you try to integrate the rss of Forrest Changes 
(http://forrest.apache.org/docs_0_80/changes.rss) in your Netvibes account, the 
links are not correct because relative to the site.
Full Url should be better.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (FOR-742) trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyriaque Dupoirieux reassigned FOR-742:
---

Assignee: (was: Cyriaque Dupoirieux)

> trouble accessing unversioned plugin for a released version of Forrest, e.g. 
> projectInfo
> 
>
> Key: FOR-742
> URL: https://issues.apache.org/jira/browse/FOR-742
> Project: Forrest
>  Issue Type: Bug
>  Components: Plugins (general issues)
>Affects Versions: 0.7, 0.8-dev
>Reporter: David Crossley
>Priority: Critical
> Fix For: 0.8-dev
>
>
> The plugin retrieval and deployment process are not quite correct. Recently 
> the projectInfo plugin had its version number incremented and the 
> "unversioned" plugin now relates specifically to 0.8-dev version. That 
> prevents 0.7 from accessing the relevant plugin.
> The solution is discussed here:
> http://marc.theaimsgroup.com/?t=11317632832

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (FOR-962) Wrong port used in ForrestBar if none standard forrest port used

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyriaque Dupoirieux reassigned FOR-962:
---

Assignee: (was: Cyriaque Dupoirieux)

I have just added an Option window to be able to specifiy the host (default is 
localhost) and the port (default is ) of "Forrest run" and saved - if 
needed - in the user preferences.
The solution is more robust - cf. the old javascript function isLocalUrl() 
where the host and port were hard coded...
Ross has thought of a solution much more simple based on a Regexp of the 
current Url to find the host and port.
My dilemma was that some installations (mine for instance) have several web 
server running at the same time (I always have an apache for Oracle on port 
8080...) So I wanted a solution flexible and independant.
I don't know what to say, but now, the forrest bar has an Option window ready 
for future features and it may be a good thing ;-)

> Wrong port used in ForrestBar if none standard forrest port used
> 
>
> Key: FOR-962
> URL: https://issues.apache.org/jira/browse/FOR-962
> Project: Forrest
>  Issue Type: Bug
>  Components: Dispatcher (aka views), Tool: Forrestbar
>Affects Versions: 0.8-dev
>Reporter: Ross Gardler
>Priority: Minor
>
> If Forrest is run on a port other than , the forrestbar fails to pick 
> this up from the request URI.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (FOR-635) images not reproduced in PDFs, if sources are in xdocs/images directory

[Cyriaque Dupoirieux]

le 28/03/2007 11:25 Ross Gardler a écrit :

Ross Gardler wrote:

Cyriaque Dupoirieux wrote:
(I think we will have lots of problems with input plugins such as 
Odt...)


I only just realised the implications of this sentence. There should 
be *no* problems with input plugins, it is the above issue is a 
special case that results from the fact that FOP insists on having 
absolute addresses. It is an output plugin issue, not an input plugin.


The OOo input plugin works just fine (at least last time I checked), 
so there is no reason why the Odt plugin should not work.
Ok, I was just wandering about the need of fullpath in fo file for 
pictures. Which src path are we going to give, since the picture is not 
directly available in the sources.
But let's see what happens, I have several page written in Odt in my 
site (made with the dispatcher) I am going to test myself.


Thank you,

Salutations,
Cyriaque,



Raise this with me after the 0.8 release if you like.

Ross

[jira] Work stopped: (FOR-962) Wrong port used in ForrestBar if none standard forrest port used

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on FOR-962 stopped by Cyriaque Dupoirieux.

> Wrong port used in ForrestBar if none standard forrest port used
> 
>
> Key: FOR-962
> URL: https://issues.apache.org/jira/browse/FOR-962
> Project: Forrest
>  Issue Type: Bug
>  Components: Dispatcher (aka views), Tool: Forrestbar
>Affects Versions: 0.8-dev
>Reporter: Ross Gardler
> Assigned To: Cyriaque Dupoirieux
>Priority: Minor
>
> If Forrest is run on a port other than , the forrestbar fails to pick 
> this up from the request URI.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (FOR-635) images not reproduced in PDFs, if sources are in xdocs/images directory

[Cyriaque Dupoirieux]

Did you commit your changes ?
I want to make it work also with dispatcher, thanks.
(I think we will have lots of problems with input plugins such as Odt...)


Salutations,
Cyriaque,

le 27/03/2007 21:53 Ross Gardler (JIRA) a écrit :
[ https://issues.apache.org/jira/browse/FOR-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484567 ] 


Ross Gardler commented on FOR-635:
--

OK, some success and some failure.

The good news:

I've made a change that means samples 1,2, 4, 5, 6 in group 1 and sample 3 in 
group 2 now works in both run and site modes

The bad news:

There is no way to make the remaining images work. However, this must have 
always been the case since the problem is very deep rooted in the way the FO 
XSLT calculates the path to images and the way some images are generated 
dynamically.

I propose we now document this limitations and move this to 0.9.

  

images not reproduced in PDFs, if sources are in xdocs/images directory
---

Key: FOR-635
URL: https://issues.apache.org/jira/browse/FOR-635
Project: Forrest
 Issue Type: Bug
 Components: Documentation and website
   Affects Versions: 0.7, 0.8-dev
   Reporter: David Crossley
   Priority: Minor
Fix For: 0.8-dev

Attachments: fo.diff


We used to enable images to be placed in the xdocs/images directory. However, 
now they are intended to go in the resources/images directory instead. Both 
methods will work for html pages, but  only the latter method for the PDF pages.



  

Re: [Vote] Release Plan for Forrest 0.80

[Cyriaque Dupoirieux]

+1,
(I am sure more versions will bring us more users and devs...)

Salutations,
Cyriaque,

le 27/03/2007 12:10 Ross Gardler a écrit :

David Crossley wrote:

Another reason is to draw attention to it and get as
many people involved as possible, including developers.


+1 with the correction David made later in this thread.

Ross

Re: svn commit: r521779 - in /forrest/trunk/tools/forrestbar/xpi: chrome/content/contents.rdf chrome/content/forrestbarOverlay.js chrome/content/forrestbarOverlay.xul chrome/content/forrestbarSettings

[Cyriaque Dupoirieux]

Ross,

Do you want I rollback my commit ?
In that case, can you explain me the problem you have (I mean, when does 
the forrest bar loose the port ?)



Salutations,
Cyriaque,

le 26/03/2007 12:13 Ross Gardler a écrit :

Cyriaque Dupoirieux wrote:

le 25/03/2007 01:26 Ross Gardler a écrit :

Cyriaque Dupoirieux wrote:

Ross,

   If you think this commit correct the FOR-962 - 
https://issues.apache.org/jira/browse/FOR-962 -, just tell me and 
I'll close it.


I've not tested it, but it looks like an OK workaround.

You are cruel with me to say I have just made a workaround ;-) .


However, I wonder if we need to set a property for this. The port 
number is in the URL of the currently viewed page, can't we just 
extract it?

Ok, my concerns are :

   * What can be the first access to "Forrest run" if we don't have
 properties to define the host and the port ?


The first access will almost never be a request for one of the 
internal dispatcher files, if it is we can simply throw up a box 
asking for the port (or just an error saying go to the index page first).




   * How to be sure the current Url is a "forrest run" Url. You may
 have several local ports which are not for forrest.


That is not a problem introduced by this requirement. The URL for 
dispatcher menu stuff is already derived from the browser URL, e.g. 
click on "dispatcher-dev -> structurer".


Ross

Re: svn commit: r521779 - in /forrest/trunk/tools/forrestbar/xpi: chrome/content/contents.rdf chrome/content/forrestbarOverlay.js chrome/content/forrestbarOverlay.xul chrome/content/forrestbarSettings

[Cyriaque Dupoirieux]

le 25/03/2007 01:26 Ross Gardler a écrit :

Cyriaque Dupoirieux wrote:

Ross,

   If you think this commit correct the FOR-962 - 
https://issues.apache.org/jira/browse/FOR-962 -, just tell me and 
I'll close it.


I've not tested it, but it looks like an OK workaround.

You are cruel with me to say I have just made a workaround ;-) .


However, I wonder if we need to set a property for this. The port 
number is in the URL of the currently viewed page, can't we just 
extract it?

Ok, my concerns are :

   * What can be the first access to "Forrest run" if we don't have
 properties to define the host and the port ?
   * How to be sure the current Url is a "forrest run" Url. You may
 have several local ports which are not for forrest.
 o Several options in Dev. menu make a test to check the action
   is available (display the toc, the body of the current page...)


Salutations,
Cyriaque,


Ross

Re: svn commit: r521779 - in /forrest/trunk/tools/forrestbar/xpi: chrome/content/contents.rdf chrome/content/forrestbarOverlay.js chrome/content/forrestbarOverlay.xul chrome/content/forrestbarSettings

[Cyriaque Dupoirieux]

  var Url= "http://"; + getLocalWebServer() + "/" ;
+  return Url;
+}
+
+/* - */
+/* Options functions */
+/* - */
+
+/* Getting preferences */
+function getForrestRunHost()
+{
+  var prefservice = 
Components.classes["@mozilla.org/preferences-service;1"].getService(Components.interfaces.nsIPrefService);
+  var prefs = prefservice.getBranch("");
+
+  var forrestHost = null;
+  if (prefs.getPrefType("forrestbar.run.host") == prefs.PREF_STRING)
+  {
+forrestHost = prefs.getCharPref("forrestbar.run.host");
+  }
+  if ((forrestHost == null) || (forrestHost.length = 0))
+  {
+ forrestHost='localhost';
+  }
+  return forrestHost;
+}
+
+function getForrestRunPort()
+{
+  var prefservice = 
Components.classes["@mozilla.org/preferences-service;1"].getService(Components.interfaces.nsIPrefService);
+  var prefs = prefservice.getBranch("");
+
+  var forrestPort = null;
+  if (prefs.getPrefType("forrestbar.run.port") == prefs.PREF_STRING)
+  {
+forrestPort = prefs.getCharPref("forrestbar.run.port");
+  }
+  if ((forrestPort == null) || (forrestPort.length = 0))
+  {
+ forrestPort='';
+  }
+  return forrestPort;
+}
+
+/* Initialising Options Panel */
+function initForrestBarOptions()
+{
+  document.getElementById('forrestbar.run.host').value = getForrestRunHost();
+  document.getElementById('forrestbar.run.port').value = getForrestRunPort();
+}
+
+/* recording Options in prefs */
+function setForrestBarOptions()
+{
+  var prefService = Components.classes["@mozilla.org/preferences-service;1"]
+.getService(Components.interfaces.nsIPrefService);
+  var prefs = prefService.getBranch("");
+
+  var oldHost=getForrestRunHost();
+  var oldPort=getForrestRunPort();
+  var newHost=document.getElementById('forrestbar.run.host').value;
+  var newPort=document.getElementById('forrestbar.run.port').value;
+  var change=false;
+
+  if( oldHost != newHost )
+  {
+change=true;
+prefs.setCharPref("forrestbar.run.host", newHost);
+  }
+  if( oldPort != newPort )
+  {
+change=true;
+prefs.setCharPref("forrestbar.run.port", newPort);
+  }
+  if( change )
+alert("Warning! the label of the Local Forrest item will be refreshed at the 
next start of your browser...");
+
+  window.close();
+}
+

Modified: 
forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarOverlay.xul
URL: 
http://svn.apache.org/viewvc/forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarOverlay.xul?view=diff&rev=521779&r1=521778&r2=521779
==
--- forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarOverlay.xul 
(original)
+++ forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarOverlay.xul Fri 
Mar 23 08:48:03 2007
@@ -35,10 +35,7 @@
   http://forrest.apache.org/docs/dev/');" />
   http://forrest.zones.apache.org/');" />
   
-  http://localhost:/');" hidden="false" />
-  http://127.0.0.1:/');" hidden="false" />
-  
-  http://127.0.0.1:8080/');" hidden="false" />
+  
 
   
 


Added: forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarSettings.xul
URL: 
http://svn.apache.org/viewvc/forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarSettings.xul?view=auto&rev=521779
==
--- forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarSettings.xul 
(added)
+++ forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarSettings.xul 
Fri Mar 23 08:48:03 2007
@@ -0,0 +1,65 @@
+ 
+
+
+
+
+http://www.w3.org/1999/xhtml";
+  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
+  xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul";
+  onload="initForrestBarOptions();"
+  ondialogaccept="setForrestBarOptions();"
+  title="Forrest Bar Options">
+
+  
+
+  
+
+  
+
+ 
+

+  
+
+
+  
+  Indicate here the name of the host runing Forrest 
Run.
+   
+

+   
+  
+
+
+  
+
+  
+ 
+
++  pref="true"

+  preftype="string"
+  prefstring="forrestbar.run.port"
+  size="15"
+/> 
+  

+   
+
+  
+    
+  
+
+

Propchange: 
forrest/trunk/tools/forrestbar/xpi/chrome/content/forrestbarSettings.xul

[jira] Work started: (FOR-962) Wrong port used in ForrestBar if none standard forrest port used

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on FOR-962 started by Cyriaque Dupoirieux.

> Wrong port used in ForrestBar if none standard forrest port used
> 
>
> Key: FOR-962
> URL: https://issues.apache.org/jira/browse/FOR-962
> Project: Forrest
>  Issue Type: Bug
>  Components: Dispatcher (aka views), Tool: Forrestbar
>Affects Versions: 0.8-dev
>Reporter: Ross Gardler
> Assigned To: Cyriaque Dupoirieux
>Priority: Minor
>
> If Forrest is run on a port other than , the forrestbar fails to pick 
> this up from the request URI.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (FOR-962) Wrong port used in ForrestBar if none standard forrest port used

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyriaque Dupoirieux reassigned FOR-962:
---

Assignee: Cyriaque Dupoirieux

> Wrong port used in ForrestBar if none standard forrest port used
> 
>
> Key: FOR-962
> URL: https://issues.apache.org/jira/browse/FOR-962
> Project: Forrest
>  Issue Type: Bug
>  Components: Dispatcher (aka views), Tool: Forrestbar
>Affects Versions: 0.8-dev
>Reporter: Ross Gardler
> Assigned To: Cyriaque Dupoirieux
>Priority: Minor
>
> If Forrest is run on a port other than , the forrestbar fails to pick 
> this up from the request URI.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Updated: (FOR-767) Forrestbot webapp reports succesful even when there are broken links

[Cyriaque Dupoirieux]

I don't use this...

Salutations,
Cyriaque,


le 22/03/2007 16:59 Ross Gardler (JIRA) a écrit :

 [ 
https://issues.apache.org/jira/browse/FOR-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ross Gardler updated FOR-767:
-

Fix Version/s: (was: 0.8-dev)

Does anyone actually use this webapp. It is archaic, clunky and buggy (it does 
work though).

If I'm the only one using it then I'm happy with this bug slipping to a later 
release (or even goging away completely with a better forrestbot webapp 
implementation)

  

Forrestbot webapp reports succesful even when there are broken links


Key: FOR-767
URL: https://issues.apache.org/jira/browse/FOR-767
Project: Forrest
 Issue Type: Bug
 Components: Tool: Forrestbot
   Affects Versions: 0.8-dev
   Reporter: Ross Gardler
   Priority: Minor

We should also report why it failed:
- plugin problem
- broken link (with a link to the broken links file)
- ??



  

[jira] Commented: (FOR-809) Remove build targets around "skins"

[Cyriaque Dupoirieux (JIRA)]

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

Cyriaque Dupoirieux commented on FOR-809:
-

Generally, we should put the skin generation in a plugin just like the 
dispatcher.
There are not only some skin oriented targets (targets/skins.xml) to remove 
from the core, but also :
 - the skin directory,
 - the specific location maps in webapps (locationmap-skinconf.xml, 
locationmap-skins.xml...)
 - and certainly other files I forget.

> Remove build targets around "skins"
> ---
>
> Key: FOR-809
> URL: https://issues.apache.org/jira/browse/FOR-809
> Project: Forrest
>  Issue Type: Sub-task
>  Components: Core operations, Dispatcher (aka views), Skins (general 
> issues)
>Reporter: Thorsten Scherler
>Priority: Minor
>
> We need to remove some targets that we now use for skins for the dispatcher.
> from forrest site:
> check-skin:
> ...
> fetch-skins-descriptors:
> fetch-skin:
> unpack-skins:
> init-skins:
> ...
> -validate-skinconf:
> 1 file(s) have been successfully validated.
> ...validated skinconf
> validate-skins-stylesheets:
> validate-skins:
> validate-skinchoice:
> ...validated existence of skin 'pelt'
> Created dir: 
> /home/thorsten/src/apache/forrest-trunk/main/template-sites/v2/build/site/skin/images
> Copying 23 files to 
> /home/thorsten/src/apache/forrest-trunk/main/template-sites/v2/build/site/skin/images
> Copying 14 files to 
> /home/thorsten/src/apache/forrest-trunk/main/template-sites/v2/build/site/skin/images
> Copying project skin images to site ...
> Warning: 
> /home/thorsten/src/apache/forrest-trunk/main/template-sites/v2/src/documentation/skins/common/images
>  not found.
> Warning: 
> /home/thorsten/src/apache/forrest-trunk/main/template-sites/v2/src/documentation/skins/pelt/images
>  not found.
> Copying main skin css and js files to site ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (FOR-968) Embbed the Faq generation into a plugin instead of the core

[Cyriaque Dupoirieux (JIRA)]

Embbed the Faq generation into a plugin instead of the core
---

 Key: FOR-968
 URL: https://issues.apache.org/jira/browse/FOR-968
 Project: Forrest
  Issue Type: Improvement
  Components: Core operations, Plugins: Potential new
Reporter: Cyriaque Dupoirieux
Priority: Minor
 Fix For: 0.9




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Closed: (FOR-726) use locationmap in all of the plugins

[Cyriaque Dupoirieux]

le 22/03/2007 02:21 Ross Gardler (JIRA) a écrit :

 [ 
https://issues.apache.org/jira/browse/FOR-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ross Gardler closed FOR-726.


Resolution: Fixed
  Assignee: Ross Gardler

I see no reason why this issue was re-opened. The comment says:

"Still need to verify the version numbers in each plugin's build.xml (some use a 
-dev and some do not) and in plugins.xml"

I've looked over both plugins.xml, whiteboard-plugins.xml and all plugin 
build.xml files I see no incorrect version numbers. I guess these have been 
fixed gradually over time rather than specifically as part of this issue.
  

I can't find the s5 plugin ?

Salutations,
Cyriaque,
  

use locationmap in all of the plugins
-

Key: FOR-726
URL: https://issues.apache.org/jira/browse/FOR-726
Project: Forrest
 Issue Type: Sub-task
 Components: Locationmap
   Affects Versions: 0.8-dev
   Reporter: David Crossley
Assigned To: Ross Gardler
Fix For: 0.8-dev


Each plugin has sitemaps that need to use the locationmap.
(Perhaps we need Jira sub-tasks for each plugin.)



  

Re: Use Cases in projectInfo plugin

[Cyriaque Dupoirieux]

le 21/03/2007 17:40 Ross Gardler a écrit :
Some time ago I added some use case functionality to the projectInfo 
plugin. Like the DOAP stuff this should really have gone into a new 
plugin.


The projectInfo plugin has never been released with this functionality.

I therefore propose to extract the use case stuff into a new input 
plugin in whiteboard.


Lazy consensus is in operation.
Ok, BTW why the don't we do the same for the faq which are still in the 
core ?



Salutations,
Cyriaque,



Ross

Re: svn commit: r520650 - in /forrest/trunk/whiteboard/plugins: org.apache.forrest.plugin.input.doap/ org.apache.forrest.plugin.internal.dispatcher/ org.apache.forrest.plugin.output.solr/ org.apache.f

[Cyriaque Dupoirieux]

le 21/03/2007 11:09 Thorsten Scherler a écrit :

Hmm, since we decided to change the name of tiles to panels (see the
thread on dev) I did expect that this commit would have addressed this
issue as well.

Let me explain why the commit is not really how we want it.

On Tue, 2007-03-20 at 15:50 +, Ross Gardler wrote: 
  

Why is common-fo.vt.xml in html directory rather than the fo directory?



This should go into the "panels" directory of the theme directory since
it is an "old" tiles.

Panels do not care which contracts they contain. Meaning that for
internal processing in the dispatcher pelt-css.vt.xml will not be
treated different then common-fo.vt.xml. 


The fo/css in the naming only shows which aggregation of contract and
hook (in short panel) are addressed.

Panels do not belong in the html nor in the fo nor in css nor in 
directory but in a directory on its on like e.g.
themes/pelt/panels
themes/common/panels
  
Humm, I agree with the definition of panels and with the fact that vt 
should be changed.
I don't see the benefit to store them in a specific directory, because I 
have no example where a panel can be used for two different formats.
Why don't we name them with the .panel extension and store them in the 
format directory ?
If we look at the css common directory we have a mix of different kind 
of files :

theme/common/css
 |-- basic.css   (a real source file to be used 
as it is)

 |-- branding-generic-css.ft  (a contract...)
 |-- ...
 |-- profiling.css.xslt (a stylesheet - which I'm not 
sure is very useful...)

 |-- ...

It doesn't strike me to have panels in there :
 |-- common.panel

Salutations,
Cyriaque,


salu2

On Wed, 2007-03-21 at 10:49 +0100, Cyriaque Dupoirieux wrote:
  

le 21/03/2007 10:31 Ross Gardler a écrit :


Cyriaque Dupoirieux wrote:
  

le 21/03/2007 00:17 [EMAIL PROTECTED] a écrit :


Author: rgardler
Date: Tue Mar 20 16:17:47 2007
New Revision: 520650

URL: http://svn.apache.org/viewvc?view=rev&rev=520650
Log:
Enable *.vt.xml files to be located in the correct directory within 
themes.
  
  

[...SNIP...]



Also a good solution.

I didn't want to mess with the structure of the pattern as I'm not 
familiar enough with dispatcher to know what side effects this may 
have. If you think it is safe to do this, then I agree bother are 
better than the current implementation.


I prefer the first option.
  

So do I.
I will make the update, may you check for the doap plugin please, I am 
not sure to be able to test it...


Salutations,
Cyriaque,



Ross


  

Re: svn commit: r520650 - in /forrest/trunk/whiteboard/plugins: org.apache.forrest.plugin.input.doap/ org.apache.forrest.plugin.internal.dispatcher/ org.apache.forrest.plugin.output.solr/ org.apache.f

[Cyriaque Dupoirieux]

le 21/03/2007 11:45 Ross Gardler a écrit :

Cyriaque Dupoirieux wrote:

le 21/03/2007 10:31 Ross Gardler a écrit :

Cyriaque Dupoirieux wrote:

le 21/03/2007 00:17 [EMAIL PROTECTED] a écrit :

Author: rgardler
Date: Tue Mar 20 16:17:47 2007
New Revision: 520650

URL: http://svn.apache.org/viewvc?view=rev&rev=520650
Log:
Enable *.vt.xml files to be located in the correct directory 
within themes.
  

[...SNIP...]



Also a good solution.

I didn't want to mess with the structure of the pattern as I'm not 
familiar enough with dispatcher to know what side effects this may 
have. If you think it is safe to do this, then I agree bother are 
better than the current implementation.


I prefer the first option.

So do I.
I will make the update, may you check for the doap plugin please, I 
am not sure to be able to test it...


See Thorstens response before making the changes. But, yes, I will 
test the DOAP stuff. I'm active on a project using that at present so 
I'll keep it up to date.

Too late, I have made the changes, but I will not commit.


Having said that, building the doap docs should be a sufficient test, 
as is the case with all plugins.
I think a specific target build.sh validation which will make a build.sh 
test + the generation of every plugins would be great to improve the 
test phase.


Cyriaque,


Ross

Re: svn commit: r520650 - in /forrest/trunk/whiteboard/plugins: org.apache.forrest.plugin.input.doap/ org.apache.forrest.plugin.internal.dispatcher/ org.apache.forrest.plugin.output.solr/ org.apache.f

[Cyriaque Dupoirieux]

le 21/03/2007 10:31 Ross Gardler a écrit :

Cyriaque Dupoirieux wrote:

le 21/03/2007 00:17 [EMAIL PROTECTED] a écrit :

Author: rgardler
Date: Tue Mar 20 16:17:47 2007
New Revision: 520650

URL: http://svn.apache.org/viewvc?view=rev&rev=520650
Log:
Enable *.vt.xml files to be located in the correct directory within 
themes.
  

[...SNIP...]



Also a good solution.

I didn't want to mess with the structure of the pattern as I'm not 
familiar enough with dispatcher to know what side effects this may 
have. If you think it is safe to do this, then I agree bother are 
better than the current implementation.


I prefer the first option.

So do I.
I will make the update, may you check for the doap plugin please, I am 
not sure to be able to test it...


Salutations,
Cyriaque,



Ross

Re: svn commit: r520650 - in /forrest/trunk/whiteboard/plugins: org.apache.forrest.plugin.input.doap/ org.apache.forrest.plugin.internal.dispatcher/ org.apache.forrest.plugin.output.solr/ org.apache.f

[Cyriaque Dupoirieux]

le 21/03/2007 00:17 [EMAIL PROTECTED] a écrit :

Author: rgardler
Date: Tue Mar 20 16:17:47 2007
New Revision: 520650

URL: http://svn.apache.org/viewvc?view=rev&rev=520650
Log:
Enable *.vt.xml files to be located in the correct directory within themes.
  

[...SNIP...]


Modified: 
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/locationmap.xml
URL: 
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/locationmap.xml?view=diff&rev=520650&r1=520649&r2=520650
==
--- 
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/locationmap.xml
 (original)
+++ 
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/locationmap.xml
 Tue Mar 20 16:17:47 2007
@@ -247,21 +247,21 @@
 
 
 
-
+
 
 -src="{properties:resources}/themes/{properties:dispatcher.theme}/html/{1}.vt.xml" 
+src="{properties:resources}/themes/{properties:dispatcher.theme}/{2}/{1}-{2}.vt.xml" 
 />
 -src="{properties:resources}/themes/{properties:dispatcher.fallback.theme}/html/{1}.vt.xml" 
+src="{properties:resources}/themes/{properties:dispatcher.fallback.theme}/{2}/{1}-{2}.vt.xml" 
 />

 
-
+
 -src="{lm:dispatcher.themer}/themes/{properties:dispatcher.theme}/html/{1}.vt.xml" 
+src="{lm:dispatcher.themer}/themes/{properties:dispatcher.theme}/{2}/{1}-{2}.vt.xml" 
 />
 -src="{lm:dispatcher.themer}/themes/{properties:dispatcher.fallback.theme}/html/{1}.vt.xml" 
+src="{lm:dispatcher.themer}/themes/{properties:dispatcher.fallback.theme}/{2}/{1}-{2}.vt.xml" 
 />

 
 
  

Ok, that's nice,
Don't you think a pattern like :




...
Would be clearer ?

Or at least a pattern like the following to avoid to have the format in 
the tiles filename :



 
   


WDOT ?


Salutations,
Cyriaque


Modified: 
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.output.solr/locationmap.xml
URL: 
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.output.solr/locationmap.xml?view=diff&rev=520650&r1=520649&r2=520650
==
--- 
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.output.solr/locationmap.xml
 (original)
+++ 
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.output.solr/locationmap.xml
 Tue Mar 20 16:17:47 2007
@@ -42,10 +42,10 @@
 
   
 
-
+
   
-
-
+
+
   
 
   



  

Re: common-fo.vt.xml is in html directory

[Cyriaque Dupoirieux]

le 20/03/2007 16:50 Ross Gardler a écrit :

Why is common-fo.vt.xml in html directory rather than the fo directory?

Ross



Hi,

   Because the pdf generation is new with the dispatcher and few things 
- like this one - are still missing.

   cf. http://svn.apache.org/viewvc?view=rev&revision=518640

Salutations,
Cyriaque,

Re: svn commit: r518991 - in /forrest/trunk/main: build.xml fresh-site/forrest.properties.dispatcher.properties

[Cyriaque Dupoirieux]

le 16/03/2007 17:32 Ross Gardler a écrit :

[...SNIP...]

+project.required.plugins=org.apache.forrest.plugin.output.pdf
+project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.inputModule 



That's a typo right? We should only have one setting for these 
properties.

Corrected,

Cyriaque,


Ross

Re: Test before commit (was Re: dispatcher pdf issues)

[Cyriaque Dupoirieux]

le 16/03/2007 10:27 Ross Gardler a écrit :

Ok I have committes, Thank you David and Gavin.
Now we have to wait 3 ours to see what happens,


We should not have to wait. In fact the test builds should never fail 
because we should never fail because we should all be doing thorough 
tests before committing any changes.


That means...

cd $FORREST_HOME/main
./build.sh test

(Not sure if this tests dispatcher or not, it should, so if you are 
working on dispatcher please ensure the test is added).

This doesn't test the dispatcher...
I am going to see what I can do. I think we need to seed a dispatcher 
template site and generate it...


Thank you,

Cyriaque,



There is no excuse for breaking SVN in a way that is picked up by the 
ForrestBot.


(of course we all do it from time to time, I'm not pointing fingers 
here, the archives show every one of us has made a mistake in the 
past. My intention is only to remind us of good practice)


Ross

[jira] Resolved: (FOR-830) content-xml-link.ft outputs pdf

[Cyriaque Dupoirieux (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FOR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cyriaque Dupoirieux resolved FOR-830.
-

   Resolution: Fixed
Fix Version/s: 0.8-dev
 Assignee: Cyriaque Dupoirieux

Patch applied, thank you Paul.

> content-xml-link.ft outputs pdf
> ---
>
> Key: FOR-830
> URL: https://issues.apache.org/jira/browse/FOR-830
> Project: Forrest
>  Issue Type: Bug
>  Components: Dispatcher (aka views)
>Affects Versions: 0.8-dev
>Reporter: paul bolger
> Assigned To: Cyriaque Dupoirieux
>Priority: Minor
> Fix For: 0.8-dev
>
> Attachments: content-xml-link-fixed.patch
>
>
> content-xml-link.ft actually outputs the PDF contract. Patch attached. Sorry 
> if I've patched the wrong copy of the file - there seems to be one in each of 
> the two Dispatcher plugins.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

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

Cyriaque Dupoirieux commented on FOR-311:
-

This plugin should be superseded by the odt plugin.
Are we sure that we want to maintain this version which manage a format 
abandonned by OOo ?

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: https://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
> Attachments: headings.zip, openoffice-writer.sxw, 
> openoffice-writer2.sxw, openoffice-writer2forrest.xsl, 
> openoffice-writer_clay.diff, openoffice-writer_update.sxw
>
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r514362 - in /forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt: css/pelt.screen.css html/pelt-html.vt.xml images/Thumbs.db images/chapter.gif images/chapter_

[Cyriaque Dupoirieux]

le 05/03/2007 10:21 Gav a écrit :
  

-Original Message-
From: Cyriaque Dupoirieux [mailto:[EMAIL PROTECTED]
Sent: Monday, 5 March 2007 5:41 PM
To: Forrest Developers List
Subject: Re: svn commit: r514362 - in
/forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pe
lt: css/pelt.screen.css html/pelt-html.vt.xml images/Thumbs.db
images/chapter.gif images/chapter_open.gif

le 04/03/2007 07:21 [EMAIL PROTECTED] a écrit :




  

   
 
   
-2002
+2007

  

No, inception year of Acme Software Organisation is still 2002.
The actual year 2007 will be automatically calculated...



I Cyriaque,

I realise how inception and current date work, I was just bringing it upto
Date for the example. 'Acme' is a generic that anyone is allowed to use, 
There is no inception date as such - Acme has been in cartoons etc since the

Early 20's. Clicking on the link to acme.org/licenses/ will take you to some
Random place at the moment you can buy cheap travel there.

If it really makes that much of a difference, I'll put it back.
  

Ok sorry for the noise...


Gav...

  

Salutations,
Cyriaque,



 The Acme Software Organisation.
   

link>http://www.acme.org/licenses/


   
@@ -256,4 +284,4 @@
   -->
   
 
-
\ No newline at end of file
+

Modified:
  

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pel
t/images/Thumbs.db


URL:
  

http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.f
orrest.themes.core/themes/pelt/images/Thumbs.db?view=diff&rev=514362&r1=51
4361&r2=514362

==




Binary files - no diff available.

Modified:
  

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pel
t/images/chapter.gif


URL:
  

http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.f
orrest.themes.core/themes/pelt/images/chapter.gif?view=diff&rev=514362&r1=
514361&r2=514362

==




Binary files - no diff available.

Modified:
  

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pel
t/images/chapter_open.gif


URL:
  

http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.f
orrest.themes.core/themes/pelt/images/chapter_open.gif?view=diff&rev=51436
2&r1=514361&r2=514362

==




Binary files - no diff available.




  



  

Re: svn commit: r514362 - in /forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt: css/pelt.screen.css html/pelt-html.vt.xml images/Thumbs.db images/chapter.gif images/chapter_

[Cyriaque Dupoirieux]

le 04/03/2007 07:21 [EMAIL PROTECTED] a écrit :

Author: gmcdonald
Date: Sat Mar  3 22:21:50 2007
New Revision: 514362

URL: http://svn.apache.org/viewvc?view=rev&rev=514362
Log:
Changes to make pelt theme more like pelt skin FOR-811, a little more to do.

Modified:

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/css/pelt.screen.css

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/pelt-html.vt.xml

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/images/Thumbs.db

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/images/chapter.gif

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/images/chapter_open.gif

Modified: 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/css/pelt.screen.css
URL: 
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/css/pelt.screen.css?view=diff&rev=514362&r1=514361&r2=514362
==
--- 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/css/pelt.screen.css
 (original)
+++ 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/css/pelt.screen.css
 Sat Mar  3 22:21:50 2007
@@ -234,9 +234,9 @@
 padding: 5px 15px 4px;
 width: .1em; /* IE/Win fix */
 }
-#nav-main li a:link {  color: #00; }
-#nav-main li a:visited { color: #00; }
-#nav-main li a:hover { color: #00; }
+#nav-main li a:link {  color: #0F3660; }
+#nav-main li a:visited { color: #0F3660; }
+#nav-main li a:hover { color: #0F3660; }
 
 #nav-main > li a { width: auto; } /* Rest of IE/Win fix */
 
@@ -253,15 +253,15 @@

 #nav-main .current a {
 font-weight: bold;
 padding-bottom: 5px;
-color: #00;
+color: #CFDCED;
 background-image: 
url(../themes/images/roundcorner-t-l-5-bg294563-stroke4A6D8C-fg4A6D8C.png);
 background-repeat: no-repeat;
 background-position: top left;
 }
 
-#nav-main .current a:link {  color: #00;  }

-#nav-main .current a:visited { color: #00; }
-#nav-main .current a:hover { color: #00; }
+#nav-main .current a:link {  color: #CFDCED;  }
+#nav-main .current a:visited { color: #CFDCED; }
+#nav-main .current a:hover { color: #CFDCED; }
 
 #publishedStrip {

 position: relative;
@@ -285,10 +285,20 @@
 position:relative;
 background-color: #4A6D8C ;
 }
-#level2tabs a{padding-right: 5px;}
-#level2tabs a:link {  color: #00; }
-#level2tabs a:visited {  color: #00; }
-#level2tabs a:hover { color: #66; }
+#level2tabs a {padding-right: 5px;
+background-color: #CFDCED;
+text-decoration:none;
+cursor: pointer;
+background-image: url('../themes/images/chapter.gif');
+background-repeat: no-repeat;
+background-position: center left;
+margin-left: 6px;
+padding-left : 6px;
+}
+#level2tabs a:link {  color: #66; }
+#level2tabs a:visited {  color: #66; }
+#level2tabs a:hover { color: #66; text-decoration:underline; }
+#level2tabs a:selected {background-color: #4A6D8C; color: #CFDCED;}
 /*
 *border-top: solid #4A6D8C 15px;
 */
@@ -353,11 +363,11 @@
 padding: 0px;
 }
 
-#leftbar a {  font-weight: normal;}

-#leftbar a:link { color: #00; }
-#leftbar a:visited { color: #00; }
-#leftbar a:active { color: #00; }
-#leftbar a:hover { color: #FFCF00; }
+#leftbar a {  font-weight: normal; text-decoration: none;}
+#leftbar a:link { color: #FF; }
+#leftbar a:visited { color: #FF; }
+#leftbar a:active { color: #FF; }
+#leftbar a:hover { color: #FFCF00; text-decoration: underline; }
 
 #menuarea { width:10em;}
 
@@ -394,15 +404,15 @@

 }
 #nav-section .pagegroup span {
 background-image: url('../themes/images/chapter.gif');
-color: #00;
+color: #CEDFEF;
 }
 .pagegroupselected span {
 background-image: url('../themes/images/chapter_open.gif');
-color: #00;
+color: #CEDFEF;
 }
 .pagegroupopen span {
 background-image: url('../themes/images/chapter_open.gif');
-color: #00;
+color: #CEDFEF;
 }
 
 .pagegroupselected {

@@ -446,6 +456,7 @@
 color: #00;
 padding: 0px 0px 0px 6px;
 font-style : normal;
+   font-weight : normal;
 border-style: solid;
 border-width: 1px;
 margin-right: 10px;

Modified: 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/pelt-html.vt.xml
URL: 
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/pelt-html.vt.xml?view=diff&rev=514362&r1=514361&r2=514362
==
--- 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/pelt-html.vt.xml
 (original)
+++ 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes

Re: Getting 0.8-dev out the door

[Cyriaque Dupoirieux]

le 29/01/2007 00:17 Thorsten Scherler a écrit :
On Sat, 2007-01-27 at 11:44 +0900, Gav wrote: 
  

There has been lots of talk lately regarding upgrading Cocoon, using
Ivy/Maven + other stuff.

All of these are fine and are paving the way forward, but as far as I can
see , none of these should be affecting what happens in 0.8-dev, they are
talks for possibly the next version.



Yes, I agree.
  

Don't know exactly...
  

I am concerned that everybody is already moving on to the next greatest
thing and leaving 0.8-dev behind in its unfinished state. 



No, I myself need a 0.8 release (within the next couple of months).
  

I also need a stable 0.8 release to dive into forrest 2 !
  

Whilst I
appreciate that everyone has their own agendas on what is good for them,
what is good for the short term of the project is not being attended to and
this can lead to a long term deficit.



Yeah, in lenya we are suffering ATM the consequences. People get the
impression there is no development since there is no release.
  

Exact, we all think the same when we download an open source project...
I think we should think about a way to really shorten our release lifecycle.
A small version every three months should be motivating for us - devs - 
and above all for forrest users !
If you are using linux, look at the pleasure you have when the system 
updates the programs you are using :-)  ! That's great to see bugs are 
fixed and that new features always appear.




  

I would like to know what everyone feels about everyone concentrating on
getting 0.8-dev fixed and released as soon as possible. There are 25 roadmap
issues and if everyone worked on them it wouldn't take long to get these
crossed off. We should also resurrect IRC sessions purely for collaboration
on getting 0.8 issues fixed.



agree, but somebody need to follow it through. There have been many
attempts from different people so far.

  

The one major decision in the release is whether or not dispatcher is ready
to be released from the whiteboard into (I think Thorsten mentioned) a
plugin endorsed by the community, or whether it will be part of core.



...
  

To complex to decide. Dispatcher can stay in the whiteboard.
An old roadmap was to clear the core from skin and to create an 
independent plugin for skin so that the forrest users can choose the way 
to generate.
(We are far from this dream, many thing from the skin still appear in a 
site generated with the dispatcher...)


Salutations,
Cyriaque,

Thoughts ?



IMO we should release the dispatcher into the official plugins and then release 
0.8.

salu2
  

[Dispatcher] head and body tags are inverted

[Cyriaque Dupoirieux]

Hi,

   With the dispatcher, the head tag is generated after the body tag 
and it is not W3C...

   http://www.w3.org/TR/html4/struct/global.html#edef-HTML

   I have a problem with this because some scripts are included in the 
head and are not found in the body - because the body appears first...


   How can I correct this ?

--
Salutations,
Cyriaque,

Re: howto-dispatcher-install

[Cyriaque Dupoirieux]

Thorsten Scherler a écrit :

[SNIP]

Easy enough to find using Google,
but I can't see any way of getting from

http://forrest.apache.org/docs_0_80/index.html

to

http://forrest.apache.org/docs_0_80/howto/howto-dispatcher-install.html

using the site nav.



Hmm, we need to remove this docu since it is not maintained in this
location anymore. 


http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.html

salu2



  

Will you correct this Thorsten ?
I cannot, I have not working copy of Forrest at the moment.


Salutations,
Cyriaque,

Re: ODT plugin

[Cyriaque Dupoirieux]

Paul Bolger a écrit :

The ODT plugin seems to be working with images now, which is a great
step forward. Does anyone know what the status is with getting the
images to then get sent through to a rendered PDF?

I have worked on the ODT plugin (images, text style...) And I will 
continue because it is a good way to make forrest popular.

Now I use it everytime I update an existing page or create a new one.
My problem is that I don't have currently pages containing pictures and 
above all, I don't have much time to spend on forrest.


When I am back, I will try to fix the problem.
Gice me two weeks or three...


Salutations,
Cyriaque,

Re: Forrestbar for Firefox 2

[Cyriaque Dupoirieux]

C. Grobmeier a écrit :

Hi,

any chance/plans to upgrade the forrestbar tool for firefox2?

regards,
chris



It has been upgraded iin the 0.8-dev.
Maybe we can update it in the 0.7 ?

I ask on the dev list to see

Salutations,
Cyriaque,

Re: [jira] Commented: (FOR-145) Make Forrest able to be imported by Ant

[Cyriaque Dupoirieux]

Ross Gardler a écrit :

Thorsten Scherler (JIRA) wrote:
[ 
http://issues.apache.org/jira/browse/FOR-145?page=comments#action_12449623 
] Thorsten Scherler commented on FOR-145:

---

I started to prefix all targets.

An observation is that we now need to add the "forrest." prefix as 
well calling forrest.


When we did in main/ ./build.sh clean we now have to use ./build.sh 
forrest.clean 


This is going to break peoples build systems. Would it be better to 
deprecate the none prefixed versions of clean, run, site (and any 
others we can think of)?


Ross


Maybe we can alert the user that the target (clean for instance) is 
deprecated and redirect to the forrest.clean target


Salutations,
Cyriaque,

Re: svn commit: r466066 - /forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/content-main.ft

[Cyriaque Dupoirieux]

le 20/10/2006 16:50 Thorsten Scherler a écrit :

On Fri, 2006-10-20 at 11:19 +, [EMAIL PROTECTED] wrote:
  

Author: cdupoirieux
Date: Fri Oct 20 04:19:45 2006
New Revision: 466066

URL: http://svn.apache.org/viewvc?view=rev&rev=466066
Log:
Need to pass the context here...



Hmm, why?
http://www.w3.org/1999/XSL/Transform";>
  

Meaning all xsl:templates "know" $content-main-conf. No need to ...
  

Yes, I think your are right, because I have made some tests friday night.
I am going to continue my tests and correct this.

Thanks,

Salutations,
Cyriaque,

  

Modified:

forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/content-main.ft

Modified: 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/content-main.ft
URL: 
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/content-main.ft?view=diff&rev=466066&r1=466065&r2=466066
==
--- 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/content-main.ft
 (original)
+++ 
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/pelt/html/content-main.ft
 Fri Oct 20 04:19:45 2006
@@ -95,8 +95,12 @@
   
 
   

+



see above. 


IMO we should remove all  in the
xsl:template.

salu2
  

Re: Plugin Specific Stylsheets

[Cyriaque Dupoirieux]

le 16/10/2006 11:03 Gav a écrit :

I think we touched on this before, at least I remember lots of
Questions on how can it be done.

As an example FOR-412 has a stylesheet in Jira ready to be applied
But we don't know where to apply it (at least I don't).

We don't want plugin specific stylesheets to be mixed up with
Skin or theme stylesheets because they will be redundant to
Those that don't use the plugin. Also things like images that
Are for the projectinfo plugin reside in core when they should 
Also be in the plugin as they are plugin specific.


So I had a thought. I wonder if we can create a /resources/css
In the plugin, put any stylesheets in there,

I am a fervent supporter of this behaviour.
I think that plugin should be able to come with specific resources (css 
files, xsl style sheets, images...) and these resources should not be 
part of the core.




 enable it with
A 'plugin.stylesheet="yes"' in the plugins forrest.properties.xml
And then get forrest to check for this when the 'forrest' gets built
And adds it to the projects /resources/css and adds it to the rendered
Output.
  

In my first thought, there was no need of such a property.
The plugin comes with its resources which can be overriden by projects 
with location map fallback mecanism...



Does that make sense. If so or not any ideas on how to get started?
  

I have not think about it yet,
I will come back latter..

Salutations,
Cyriaque,


Once this plugin stylesheet problem is sorted then a few issues I think
Can be closed, including FOR-412 to start with to test if the solution
Works.

Gav...



  

Re: svn commit: r453159 - /lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl

[Cyriaque Dupoirieux]

le 13/10/2006 05:10 David Crossley a écrit :

Cyriaque, sorry that that happened to you.
  

No problem,

I wonder if using svn:external is warranted.
This is the only place that we use it in Forrest SVN.

Perhaps it would be better to have an 'svn copy' and
deliberately merge from time-to-time as needed.
  
I think I am going to include what I previously did in the 
odt-to-forrest.xsl - because, in fact, it is more the good place, 
because it is a little forrest specific.
I am going to see if we can manage to keep a shared file with Lenya. (In 
this case we have to discuss with the team to see if the improvments are 
good for both project)


Salutations,
Cyriaque,

-David

Cyriaque Dupoirieux wrote:
  

le 09/10/2006 23:24 Renaud Richardet a ??crit :


Hello,
  

Hello,

I get the following error when opening the odt sample page on zones 
(http://lenya.zones.apache.org:/default/authoring/doctypes/opendocument.html): 



Could not find variable with the name of dirname

org.apache.cocoon.ProcessingException: Failed to process pipeline at 
[TransformerException] - 
file:/export/home/lenya/src/lenya-trunk/build/lenya/webapp/lenya/modules/opendocument/xslt/common/odt_to_xhtml.xsl:476:109 
at  - 
file:/export/home/lenya/src/lenya-trunk/build/lenya/webapp/lenya/modules/opendocument/sitemap.xmap:62:36 
at  - 
file:/export/home/lenya/src/lenya-trunk/build/lenya/webapp/lenya/modules/opendocument/sitemap.xmap:57:96 
at  - file:/exp


Is the issue somehow similar to 
http://mail-archives.apache.org/mod_mbox/forrest-dev/200606.mbox/[EMAIL PROTECTED] 
?
  

I didn't know I was working on a Lenya file.
The variable is defined in the parent stylesheet which is a forrest file.
I am going to rollback because I am so surprised that I don't know at 
the moment what to do...


Sorry,

Salutations,
Cyriaque,



--Renaud

[EMAIL PROTECTED] wrote:
  

Author: cdupoirieux
Date: Thu Oct  5 02:31:28 2006
New Revision: 453159

URL: http://svn.apache.org/viewvc?view=rev&rev=453159
Log:
Images management.
(inspired by the OOo plugin.)

Modified:
   lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl

Modified: 
lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl
URL: 
http://svn.apache.org/viewvc/lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl?view=diff&rev=453159&r1=453158&r2=453159 

== 

--- lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl 
(original)
+++ lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl 
Thu Oct  5 02:31:28 2006

@@ -463,6 +463,21 @@



+  
+
+select="@xlink:href"/>

+
+
+
+
+
+src="/{$dirname}openDocumentEmbeddedImages/zip-{$filename}.odt/file-{$href}" 
alt="{../@draw:name}"/>

+
+
+
+






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 




  

Re: [Resolve location map]

[Cyriaque Dupoirieux]

Great, Thank you Thorsten, Nice you are back  :-) .

Salutations,
Cyriaque,

le 11/10/2006 13:46 Thorsten Scherler a écrit :
On Wed, 2006-10-11 at 12:43 +0200, Cyriaque Dupoirieux wrote: 
  

Hi,

I would like to resolve a location map within my browser (just like 
the forrest bar does with the contracts for instance)
I would like to entre in the URL something like : 
lm:transform.xml.xml-namespace-stripped

And to see the located stylesheet...




Well, that mean you need to teach your browser the lm protocol.

Meaning (with a forrest servlet running) typing 
lm://transform.xml.xml-namespace-stripped in your browser will give you

that firefox does not know the protocol.

http://www.codeproject.com/internet/FirefoxProtocol.asp
http://nexgenmedia.net/docs/protocol

Where you should first add a generic match in the core like:





and the protocol would "rewrite" (the easiest solution)
lm://transform.xml.xml-namespace-stripped to
http://localost:/lm.transform.xml.xml-namespace-stripped

This solution only works with forrest running as servlet, further it
assumes that forrest is running on the 
host: localhost

port: 
servlet-prefix: null

If you want to implement it in the forrestbar, then we need to make this
configurable. Which would be awesome then we can get rid of the 3
different "local forrest" we have now.

HTH

salu2
  

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: openoffice-writer2forrest.xsl
openoffice-writer_clay.diff
openoffice-writer_update.sxw

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
> Attachments: headings.zip, openoffice-writer.sxw, 
> openoffice-writer2.sxw, openoffice-writer2forrest.xsl, 
> openoffice-writer_clay.diff, openoffice-writer_update.sxw
>
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: headings.zip
openoffice-writer.sxw
openoffice-writer2.sxw

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
> Attachments: headings.zip, openoffice-writer.sxw, 
> openoffice-writer2.sxw, openoffice-writer2forrest.xsl, 
> openoffice-writer_clay.diff, openoffice-writer_update.sxw
>
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: (was: openoffice-writer_update.sxw)

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: (was: openoffice-writer_clay.diff)

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: (was: openoffice-writer2forrest.xsl)

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: (was: openoffice-writer.sxw)

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: (was: openoffice-writer.sxw)

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (FOR-311) OOo Headings bug causes Forrest to fail

[Cyriaque Dupoirieux (JIRA)]

 [ http://issues.apache.org/jira/browse/FOR-311?page=all ]

Cyriaque Dupoirieux updated FOR-311:


Attachment: (was: headings.zip)

> OOo Headings bug causes Forrest to fail
> ---
>
> Key: FOR-311
> URL: http://issues.apache.org/jira/browse/FOR-311
> Project: Forrest
>  Issue Type: Improvement
>  Components: Plugin: input.OpenOffice.org
>Affects Versions: 0.6
> Environment: All
>Reporter: Charles Palmer
>Priority: Minor
>
> There appears to be a bug or feature in OpenOffice which affects how haedings 
> are stored as XML. It appears that if a virgin document is opened then all 
> headings are stored in  tags, but if an existing document is opened 
> that lacks a particular haeding style, then if you create that heading style 
> it is stored in  tags.
> This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file 
> identifies OOo headings by looking for the  tags.
> (Moved detail from Description to Comment - see 2005-12-24)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [FOR-311] Attachments lost

[Cyriaque Dupoirieux]

Ho, I have the right to delete attachments,
sorry,


Salutations,
Cyriaque,

le 12/10/2006 08:55 Cyriaque Dupoirieux a écrit :

Hi,

   I have the attachments but I would like to remove the current ones 
- which are all corrupted - but I have not the access rights...


   Can someone do this for me please...

Salutations,
Cyriaque,

le 12/10/2006 07:24 David Crossley a écrit :

Ross Gardler wrote:
 

Cyriaque Dupoirieux wrote:
   

Hi,

  We have lost the attachments of the 
http://issues.apache.org/jira/browse/FOR-311...


  I don't know haw to get them from the system used before JIRA.
  If someone tells me, I will get them back.
  

http://issues.cocoondev.org/browse/FOR-311



Cyriaque can you create an account and retrieve the attachemnts?
If not, then an older Forrest developer will need to do it.

-David


  

Re: [FOR-311] Attachments lost

[Cyriaque Dupoirieux]

Hi,

   I have the attachments but I would like to remove the current ones - 
which are all corrupted - but I have not the access rights...


   Can someone do this for me please...

Salutations,
Cyriaque,

le 12/10/2006 07:24 David Crossley a écrit :

Ross Gardler wrote:
  

Cyriaque Dupoirieux wrote:


Hi,

  We have lost the attachments of the 
http://issues.apache.org/jira/browse/FOR-311...


  I don't know haw to get them from the system used before JIRA.
  If someone tells me, I will get them back.
  

http://issues.cocoondev.org/browse/FOR-311



Cyriaque can you create an account and retrieve the attachemnts?
If not, then an older Forrest developer will need to do it.

-David


  

[Resolve location map]

[Cyriaque Dupoirieux]

Hi,

   I would like to resolve a location map within my browser (just like 
the forrest bar does with the contracts for instance)
   I would like to entre in the URL something like : 
lm:transform.xml.xml-namespace-stripped

   And to see the located stylesheet...

--
Salutations,
Cyriaque,

Re: svn commit: r453159 - /lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl

[Cyriaque Dupoirieux]

le 09/10/2006 23:24 Renaud Richardet a écrit :

Hello,

Hello,


I get the following error when opening the odt sample page on zones 
(http://lenya.zones.apache.org:/default/authoring/doctypes/opendocument.html): 



Could not find variable with the name of dirname

org.apache.cocoon.ProcessingException: Failed to process pipeline at 
[TransformerException] - 
file:/export/home/lenya/src/lenya-trunk/build/lenya/webapp/lenya/modules/opendocument/xslt/common/odt_to_xhtml.xsl:476:109 
at  - 
file:/export/home/lenya/src/lenya-trunk/build/lenya/webapp/lenya/modules/opendocument/sitemap.xmap:62:36 
at  - 
file:/export/home/lenya/src/lenya-trunk/build/lenya/webapp/lenya/modules/opendocument/sitemap.xmap:57:96 
at  - file:/exp


Is the issue somehow similar to 
http://mail-archives.apache.org/mod_mbox/forrest-dev/200606.mbox/[EMAIL PROTECTED] 
?

I didn't know I was working on a Lenya file.
The variable is defined in the parent stylesheet which is a forrest file.
I am going to rollback because I am so surprised that I don't know at 
the moment what to do...


Sorry,

Salutations,
Cyriaque,



--Renaud

[EMAIL PROTECTED] wrote:

Author: cdupoirieux
Date: Thu Oct  5 02:31:28 2006
New Revision: 453159

URL: http://svn.apache.org/viewvc?view=rev&rev=453159
Log:
Images management.
(inspired by the OOo plugin.)

Modified:
lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl

Modified: 
lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl
URL: 
http://svn.apache.org/viewvc/lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl?view=diff&rev=453159&r1=453158&r2=453159 

== 

--- lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl 
(original)
+++ lenya/trunk/src/modules/opendocument/xslt/common/odt_to_xhtml.xsl 
Thu Oct  5 02:31:28 2006

@@ -463,6 +463,21 @@
 
 
 
+  
+
+select="@xlink:href"/>

+
+
+
+
+
+src="/{$dirname}openDocumentEmbeddedImages/zip-{$filename}.odt/file-{$href}" 
alt="{../@draw:name}"/>

+
+
+
+
 
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

[FOR-311] Attachments lost

[Cyriaque Dupoirieux]

Hi,

   We have lost the attachments of the 
http://issues.apache.org/jira/browse/FOR-311...


   I don't know haw to get them from the system used before JIRA.
   If someone tells me, I will get them back.

--
Salutations,
Cyriaque,

Re: BUG: LM and i18n

[Cyriaque Dupoirieux]

le 21/09/2006 22:50 Sjur Moshagen a écrit :

Den 21. sep. 2006 kl. 23.15 skrev Sjur Moshagen:

If not then set a breakpoint on LocationmapSourceFactory.java:75 and 
take a look at the file location.


How do I set a breakpoint? Anyway, I will try to produce more 
debugging info.


After I did this, the error disappeared. Forrest is now behaving 
exactly the way I want - clicking on a language makes that language 
the default language for subsequent requests.


I have no idea what fixed the bug - I have later commented out my 
extra debug line, and there's no change.


Perhaps rebuilding Forrest did something. Anyway - no bug anymore!

Cache problem perhaps ?


Sjur

Re: [jira] Commented: (FOR-934) i18n language override menu

[Cyriaque Dupoirieux]

Ross Gardler a écrit :

Sjur Moshagen wrote:

Den 20. sep. 2006 kl. 17.00 skrev Thorsten Scherler (JIRA):

[ 
http://issues.apache.org/jira/browse/FOR-934?page=comments#action_12436238 
]


Thorsten Scherler commented on FOR-934:
---

I had a quick look at the patch and it would make a good plugin.

Since the dispatcher contract is only a small part of the overall 
code and the code is not limited to the dispatcher it makes sense to 
create a plugin out of it.


wdyt?


Sure, that way I guess it would be available both to dispatcher and 
non-dispatcher users. One could argue that this i18n-functionality 
should really be part of the core, to make the i18n services of 
Forrest complete, though.


I've not been following the i18n discussions, but I have to admit that 
when I saw Thorstens comments I wondered "why not core?".


I'm not doing the work on this so do it however you like. But if you 
want my (possibly uninformed) opinion then I'd say core is the right 
place.


Ross



+1 to include it in the core...

Re: svn commit: r447768 - /forrest/trunk/site-author/content/xdocs/live-sites.xml

[Cyriaque Dupoirieux]

Hi,

We have lots of live sites now.
Maybe we should think to sort them - in a table ?

With the following information :

Site
Short description
Forrest version
Skinned or Dispatcher
Skin or Theme
Comment on customisation
Le Renard 
French Family site
Forrest 8.0-dev
Dispatcher
Pelt
Uses pdf, odt, projectInfo and php plugins,
WebRing inclusion 



What do you think ?
If this table is created, the new users who want to add their site will 
certainly give us these information...


Salutations,
Cyriaque,

le 19/09/2006 09:24 [EMAIL PROTECTED] a écrit :

Author: cdupoirieux
Date: Tue Sep 19 00:24:43 2006
New Revision: 447768

URL: http://svn.apache.org/viewvc?view=rev&rev=447768
Log:
Add of the http://www.erbox.org site.

Modified:
forrest/trunk/site-author/content/xdocs/live-sites.xml

Modified: forrest/trunk/site-author/content/xdocs/live-sites.xml
URL: 
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/live-sites.xml?view=diff&rev=447768&r1=447767&r2=447768
==
--- forrest/trunk/site-author/content/xdocs/live-sites.xml (original)
+++ forrest/trunk/site-author/content/xdocs/live-sites.xml Tue Sep 19 00:24:43 
2006
@@ -164,7 +164,8 @@
 - Modeling and simulation of cells, other biological entities, and
 biochemical networks, using Xholon.
   
-
+  http://www.erbox.org/";>ER/Box Site An all Java, open source ERP system built 
on Compiere and Apache Derby. Some customisations have been http://www.erbox.org/documentation/Other/ForrestNotes/forrestNotesOverview.html";>documented.
+  
 
 
 




  

Re: [ODT Plugin]

[Cyriaque Dupoirieux]

le 15/09/2006 16:40 Thorsten Scherler a écrit :

On Fri, 2006-09-15 at 16:29 +0200, Cyriaque Dupoirieux wrote:
  

le 13/09/2006 13:29 Thorsten Scherler a écrit :


On Wed, 2006-09-13 at 13:21 +0200, Cyriaque Dupoirieux wrote:
  
  

le 13/09/2006 13:16 Thorsten Scherler a écrit :



On Wed, 2006-09-13 at 13:08 +0200, Cyriaque Dupoirieux wrote:
  
  
  

Hi,

I realise that I have made several improvment on the input.odt 
plugin because I had not the good layout (Notes, Sources...)

Are you Ok I commit my changes ?




Sure, why do you ask?
  
  
  
Because I am not sure of the state of this plugin, it is written that it 
generates xhtml2 and  or  are not I think...



Hmm, the odt plugin was started by me ASAIR and back then it was
producing xhtml and this xhtml then got transformed to xdocs. You may
want to look into the html-to-xdocs.xsl and enable the generation of
notes/source out of divs/spans there. This way not only the odt plugin
will be enhanced.
  
  

Well, but I cannot find this file, can you help ?



cd $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.input.odt/
cat input.xmap
...
 
...
cd $FORREST_HOME/main/webapp/resources/stylesheets
ls |grep "html*"
...
html-to-document.xsl

Should be this one. 
  
Okay, now I understand why the odt plugin generates h1, h2 ... headers 
which are interpreted by the dispatcher - or the skins - as sections.

(I was a little lost...)

I am improving the sample to validate the plugin and I will see latter 
how we can manage specific xdocs tags - such as notes, warnings...


Thank you very much.
(I should have search by myself before to ask...)

Salutations,
Cyriaque,

hth

salu2

  

Salutations,
Cyriaque,

  
  
I am going to wait a little (maybe for Ross answer :-P ) and I'll commit 
if everyone is Ok.


Just a reminder we have Commit-then-Review in place. 

  
  

Thanks Thorsten,



de nada.

salu2

  
  

salu2