[JIRA] Assigned: (FOR-487) generate announcement text from the status.xml
Message: The following issue has been re-assigned. Assignee: Juan Jose Pablos (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Open Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Juan Jose Pablos Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Mon, 9 May 2005 3:41 AM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-487) generate announcement text from the status.xml
The following issue has been updated: Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED]) Date: Mon, 9 May 2005 3:43 AM Comment: dtd changed needed Changes: Attachment changed to importance.patch - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-487?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Open Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Juan Jose Pablos Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Mon, 9 May 2005 3:43 AM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
Cocoon GetTogether 2005: call for assistance
Hi folks, a few months ago, I tentatively reserved The Pand in Ghent again for our annual gathering - now scheduled for 10-11 october 2005. Only a while after that, I learned about O'Reilly EuroOSCON, to be held October 17-20 in Amsterdam. There's obviously a bit of a scheduling conflict here - OTOH, Amsterdam and Ghent are only a 2 1/2 hour drive from each other, and October is always a busy conference month. We're May now, and we need to decide how to move forward for the GetTogether. After last year's GetTogether, we decided to untie the GT from any commercial involvement (however small there ever was any), making sure the GT is an event organized by and for the Cocoon community. That means we need to form some sort of GT organisation committee, for which we need a couple of volunteers. As for now, we need the following answers to be answered: * are we on for 10-11 October? * Ghent again? * are you up for volunteering? Things we need to tackle soon now: * website design development (the cocoongt.org domain has been registered for this purpose) * call for proposals and ideas We might seek some affiliation with the Apache Conference team as well. Please direct your replies to [EMAIL PROTECTED] Regards, /Steven -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source Java XMLAn Orixo Member Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org
status state
Hi, i am looking at how we use status.xml, and these are my impressions: 1) I always like it status.xml to be on the root of out svn space, so when you make a change you could modify it over there. Can we change that back? 2) I tried to put the document type of status and I have found around 400 validation errors. they are mostly on the context attributes. The valid attributes are build,code,docs,admin,design My proposal is to add documentation about the scope of every single attribute ie: build --- our build system and tools that make the sofware code --- xsl,sitemaps and java code that we use docs --- our website, and documentation of the project. design -- ¿?¿? skins maybe? out of that I am happy to help to convert all of those. Cheers, cheche
New Web Site based on Forrest
Hello, Just a note to let you know that I have published my web site using Apache Forrest. I still have some minor issues to resolve, but the content is driven entirely from Docbook XML. http://www.inwords.co.za Feedback thoughts, ideas, typos, etc. All welcomed. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpVlb9xBDbwT.pgp Description: PGP signature
Re: status state
Juan Jose Pablos wrote: Hi, i am looking at how we use status.xml, and these are my impressions: 1) I always like it status.xml to be on the root of out svn space, so when you make a change you could modify it over there. Can we change that back? I have no feelings in this whatsoever. 2) I tried to put the document type of status and I have found around 400 validation errors. they are mostly on the context attributes. :-)) I did exactly the same thing and decided it was too big a job to fix in the middle of the night when I did it, so I ran away ;-) The valid attributes are build,code,docs,admin,design My proposal is to add documentation about the scope of every single attribute ie: build --- our build system and tools that make the sofware code --- xsl,sitemaps and java code that we use docs --- our website, and documentation of the project. design -- ¿?¿? skins maybe? I'd put skins under code, especially with view/viewhelper coming along which blurs the distinction even more. design would be things like refactoring? out of that I am happy to help to convert all of those. I'm still running away, so feel free ;-) Ross
[Proposal] Forrest Terminology
Whenever I start explaining Forrest, I stumble into the problem of crossing terminology borders, using terms like 'build', 'compile', 'run' for the Forrest program and at the same time applying them to Forrest projects. If this is not just my ignorance about the proper terms, can we perhaps try and define a terminology that makes it easier to know whether the instruction 'after that run Forrest' means - 'execute a Forrest run from the commandline' or - 'execute Forrest from the commandline' Or whether 'after that re-build your forrest' means that I should rebuild the Java sources or run Forrest to rebuild the static pages. I find this extremely frustrating because you either have to assume that a user will know what to do from context or you have to use unpleasantly detailed wording to be sure they get it right. If nobody objects, I'd be happy to suggest some changes to fix these conflicts. -- Ferdinand Soethe
Re: New Web Site based on Forrest
On Monday 09 May 2005 13:32, Ross Gardler wrote: Sean Wheller wrote: Just a note to let you know that I have published my web site using Apache Forrest. I still have some minor issues to resolve, but the content is driven entirely from Docbook XML. http://www.inwords.co.za added, thanks Great. Feedback thoughts, ideas, typos, etc. All welcomed. I was thinking of contacting people like yourself, who have customised their skins, and requesting that you make the skin available for others via the skin download mechanism. It would be an easy way to contribute back to the community. All you need to do is package the skin using forrest and make it available somewhere on the web and let us know what to add to the skins.xml file (see http://forrest.apache.org/0.6/docs/skin-package.html ) Of course, there is no obligation to do this. If the skin is an important part of your corporate branding we will understand perfectly. Problem is, the skin download mechanism has been around for a long time but has not really been tested out in the real world. Perhaps you could help us out by being the first to provide a skin to download? Yes, I am aware of this problem. However, like you say branding is an issue. I will see if I can squeeze some time to develop a more generic skin type, based on the one you see on my web site, and publish that. I may also have the opportunity to produce a new skin for another project I am working on. Keep in touch. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpbWulqy5TKz.pgp Description: PGP signature
Re: [Proposal] Forrest Terminology
Ferdinand Soethe wrote: Whenever I start explaining Forrest, I stumble into the problem of crossing terminology borders, using terms like 'build', 'compile', 'run' for the Forrest program and at the same time applying them to Forrest projects. ... If nobody objects, I'd be happy to suggest some changes to fix these conflicts. We'd never object to suggestions ;-) In this case I don't see the problem, but as you say that is because I am a user who can infer the context. If you can improve things for new users then we're all listening. Ross
Plugin simplified.docbook
Hi, On a separate instance of forrest I have updated to svn HEAD. In my project forrest.properties I have defined project.required.plugins=org.apache.forrest.plugin.input.simplified-docbook When I run forrest my site is rendered but content (docbook 4.2 xml is not). Yet it appears that the plugin is installed and configured. check-java-version: This is apache-forrest-0.7-dev Using Java 1.4 from /usr/lib/jvm/java-1.4.2-sun-1.4.2.06/jre init-plugins: Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Copying 1 file to /home/sean/projects/inwordsweb/trunk/build/tmp Installing plugin: org.apache.forrest.plugin.input.simplified-docbook configure-input-plugin: Mounting input plugin: org.apache.forrest.plugin.input.simplified-docbook Processing /home/sean/projects/inwordsweb/trunk/build/tmp/input.xmap to /home/sean/projects/inwordsweb/trunk/build/tmp/input.xmap.new Loading stylesheet /home/sean/projects/forrest/main/var/pluginMountSnippet.xsl Moving 1 files to /home/sean/projects/inwordsweb/trunk/build/tmp Processing /home/sean/projects/inwordsweb/trunk/build/tmp/resources.xmap to /home/sean/projects/inwordsweb/trunk/build/tmp/resources.xmap.new Loading stylesheet /home/sean/projects/forrest/main/var/pluginMountSnippet.xsl Moving 1 files to /home/sean/projects/inwordsweb/trunk/build/tmp Switching back to my previous instance of Forrest, the site renders with all content. Any pointers. -- Sean Wheller Technical Author [EMAIL PROTECTED] 084-854-9408 http://www.inwords.co.za Registered Linux User #375355 pgpnF7Vrg5YsS.pgp Description: PGP signature
Encoding-atribute in site.xml (copied from user list)
Ross Gardler wrote: RG Roland Becker wrote: Is there e reason, that site.xml after forrest seed has no encoding-atribute? If there is a german umlaut in site.xml, then build fails with: linkmap.html BROKEN: Invalid byte 2 of 2-byte UTF-8 sequence. BUILD FAILED C:\programme\apache-forrest-0.6\src\core\targets\site.xml:43: Java returned: 1 RG No reason that I am aware of or can imagine. I've updated the file in RG site.xml for the next release. Funny, I have been using Umlaute with 0.7 head all over my site.xml and never had a problem compiling it. See below: ?xml version=1.0? site label=Bildungsverein Hannover href= xmlns=http://apache.org/forrest/linkmap/1.0; tab=home about label=Über uns tab=home über_uns label=Wir über uns href=index.html/ Dozentinnen label=Dozent/innen href=dozentinnen.html/ Lernorte label=Lernorte href=lernorte.html/ agbs label=Geschäftsbedingungen href=agbs.html/ newsletter label=Newsletter href=newsletter.html/ kontakt label=Kontakt href=kontakt.html/ impressum label=Impressum href=impressum.html/ wegweiser label=Wegweiser href=Wegweiser.html/ /about I assumed that somebody had fixed the problem in the meantime but never checked. Now I did and found that Eclipse understands site to be utf-8 even though there is not explicit declaration. Perhaps we should append the issue and the FAQ entry (How to use special characters in the labels of the site.xml file?) referring to the problem and explain that you _can_ use special characters directly if you use the standard utf-8 encoding for site.xml (and make sure your editor knows it). Still unclear to me: Am I correct that this is an _editor problem_ in the sense that no encoding-attribute means the file is utf-8 but Roland's editor needed a stronger hint? Thanks, Ferdinand Soethe
