ForrestBot build for forrest-sample-2 FAILED
Automated build for forrest-sample-2 FAILED Log attached. -- Forrestbot run ended at 06 January 08:56 AM Using Forrest 0.8-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2006-01-06 08:56:06 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 check-java-version: [echo] This is apache-forrest-0.8-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: init-plugins: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.output.pdf check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf [echo] Installing plugin: org.apache.forrest.plugin.output.themer check-plugin: [echo] org.apache.forrest.plugin.output.themer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.internal.structurer check-plugin: [echo] org.apache.forrest.plugin.internal.structurer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-internal-plugin: [echo] Mounting internal plugin: org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp init: -prepare-classpath: check-contentdir: examine-proj: validation-props: validate-xdocs: [xmlvalidate] 18 file(s) have been successfully validated. [echo] ...validated xdocs
[jira] Updated: (FOR-722) tools/xxe/README.txt should be added into the docs; and broken link
[ http://issues.apache.org/jira/browse/FOR-722?page=all ] Sjur N. Moshagen updated FOR-722: - Attachment: xxe-tool-doc-update.diff Here's a patch that synchronises the two documents. Whether a synchronisation counts as a merge, I don't know:-) The patch also corrects the bad link, and clarifies and corrects a few points in the README.txt file as well as the xxe.xml doc. With this patch I think the issue can be closed (barring the note above re merge). tools/xxe/README.txt should be added into the docs; and broken link --- Key: FOR-722 URL: http://issues.apache.org/jira/browse/FOR-722 Project: Forrest Type: Bug Components: Documentation and website, Tool: XXE config Versions: 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: xxe-tool-doc-update.diff Merge the tools/xxe/README.txt with site-author/content/xdocs/tools/xxe.xml There is also a broken link at bottom of page. -- 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: maintain forrest.properties skinconf.xml etc. (Was: svn commit: r366100)
David Crossley wrote: David Crossley wrote: Ross Gardler wrote: Thorsten Scherler wrote: ... I reckon that benchmark can be minimal. I also want to keep the v3 minimal. The v2 i have not touched because i presume that it will be entirely removed prior to the 0.8 release. WDYT Sounds fine to me. To link the history of the discussion for the archives: http://thread.gmane.org/gmane.text.xml.forrest.devel/18638 http://issues.apache.org/jira/browse/FOR-776 As mentioned there, Reinhard did some experimentation at Cocoon-2.2 (pre Daisy docs) that used svn:externals to maintain the forrest.properties and skinconf.xml etc. I will investigate and report back. I get the feeling that it only operates at directory level. Here is a summary of his technique. There are two aspects: - including copy of common configuration files via svn:externals - using xml entities to manage common sections of xml files Standard configuration files are at http://svn.apache.org/repos/asf/cocoon/site/src/forrest-configuration There are various things here such as sitemap.xmap and stylesheets which we would not need for our situation. Using 'svn:externals' this directory is created wherever it is needed, e.g. under http://svn.apache.org/repos/asf/cocoon/trunk/src/documentation/src So the tree is ... documentation |-- forrest.properties |-- src (this second src directory was a forrest config mistake) |-- content |-- forrest-configuration - |-- skinconf.xml The forrest.properties refers to resources in the forrest-configuration directory. The skinconf.xml declares some of its own stuff, and includes other skinconf.xml files by using xml entities. Clever. :-) --oOo-- So we could use this technique for managing the config files of our plugins. At the moment the only ones that i can think of is skinconf.xml and maybe the CatalogManager.properties file. Later we might need to include others. What do you reckon? Sounds like a great idea. --oOo-- The other thing that we discussed (need to find the thread) was to streamline these seed sites so that we can generate various seed sites, e.g. one that strips out the Apache licensing info. I reckon leave this until stage two. Actually, the infrastructure is already in place in the ant scripts. I built it for the business template which asks a series of questions and uses ants filtering to insert the responses into the relevant file. Note, it is also possible to run an automated business seed, where no questions are asked and default responses are used. It's just a case of reusing things, no need for discussion (unless you can think of a better way of course). Ross
[jira] Created: (FOR-780) built xxe tool has wrong version number
built xxe tool has wrong version number --- Key: FOR-780 URL: http://issues.apache.org/jira/browse/FOR-780 Project: Forrest Type: Bug Components: Tool: XXE config Versions: 0.8-dev Reporter: Sjur N. Moshagen Attachments: xxe-tool-build.xml.diff I forgot to change the version number in the build.xml file :-( The attached patch fixes that. -- 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
ForrestBot build for forrest-sample-2 FAILED
Automated build for forrest-sample-2 FAILED Log attached. -- Forrestbot run ended at 06 January 11:56 AM Using Forrest 0.8-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2006-01-06 11:56:11 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 check-java-version: [echo] This is apache-forrest-0.8-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: init-plugins: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.output.pdf check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf [echo] Installing plugin: org.apache.forrest.plugin.output.themer check-plugin: [echo] org.apache.forrest.plugin.output.themer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.internal.structurer check-plugin: [echo] org.apache.forrest.plugin.internal.structurer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-internal-plugin: [echo] Mounting internal plugin: org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp init: -prepare-classpath: check-contentdir: examine-proj: validation-props: validate-xdocs: [xmlvalidate] 18 file(s) have been successfully validated. [echo] ...validated xdocs
Re: ForrestBot build for forrest-sample-2 FAILED
On 1/6/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Automated build for forrest-sample-2 FAILED Log attached. -- Forrestbot run ended at 06 January 11:56 AM Using Forrest 0.8-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2006-01-06 11:56:11 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 check-java-version: [echo] This is apache-forrest-0.8-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: init-plugins: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.output.pdf check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf [echo] Installing plugin: org.apache.forrest.plugin.output.themer check-plugin: [echo] org.apache.forrest.plugin.output.themer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.internal.structurer check-plugin: [echo] org.apache.forrest.plugin.internal.structurer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-internal-plugin: [echo] Mounting internal plugin: org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp init:
Re: ForrestBot build for forrest-sample-2 FAILED
On 1/6/06, Tim Williams [EMAIL PROTECTED] wrote: On 1/6/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Automated build for forrest-sample-2 FAILED Log attached. -- Forrestbot run ended at 06 January 11:56 AM Using Forrest 0.8-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2006-01-06 11:56:11 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 check-java-version: [echo] This is apache-forrest-0.8-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: init-plugins: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.output.pdf check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf [echo] Installing plugin: org.apache.forrest.plugin.output.themer check-plugin: [echo] org.apache.forrest.plugin.output.themer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.internal.structurer check-plugin: [echo] org.apache.forrest.plugin.internal.structurer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-internal-plugin: [echo] Mounting internal plugin: org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to
Re: photogallery plugin thoughts
Hi Tim, I read you proposal with a real interest because I have the same feeling a couple of weeks ago. (I don't have any skills in Java programming ... ;-) ) I'm using Forrest Photogallery plugin feature into a personnal genealogical site and I'm manipuling a lot a family pictures and/or census scans I spent a lot of time to migrate my previous Forrest v0.6 into Photogallery directories and it was a mess to have to generate images three times each Apart of that is the disk space required according to the resolution used. So in my point of view, I would be a great mechanism to only have one original picture and Forrest take care of everything for the others 2. So point 2 is my preferred. If somebody decides to implement that please let me know where I have to sign up ;-) Regards Philippe Tim Williams wrote: I've looked at the Photogallery plugin and have some changes I'd like to discuss. 1) Move from directory to file convention. I don't particularly care for the whole directory-based convention for the image variations (preview | small | big). I'd like to just be able to dump a bunch of existing image directories into the gallery and not have to do much work. (Yeah, I know there's scripting that can do some grunt work here). I'd like to move the plugin to a filename based approach. The short version is that each image variation would live in the same directory as the main image file but with an added identifier in the name. Something like: IMG001.jpg IMG001.thumb.jpg IMG001.small.jpg 2) Let cocoon generate these images for us. I don't like having to pregenerate all of the image variations so I would like cocoon to do it for us. This is pretty simple with the ImageReader but we very quickly run into memory issues. The only solution to this (besides the obvious boosting maxmem) I can think of is to implement a PersistentImageReader that, once it generates the requested image variation, writes it to disk. Then, the next time though it only needs to be read from disk. This means that cocoon needs write permission but it's about the best way I can think to do it. I've actually got #1 working with the plain ImageReader (although it could be static disk-based as well). I've got #2 mostly working as well but the image writing needs some cleanup. Anyway, I like where this is going but didn't want to drastically change the current plugin without some discussion. WDYT? --tim -- Signature Philippe PEREZ Partner Support Engineer Tl. : +33 1 34 03 17 08 Fax: +33 1 34 03 17 20 Port. : +33 6 08 52 82 38 AIM : pperezfr [EMAIL PROTECTED] Sun Microsystems France S.A 13 avenue Morane Saulnier 78140 Velizy Villacoublay Le site ddi la formation : http://fr.sun.com/formation Augmentez vos bnfices. Toutes les formations Solaris 10. Enregistrez-vous ds prsent "Legal Notice The information contained in this communication is confidential, is intended only for the use of the recipient named above, and might be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original transmission or any copy of it."
Re: photogallery plugin thoughts
Philippe, Can you please send all mailing list email in *plain text*? HTML isn't very mailing list or mailing archive friendly. Thanks, --tim On 1/6/06, philippe perez [EMAIL PROTECTED] wrote: Hi Tim, I read you proposal with a real interest because I have the same feeling a couple of weeks ago. (I don't have any skills in Java programming ... ;-) ) I'm using Forrest Photogallery plugin feature into a personnal genealogical site and I'm manipuling a lot a family pictures and/or census scans I spent a lot of time to migrate my previous Forrest v0.6 into Photogallery directories and it was a mess to have to generate images three times each Apart of that is the disk space required according to the resolution used. So in my point of view, I would be a great mechanism to only have one original picture and Forrest take care of everything for the others 2. So point 2 is my preferred. If somebody decides to implement that please let me know where I have to sign up ;-) Regards Philippe Tim Williams wrote: I've looked at the Photogallery plugin and have some changes I'd like to discuss. 1) Move from directory to file convention. I don't particularly care for the whole directory-based convention for the image variations (preview | small | big). I'd like to just be able to dump a bunch of existing image directories into the gallery and not have to do much work. (Yeah, I know there's scripting that can do some grunt work here). I'd like to move the plugin to a filename based approach. The short version is that each image variation would live in the same directory as the main image file but with an added identifier in the name. Something like: IMG001.jpg IMG001.thumb.jpg IMG001.small.jpg 2) Let cocoon generate these images for us. I don't like having to pregenerate all of the image variations so I would like cocoon to do it for us. This is pretty simple with the ImageReader but we very quickly run into memory issues. The only solution to this (besides the obvious boosting maxmem) I can think of is to implement a PersistentImageReader that, once it generates the requested image variation, writes it to disk. Then, the next time though it only needs to be read from disk. This means that cocoon needs write permission but it's about the best way I can think to do it. I've actually got #1 working with the plain ImageReader (although it could be static disk-based as well). I've got #2 mostly working as well but the image writing needs some cleanup. Anyway, I like where this is going but didn't want to drastically change the current plugin without some discussion. WDYT? --tim -- Philippe PEREZ Partner Support Engineer Tél. : +33 1 34 03 17 08 Fax : +33 1 34 03 17 20 Port. : +33 6 08 52 82 38 AIM : pperezfr [EMAIL PROTECTED] Sun Microsystems France S.A 13 avenue Morane Saulnier 78140 Velizy Villacoublay Le site dédié à la formation : http://fr.sun.com/formation Augmentez vos bénéfices. Toutes les formations Solaris 10. » Enregistrez-vous dès à présent Legal Notice The information contained in this communication is confidential, is intended only for the use of the recipient named above, and might be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original transmission or any copy of it.
ForrestBot build for forrest-sample-2 FAILED
Automated build for forrest-sample-2 FAILED Log attached. -- Forrestbot run ended at 06 January 02:56 PM Using Forrest 0.8-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2006-01-06 02:56:07 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 check-java-version: [echo] This is apache-forrest-0.8-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: init-plugins: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.output.pdf check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf [echo] Installing plugin: org.apache.forrest.plugin.output.themer check-plugin: [echo] org.apache.forrest.plugin.output.themer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.internal.structurer check-plugin: [echo] org.apache.forrest.plugin.internal.structurer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-internal-plugin: [echo] Mounting internal plugin: org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp init: -prepare-classpath: check-contentdir: examine-proj: validation-props: validate-xdocs: [xmlvalidate] 18 file(s) have been successfully validated. [echo] ...validated xdocs
Re: ForrestBot build for forrest-sample-2 FAILED
On 1/6/06, Tim Williams [EMAIL PROTECTED] wrote: On 1/6/06, Tim Williams [EMAIL PROTECTED] wrote: On 1/6/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Automated build for forrest-sample-2 FAILED Log attached. -- Forrestbot run ended at 06 January 11:56 AM Using Forrest 0.8-dev Forrestbot administrator: Forrest developers -- [echo] ... Forrest render START 2006-01-06 11:56:11 ... Rendering docs in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 check-java-version: [echo] This is apache-forrest-0.8-dev [echo] Using Java 1.4 from /usr/j2se/jre init-props: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp echo-settings: check-skin: init-proxy: fetch-skins-descriptors: fetch-skin: unpack-skins: init-skins: init-plugins: [mkdir] Created dir: /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/webapp/conf [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [copy] Copying 1 file to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.output.pdf check-plugin: [echo] org.apache.forrest.plugin.output.pdf is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] No locationmap provided for plugin org.apache.forrest.plugin.output.pdf [echo] Installing plugin: org.apache.forrest.plugin.output.themer check-plugin: [echo] org.apache.forrest.plugin.output.themer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-output-plugin: [echo] Mounting output plugin: org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/output.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.themer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/locationmap.xml.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp [echo] Installing plugin: org.apache.forrest.plugin.internal.structurer check-plugin: [echo] org.apache.forrest.plugin.internal.structurer is available in the build dir init-props: echo-settings: init-proxy: fetch-plugins-descriptors: fetch-plugin: unpack-plugin: install-plugin: configure-plugin: configure-internal-plugin: [echo] Mounting internal plugin: org.apache.forrest.plugin.internal.structurer [xslt] Processing /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp/internal.xmap.new [xslt] Loading stylesheet /export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl [move] Moving 1 files to /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2/tmp configure-plugin-locationmap: [echo] Mounting plugin locationmap for
Re: [Proposal] Rules for Forrest Use of class-Attributes
Ross Gardler wrote: Function of class-Attributes Forrest components (and users) use class-attributes in 4 different ways: 1. Forrest uses class-attributes to preserve special meanings when transforming custom grammer (such as xdocs) to html. My interpretation of our use of class attributes in this context is different. We are not preserving special meaning we are conveying hints about how the output should be styled. The meaning at this point is completely irrelevant. Hmmm. Maybe I need to be more precise. Let's say we get to the point where xhtml will be our common internal format and all input must be transformed to xhtml before being transformed into the different output formats. - btw. this ties into our debate about the smartslides-plugin - How will I be able to supply meaning like this is a chapter of slides other then using class? Perhaps this is not needed to created Webpages or pdfs, but what about output plugins like slidy that need to know the meaning. Or - looking from a different angle - how can that one and only class serve as a hint for so different outputs as pdf, html, voice? If a user needs to maintain the contextual information then they should use the original source XML. Which was exactly what I had intended to do with Smartlides when you argued that all data had to go through the common format. I'm confused. Am I missing something? 2. Skinning uses class-attributes to identify, format and place skin specific (often generated) components such as menus and tabs. If you are referring to the *rendering* of the output then this statement is correct. If you are referring to the XDoc structure this is not true since there is not necessarily a direct correlation between XDoc structure and page structure (this is especially true in the Dispatcher work). Well skinning does the job of rendering it. To be more precise: I'm referring to the process of creating the part of a page that contains the menu items and tabs and uses a standard set of classes to allow all the skins to format it. 3. Users add class-attributes to elements to create new meanings or add 'submeanings' to existing elements and facilitate formatting of those with the Extra-CSS-mechnism. Example: By adding a class 'instructions' to a simple bulleted list I can format these lists differently with extra-css. Same comment as for 1 - the class attribute is a hint for styling not an indication of meaning. I disagree. The instruction class that I added to howto's some time ago is meaning that is deliberately carried all the way to the final html so that different skins can interpret that meaning whichever way they see fit. But perhaps I'm still missing your point. Can you help? I accept that in both case (1 and 3) it can be misused to convey meaning but that is just plain wrong. Users wishing to convey *meaning* should use an appropriate source format. Again: why misuse? I'm missing something here. 4. Plugins (often) need to use class-attributes (just like Forrest in 2) to carry meaning over to html. I can think of no example of this that is any different from the above cases, do you have something in mind? No, it is the same issue. Plugins just make it more problematic because each one may add they own set of new meanings. Remember XDoc is our intermediate format, it is not intended for human consumption. I understand that. But I think that software like out-plugins might have even more need to know meaning than humans. For example: The slidy transformations need to know where the chapters of a presentation are in order to process them correctly. A formatting hint like (make this a big heading) would be useless. - all transformations (including those in skinning and plugins) must preserve foreign class attributes. That is: Any class attributes attached to an element going into the transformation must be carried over into the resulting element. +1 - ion fact, as far as I am aware this has already been agreed, it's just that nobody has sat down and fixed each transformation by hand. Instead we have been adding them as we find they are a problem. Sure. I was just trying to summarize all the rules in one document. - When adding classes to elements that already have a class attribute, each new class it added to a space separated list. All transformations and css-formatting must be written to properly handle such class-lists. +1 This is one important part. I might have missed the outcome of the debate on having more that one class-name in a class-attribute. - To avoid conflicts between class names created by different modules, a module-specific prefix is added to the class name. For Forrest core modules and extra-css-classes this prefix can be static while each new plugin should be automatically assigned a unique prefix to use with all their class names. Yes.
Re: ForrestBot build for forrest-sample-2 FAILED
Tim Williams wrote: Tim Williams wrote: Tim Williams wrote: My guess is this is a result of the conflicting forrest.properties in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 Unfortunately I'm not sure which one is correct. It looks like the local modification should be kept since it enables views but I haven't followed the zone stuff as much as I should. A little more checking. I now see that forrest-sample-2 is built from fresh-site but there's nothing to re-enable views after the checkout. I dont' know if this is correct or not since a conflict from the locally enabled views probably would have surfaced by now. I wonder if we'd be better off basing forrest-sample-2 on template-sites\v3 instead? I changed it to v3, then back again -- got nervous I might be missing something. Anyway, looking around was fun, now I'll stop and let David fix it;) :-) Thanks for trying. The forrest-sample-2 has some manually modified config files. I will investigate - hopefully i can remember what i did. The reason that i had that seed-sample site is to excercise the Dispatcher on a full site. Yes, i have been meaning to set up the v3 seed for ages. Will try soon. -David
Re: photogallery plugin thoughts
Tim Williams wrote: Helena Edelson wrote: Just wondering since Java was mentioned, will you be coding this in xml for Forrest or do you need something in Java for Cocoon? something using JPEGCodec, JPEGImageEncoder, MediaTracker, Graphics2D, Resize, etc? My experience is that uploading the full images and using software/code to generate the thumbnail on the server is memory intensive, although I am not familiar with the readers mentioned by Tim. I know of a dll that resizes on the server on upload but who runs windoz servers anyway. Helena, Cocoon already has various compoments for handling images. See some basic demos here ... http://cocoon.zones.apache.org/demos/release/samples/imagereader/ Tim, there is a patch for a new imageop block sitting in Cocoon Jira which might be of interest. http://issues.apache.org/jira/browse/COCOON-1301 -David Hi Helena, Yeah, I was talking about extending the ImageReader, which already handles the resizing, to just write the newly resized image to disk. I want this because of the memory intensiveness you've mentioned. It turns it into essentially a one-time (hopefully non-cached) cost, then subsequent requests are read straight from disk instead of resizing yet again. I think this is a reasonable medium between pre-generating everything and dynamically generating everything. --tim
[jira] Closed: (FOR-780) built xxe tool has wrong version number
[ http://issues.apache.org/jira/browse/FOR-780?page=all ] David Crossley closed FOR-780: -- Fix Version: 0.8-dev Resolution: Fixed Done. built xxe tool has wrong version number --- Key: FOR-780 URL: http://issues.apache.org/jira/browse/FOR-780 Project: Forrest Type: Bug Components: Tool: XXE config Versions: 0.8-dev Reporter: Sjur N. Moshagen Fix For: 0.8-dev Attachments: xxe-tool-build.xml.diff I forgot to change the version number in the build.xml file :-( The attached patch fixes that. -- 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] Closed: (FOR-722) tools/xxe/README.txt should be added into the docs; and broken link
[ http://issues.apache.org/jira/browse/FOR-722?page=all ] David Crossley closed FOR-722: -- Resolution: Fixed Thanks Sjur. The confusion about merge was from a bad choice of words on my part. I meant that the README.txt should be removed and the documentation be added only to the xdocs. I will investigate. tools/xxe/README.txt should be added into the docs; and broken link --- Key: FOR-722 URL: http://issues.apache.org/jira/browse/FOR-722 Project: Forrest Type: Bug Components: Tool: XXE config, Documentation and website Versions: 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: xxe-tool-doc-update.diff Merge the tools/xxe/README.txt with site-author/content/xdocs/tools/xxe.xml There is also a broken link at bottom of page. -- 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
seed-v3 and dispatcher-enabled seed-sample (Was: ForrestBot build for forrest-sample-2 FAILED)
David Crossley wrote: Tim Williams wrote: Tim Williams wrote: Tim Williams wrote: My guess is this is a result of the conflicting forrest.properties in /export/home/config/forrestbot-trunk/conf/work/forrest-sample-2 Unfortunately I'm not sure which one is correct. It looks like the local modification should be kept since it enables views but I haven't followed the zone stuff as much as I should. A little more checking. I now see that forrest-sample-2 is built from fresh-site but there's nothing to re-enable views after the checkout. I dont' know if this is correct or not since a conflict from the locally enabled views probably would have surfaced by now. I wonder if we'd be better off basing forrest-sample-2 on template-sites\v3 instead? I changed it to v3, then back again -- got nervous I might be missing something. Anyway, looking around was fun, now I'll stop and let David fix it;) :-) Thanks for trying. The forrest-sample-2 has some manually modified config files. I will investigate - hopefully i can remember what i did. There were svn conflicts in the locally modified forrest.properties following the automatic 'svn update'. Fixed now. The way i have that set up is to let forrestbot do the very first build (so it was seed-sample) then tweak forrest.properties on the zone to have the structurer/themer plugins added. Thereafter the svn update keeps it in sync. Except for today's svn conflicts. Should be correct now. The reason that i had that seed-sample site is to excercise the Dispatcher on a full site. Yes, i have been meaning to set up the v3 seed for ages. Will try soon. It doesn't work anyway. There are stacks of errors from doing 'forrest seed-v3; forrest site'. When it is ready, then it is very easy to set up a forrestbot build for it. -David
Re: photogallery plugin thoughts
On 1/6/06, David Crossley [EMAIL PROTECTED] wrote: Tim Williams wrote: Helena Edelson wrote: Just wondering since Java was mentioned, will you be coding this in xml for Forrest or do you need something in Java for Cocoon? something using JPEGCodec, JPEGImageEncoder, MediaTracker, Graphics2D, Resize, etc? My experience is that uploading the full images and using software/code to generate the thumbnail on the server is memory intensive, although I am not familiar with the readers mentioned by Tim. I know of a dll that resizes on the server on upload but who runs windoz servers anyway. Helena, Cocoon already has various compoments for handling images. See some basic demos here ... http://cocoon.zones.apache.org/demos/release/samples/imagereader/ Tim, there is a patch for a new imageop block sitting in Cocoon Jira which might be of interest. http://issues.apache.org/jira/browse/COCOON-1301 -David Thanks David, That patch appears to expand the image handling capabilities -- which is cool -- but what I'm wanting is simply to write the image variants to disk. I've pretty much got it working but since it's a pretty huge change I want to make sure it's cool with everyone first. Right now, each variant (small, preview, and big) is created in it's own directory manually by the forrest user. What I want is to just be able to drag a bunch of my photo directories into the gallery and have those variants generated by Cocoon automatically -- when I implemented it I also made the change of being filename-based instead of directory based. This works fairly well though as you might imagine the first time through it's still memory intensive too. I also eventually want to make an additional change in behavior. The gallery\ directory will be seen as the root gallery. Any subdirectory of that one can have a gallery.meta file that describes the gallery and also may contain sub-galleries itself. Also, if there happens to be any graphically-gifted folks listening this gallery could use your help because it is pretty rough looking as is. My thought is that to improve it visually we may want to just wait until we can move it to views so that we can use *.fv files as sort of the Album Layout. --tim
Re: photogallery plugin thoughts
Tim Williams wrote: Thanks David, That patch appears to expand the image handling capabilities -- which is cool -- but what I'm wanting is simply to write the image variants to disk. I've pretty much got it working but since it's a pretty huge change I want to make sure it's cool with everyone first. Right now, each variant (small, preview, and big) is created in it's own directory manually by the forrest user. What I want is to just be able to drag a bunch of my photo directories into the gallery and have those variants generated by Cocoon automatically -- when I implemented it I also made the change of being filename-based instead of directory based. This works fairly well though as you might imagine the first time through it's still memory intensive too. I also eventually want to make an additional change in behavior. The gallery\ directory will be seen as the root gallery. Any subdirectory of that one can have a gallery.meta file that describes the gallery and also may contain sub-galleries itself. I for one, am very happy that you make those changes. This would certainly change that plugin's version number since it is different behaviour. So this would require adding the cocoon-imagereader-block to Forrest. Are you happy with doing Forrest's Cocoon upgrade process? I will do it if you are not comfortable. It would be good to do that soon anyway because Cocoon are starting to make some more radical changes to the build process. A good svn version would be 366397 which is just befaore Jorg added the tag: trunk_before_flattening as part of the Maven2 setup for Cocoon. -David Also, if there happens to be any graphically-gifted folks listening this gallery could use your help because it is pretty rough looking as is. My thought is that to improve it visually we may want to just wait until we can move it to views so that we can use *.fv files as sort of the Album Layout. --tim
