The following comment has been added to this issue: Author: Ross Gardler Created: Wed, 1 Jun 2005 6:07 AM Body: In one sense you change is a big improvement on my original code. However, it prevents the ability to add a meningful title to each section since the title becomes the value of the context attribute.
Perhaps we can provide an (optional) lookup table in the status.xml file that will give a title, for example: <status> <actionContexts> <context id="code" description="Changes to the Code Base"> <context id="docs" description="Changes to the Documentation"> </action> ... <status> If no entry is found for //actionContexts/[EMAIL PROTECTED]"CONTEXT"] then we would use the @id value in titles otherwise we would use //actionContexts/[EMAIL PROTECTED]"CONTEXT"]/@description In later versions this would allow for internationalisation of the status contexts. WDYT? [NB try to submite changes as patched, it makes it much easier for us to apply and therefore increases the chance of it being applied in a timely fashion. If you don't know how ask us on the dev list.] --------------------------------------------------------------------- View this comment: http://issues.cocoondev.org//browse/FOR-514?page=comments#action_12460 --------------------------------------------------------------------- View the issue: http://issues.cocoondev.org//browse/FOR-514 Here is an overview of the issue: --------------------------------------------------------------------- Key: FOR-514 Summary: Do not limit status.xml contexts in project info plugin Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: projectInfo Assignee: Reporter: Ross Gardler Created: Wed, 1 Jun 2005 6:02 AM Updated: Wed, 1 Jun 2005 6:07 AM Description: (This comment brought over from FOR-487) This improvement of changes page is nice. I have my own version based on xsl:key definition in order to be able to simply manage as many contexts as you can define (My Dtd is not limited to "build|docs|code|admin|design". The advantage - on my opinion - is that my own contexts are very various and not developpement oriented nor language dependant. here a short example - using releaseNote... : http://cyriaque.dupoirieux.free.fr/changes_6.2.1.html The following code replace the 5 blocks <xsl:if test="[EMAIL PROTECTED]'build']"> : <title>Version <xsl:value-of select="@version"/> (<xsl:value-of select="@date"/>)</title> + <xsl:for-each select="action[generate-id()=generate-id(key('contextes',concat(../@version, '_', @context)))]"> + <xsl:sort select="@context"/> + <section> + <title><xsl:value-of select="@context"/></title> + <ul> + <xsl:apply-templates select="key('contextes',concat(../@version, '_', @context) )"> + <xsl:sort select="@type"/> + </xsl:apply-templates> + </ul> + </section> + </xsl:for-each> Hope you'll like the idea... Regards, Cyriaque, --------------------------------------------------------------------- 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