« Return to Thread: [gatewiki-commits] SF.net SVN: gatewiki:[1437] trunk/cow/doc
[gatewiki-commits] SF.net SVN: gatewiki:[1437] trunk/cow/doc
by hcunningham-2
::
Rate this Message:
Revision: 1437
http://gatewiki.svn.sourceforge.net/gatewiki/?rev=1437&view=rev
Author: hcunningham
Date: 2009-07-02 16:59:48 +0000 (Thu, 02 Jul 2009)
Log Message:
-----------
updated the backlog
Modified Paths:
--------------
trunk/cow/doc/cow-backlog.html
trunk/cow/doc/cow-backlog.yam
trunk/cow/doc/cow-done.html
trunk/cow/doc/cow-done.yam
Modified: trunk/cow/doc/cow-backlog.html
===================================================================
--- trunk/cow/doc/cow-backlog.html 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-backlog.html 2009-07-02 16:59:48 UTC (rev 1437)
@@ -49,7 +49,7 @@
<div class="cow-contents"><h2 class="cow-heading">Contents</h2>
<p><ul>
-<li><a href="#section-1.">1. Roadmap (finalisation of version 0.3)</a></li>
+<li><a href="#section-1.">1. Roadmap (version 0.4)</a></li>
<li><a href="#section-2.">2. Future Tasks</a></li>
<li><a href="#section-3.">3. Completed Tasks</a></li>
<li><a href="#section-4.">4. Work areas</a></li>
@@ -57,97 +57,122 @@
</ul></p></div>
<!--%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-->
-<a class="cow-section-anchor" name="section-1."/><h1 class="cow-heading"><span class="cow-sec-number">1. </span>Roadmap (finalisation of version 0.3)</h1>
+<a class="cow-section-anchor" name="section-1."/><h1 class="cow-heading"><span class="cow-sec-number">1. </span>Roadmap (version 0.4)</h1>
-<p>incoming:</p>
-
<ul>
-<li>update the backlog</li>
-<li>test reporting of svn conflicts during edit (and add to test suite, should
- be easier now not using canoo...)</li>
-</ul>
-
-
-<ul>
-<li>0.3 remaining </li>
+<li>add layouts capabilities appropriate for gate.ac.uk and the lifesci work
+ [NA, HC]</li>
+ <ul>
+ <li>layouts for whole wiki-areas</li>
<ul>
- <li>team wiki ... [MG, HC]</li>
+ <li>add a "areaLayoutName" to Wiki, which would reference a layout GSP in
+ the site-specific plugin; PageLinkTabLib would then use this for the
+ layout in that wiki area</li>
</ul>
- <li>done</li>
+ <li>layouts/navigation for specific directory trees</li>
<ul>
- <li>upgrade sam wiki [MG, IR]</li>
- <li>tag the gatewiki repository as 0.3 [MG]</li>
- <li>fix dependencies - dependent files are not being committed after changes
- [MG]</li>
- <li>a daemon script that can be linked from /etc/init.d which does a
- run-prod [MG]</li>
- <li>gate.ac.uk trialing [IR, MG, HC]</li>
- <li>Hudson testing against the production instances - heartbeat runs on most
- servers[MG]</li>
- <li>document tables / lists newlines thing [HC]</li>
+ <li>support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?</li>
+ <li>perhaps have them percolate down directory trees? they would need to be
+ picked up by JS or by yam2html</li>
</ul>
- <li>shift to future tasks</li>
+ <li>perhaps use</li>
<ul>
- <li>Look at Sventon proxying problems [IR] </li>
- <li>gate-top on g8rs.net [HC] </li>
- <li>non-native pages like javadocs: [HC, AR, IR]</li>
- <ul>
- <li>any directory that now contains a file called <tt>.cow:raw-html</tt> will now
- render any non-YAM HTML files directly (see
- <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a>). this means you can serve e.g. javadocs.
- <b>BUT</b> it is a potentially nasty security hole... so we need to add a
- better mechanism:</li>
- <ul>
- <li>add a list of path patterns to each wiki area, which would match
- either files or directories (AR might know the GORM invocations? a
- new table RawHtmlPatterns?)</li>
- <li>do an Ant API path match in PageController.show, according to config
- settings (IR would know the Ant API call?)</li>
- <li>when a non-native HTML (see <a class="cow-url" href="gatewiki.html#raw-html">the developer
- guide discussion</a> path matches serve it raw as with the
- <tt>.cow:raw-html</tt> mechanism</li>
- <li>check this works for javadocs and for other gate.ac.uk pages (tao
- etc.)</li>
- <li>finish the documentation in the user guide at
- <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a></li>
- <li>do we need a link back to the Wiki area from pages served raw? this
- could be nice, but a) isn't typical, e.g. for javadocs, and b) would
- need some munging of the page, e.g. by insertion (maybe of iframe?)
- just after the body tag or similar. so perhaps not worth it?</li>
- </ul>
- </ul>
+ <li>the Navigation Plugin gives you site navigation menus by convention. You
+ just define a property in your controllers to determine what actions are
+ shown and in what groups. <a class="cow-url" href="http://www.grails.org/Navigation+Plugin">http://www.grails.org/Navigation+Plugin</a></li>
</ul>
+ </ul>
</ul>
-
-<!--%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-->
-<a class="cow-section-anchor" name="section-2."/><h1 class="cow-heading"><span class="cow-sec-number">2. </span>Future Tasks</h1>
-
<ul>
-<li>Move <tt>cowrc.groovy</tt> inside <tt>cowrc.d</tt>? One less thing to reconfigure when you
- want to run more than one CoW on the same machine.</li>
+<li>gate-top on g8rs.net, inc. gate-server-redesign [HC] </li>
+<li>upgrade CoW to Grails 1.1 [IR for a week plus HC/AR/NA as needed]</li>
+ <ul>
+ <li>and get cow+mimir+gus running in the same instance (base of gc.net)</li>
+ </ul>
+<li>more conversion of gate.ac.uk material [HC,GG,NA]</li>
</ul>
<ul>
-<li>Fix conflict between Quartz versions</li>
+<li>non-native pages like javadocs: [HC, AR, IR]</li>
<ul>
- <li>Grails provides Quartz 1.6.x</li>
- <li>the Quartz plugin uses 1.5.2</li>
- <li>these are incompatiable</li>
+ <li>any directory that now contains a file called <tt>.cow:raw-html</tt> will now
+ render any non-YAM HTML files directly (see
+ <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a>). this means you can serve e.g. javadocs.
+ <b>BUT</b> it is a potentially nasty security hole... so we need to add a
+ better mechanism (and the ability to turn off the <tt>.cow:raw-html</tt> if I
+ didn't do that already?):</li>
<ul>
- <li>currently fixed by placing 1.6.1 in the quartz plugin directory</li>
- <li><b>THIS IS A NASTY HACK!</b></li>
+ <li>add a list of path patterns to each wiki area, which would match either
+ files or directories (AR might know the GORM invocations? a new table
+ RawHtmlPatterns?)</li>
+ <li>do an Ant API path match in PageController.show, according to config
+ settings (IR would know the Ant API call?)</li>
+ <li>when a non-native HTML (see <a class="cow-url" href="gatewiki.html#raw-html">the developer
+ guide discussion</a> path matches serve it raw as with the <tt>.cow:raw-html</tt>
+ mechanism</li>
+ <li>check this works for javadocs and for other gate.ac.uk pages (tao etc.)</li>
+ <li>finish the documentation in the user guide at
+ <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a></li>
+ <li>do we need a link back to the Wiki area from pages served raw? this
+ could be nice, but a) isn't typical, e.g. for javadocs, and b) would
+ need some munging of the page, e.g. by insertion (maybe of iframe?) just
+ after the body tag or similar. so perhaps not worth it?</li>
</ul>
+ <li>another (older?) note about this stuff:</li>
+ <ul>
+ <li>serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):</li>
+ <ul>
+ <li>perhaps in cow-managed svn trees we would allow something like a
+ special file called <tt>cow:layout.yam</tt> which might have entries like
+ <tt>non-yam-html=iframe</tt> or <tt>non-yam-html=raw</tt>; in the first case serve
+ it in an iframe, in the second case serve it raw</li>
+ </ul>
+ </ul>
</ul>
-<li>Sventon integration</li>
+</ul>
+
+<ul>
+<li>bugs and features missing for gate.ac.uk: [from GG, comments from HC]</li>
<ul>
+ <li><span class="cow-escape">%</span>contents links do not include path to current page, therefore links you
+ back to front page, i.e. <a class="cow-url" href="http://localhost:8080/#section_0.1.">http://localhost:8080/#section_0.1.</a> rather than
+ <a class="cow-url" href="http://localhost:8080/mydoc.html#section_0.1.">http://localhost:8080/mydoc.html#section_0.1.</a> [I tried to replicate this
+ but could not; I believe that a link to a bare <tt>#...</tt> anchor in any html
+ file will be relativised to the current page by the browser so I'm not
+ sure how this could be happening?]</li>
+ <li>relative links in areas other than area 2 do not work because they assume
+ you are in the default area (i.e. <a class="cow-non-existant-url" href="page1.html">page1.html</a> links to
+ <a class="cow-url" href="http://localhost:8080/page1.html">http://localhost:8080/page1.html</a> even if it should be
+ <a class="cow-url" href="http://localhost:8080/page/show/4/page1.html)">http://localhost:8080/page/show/4/page1.html)</a> [I can't replicate this
+ either; again a relative link will be dealt with the browser, not the
+ server? perhaps you made a link <span class="cow-escape">%</span>(/page.html), i.e. included the /
+ yourself?]</li>
+ <li>make a page containing a table with two rows, one of which is empty. Save
+ or preview results in the entire page content being dropped without
+ warning. [i.e. the error reporting seems broken; faults in table syntax
+ generate yam errors; need to look into this]</li>
+ <li>if the last thing in a table is a verbatim (<span class="cow-escape">%</span><span class="cow-escape"><</span>...<span class="cow-escape">></span><span class="cow-escape">%</span>) item, that thing
+ will not be verbatimised [need to check if this is in the list of known
+ yam bugs below nad if not add it]</li>
+ <li>no apparent way to make a picture into a link [just upload the file and
+ link to it? if this works for you add a note to the user guide?]</li>
+ <li>tables need more power if we are to use them for layout, i.e. control over
+ borders and width [I think we will do layout differently, see above. the
+ borders thing may need changing, or just the ability to set it from CSS?]</li>
+ </ul>
+</ul>
+
+<ul>
+<li>finish sventon integration [IR]</li>
+ <ul>
<li>proper proxying of sventon requests through a CoW controller
(/admin/sventon)</li>
<ul>
- <li>sventon pages contain all sorts of absolute path links:
- <a href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
- <div id="/sventon/ajax/...">
- (where <em>/sventon</em> is the context path where sventon is deployed)</li>
+ <li>sventon pages contain all sorts of absolute path links: <a
+ href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
+ <div id="/sventon/ajax/..."> (where <em>/sventon</em> is the context path where
+ sventon is deployed)</li>
<li>need to fix these up to point through cow, i.e. /sventon/repos ->
/admin/sventon/repos (for root-level CoW) or /sam/sventon/ajax ->
/sam/admin/sventon/ajax (for Cow deployed under /sam)</li>
@@ -158,19 +183,44 @@
contextPath, so don't need to massage the JavaScript code (phew).</li>
<li>when fetching the proxied content from sventon, add
;jsessionid=<session-id-from-cow> to the URLs, to keep sventon and cow
- sessions in sync. Any jsessionid in URLs generated by sventon need to be
- stripped during the HTML massaging process.</li>
+ sessions in sync. Any jsessionid in URLs generated by sventon need to
+ be stripped during the HTML massaging process.</li>
</ul>
<li>once proxying works, we can link from pages direct to their history.</li>
- <li>Simpler idea:</li>
+ <li>simpler idea:</li>
<ul>
- <li>Remove the localhost filter, allowing direct access to /sventon, but...</li>
- <li>Add a filter that checks for an object in the session before permitting
+ <li>remove the localhost filter, allowing direct access to /sventon, but...</li>
+ <li>add a filter that checks for an object in the session before permitting
access.</li>
- <li>This object is put in the session by CoW, posting to a URL that <em>is</em>
+ <li>this object is put in the session by CoW, posting to a URL that <em>is</em>
still restricted to localhost only.</li>
</ul>
</ul>
+<li>test reporting of svn conflicts during edit (and add to test suite, should
+ be easier now not using canoo...)</li>
+ <ul>
+ <li>do some stress-testing and logic checking of concurrent editing</li>
+ </ul>
+</ul>
+
+
+<!--%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-->
+<a class="cow-section-anchor" name="section-2."/><h1 class="cow-heading"><span class="cow-sec-number">2. </span>Future Tasks</h1>
+
+<ul>
+<li>team wiki ... [MG, HC]</li>
+<li>move <tt>cowrc.groovy</tt> inside <tt>cowrc.d</tt>? One less thing to reconfigure when you
+ want to run more than one CoW on the same machine.</li>
+<li>fix conflict between Quartz versions</li>
+ <ul>
+ <li>Grails provides Quartz 1.6.x</li>
+ <li>the Quartz plugin uses 1.5.2</li>
+ <li>these are incompatiable</li>
+ <ul>
+ <li>currently fixed by placing 1.6.1 in the quartz plugin directory</li>
+ <li><b>THIS IS A NASTY HACK!</b></li>
+ </ul>
+ </ul>
<li>saving space in deployed instances: see <a class="cow-url" href="gatewiki.html#saving-space">gatewiki.html#saving-space</a></li>
<li>new page bug (as found by milan)</li>
<ul>
@@ -179,7 +229,6 @@
try to do this via the new page form, but this doesn't work</li>
</ul>
<li>user guide to logging in, editing etc., revise <a class="cow-url" href="gatewiki.html">gatewiki.html</a></li>
-<li>do some stress-testing and logic checking of concurrent editing</li>
<li>regeneration</li>
<ul>
<li>setContext on the YamFile</li>
@@ -221,49 +270,12 @@
<ul>
<li>use the grails ant tasks</li>
</ul>
- <li>site-specific layout and config</li>
- <ul>
- <li>layouts for whole wiki-areas</li>
- <ul>
- <li>add a "areaLayoutName" to Wiki, which would reference a layout GSP in
- the site-specific plugin; PageLinkTabLib would then use this for the
- layout in that wiki area</li>
- </ul>
- <li>layouts/navigation for specific directory trees</li>
- <ul>
- <li>support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?</li>
- <li>perhaps have them percolate down directory trees? they would need to
- be picked up by JS or by yam2html</li>
- <li>example sites: gate.ac.uk or nlp.shef.ac.uk or ucu.group.shef.ac.uk or
- icon.shef.ac.uk</li>
- <li>perhaps use</li>
- <ul>
- <li>the Navigation Plugin gives you site navigation menus by convention.
- You just define a property in your controllers to determine what
- actions are shown and in what groups.
- <a class="cow-url" href="http://www.grails.org/Navigation+Plugin">http://www.grails.org/Navigation+Plugin</a></li>
- </ul>
- </ul>
- <li>serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):</li>
- <ul>
- <li>perhaps in cow-managed svn trees we would allow something like a
- special file called <tt>cow:layout.yam</tt> which might have entries like
- <tt>non-yam-html=iframe</tt> or <tt>non-yam-html=raw</tt>; in the first case serve
- it in an iframe, in the second case serve it raw</li>
- </ul>
- </ul>
<li>other bugs, see
<a class="cow-url" href="http://sourceforge.net/tracker2/?func=browse&group_id=208243&atid=1004913">http://sourceforge.net/tracker2/?func=browse&group_id=208243&atid=1004913</a></li>
<ul>
<li>titles including markup incorrectly include the markup in the html title
(e.g. <span class="cow-escape">%</span>br puts a <br/> into the title)</li>
</ul>
- <li>breadcrumbs: see <a class="cow-url" href="http://www.useit.com/alertbox/breadcrumbs.html">http://www.useit.com/alertbox/breadcrumbs.html</a>; a
- simple design where the directories above the current page are listed
- along with the top-level is probably enough, e.g. for the page
- doc/yam/summary.html we would have "You're here: Home > Help > Doc > Yam"
- as breadcrumbs. see also Darryl Pentz discussion in Jan on the mailing
- list.</li>
</ul>
<li>[CoW] dependencies</li>
<ul>
@@ -372,9 +384,6 @@
<li>use the SVNRep API, see:
<a class="cow-url" href="http://www.nabble.com/Re%3A-check-out-a-single-file--p15719277.html">http://www.nabble.com/Re%3A-check-out-a-single-file--p15719277.html</a></li>
</ul>
- <li>PC.newpageFlow does at least one and possible two redundant calls to
- PS.analyse: can replace these by making references to flow instead of
- thisPage</li>
</ul>
<li>[CoW] config, DBs and other user data: CowDataArea (CDA) <HC></li>
<ul>
@@ -435,7 +444,7 @@
expressions on each permission and (b) use the easier ant syntax, rather
than java regexp syntax.</li>
</ul>
-<li>[TAOWeb] "what we do page" <DD,VT>:</li>
+<li>[GATE.ac.uk] "what we do page" <DD,VT> (or: MIMIR search):</li>
<ul>
<li>A JSP that displays Di/Wim's taxonomy and allows users to select one or
more concepts</li>
@@ -562,22 +571,6 @@
<li>CowPermission(Wiki 1, directory "", controller [page, search], actions
[Read])</li>
</ul>
-<li>GG (Check to see if these really are bugs :)</li>
- <ul>
- <li><span class="cow-escape">%</span>contents links do not include path to current page, therefore links you back to
- front page, i.e. <a class="cow-url" href="http://localhost:8080/#section_0.1.">http://localhost:8080/#section_0.1.</a> rather than
- <a class="cow-url" href="http://localhost:8080/mydoc.html#section_0.1.">http://localhost:8080/mydoc.html#section_0.1.</a></li>
- <li>relative links in areas other than area 2 do not work because they assume
- you are in the default area (i.e. <a class="cow-non-existant-url" href="page1.html">page1.html</a> links to
- <a class="cow-url" href="http://localhost:8080/page1.html">http://localhost:8080/page1.html</a> even if it should be <a class="cow-url" href="http://localhost:8080/page/show/4/page1.html)">http://localhost:8080/page/show/4/page1.html)</a></li>
- <li>Make a page containing a table with two rows, one of which is empty. Save or
- preview results in the entire page content being dropped without warning.</li>
- <li>If the last thing in a table is a verbatim (<span class="cow-escape">%</span><span class="cow-escape"><</span>...<span class="cow-escape">></span><span class="cow-escape">%</span>) item, that thing will not
- be verbatimised</li>
- <li>No apparent way to make a picture into a link</li>
- <li>Tables need more power if we are to use them for layout, i.e. control over borders and
- width</li>
- </ul>
</ul>
Modified: trunk/cow/doc/cow-backlog.yam
===================================================================
--- trunk/cow/doc/cow-backlog.yam 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-backlog.yam 2009-07-02 16:59:48 UTC (rev 1437)
@@ -5,74 +5,91 @@
%contents
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%1 Roadmap (finalisation of version 0.3)
+%1 Roadmap (version 0.4)
-incoming:
+- add layouts capabilities appropriate for gate.ac.uk and the lifesci work
+ [NA, HC]
+ - layouts for whole wiki-areas
+ - add a "areaLayoutName" to Wiki, which would reference a layout GSP in
+ the site-specific plugin; PageLinkTabLib would then use this for the
+ layout in that wiki area
+ - layouts/navigation for specific directory trees
+ - support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?
+ - perhaps have them percolate down directory trees? they would need to be
+ picked up by JS or by yam2html
+ - perhaps use
+ - the Navigation Plugin gives you site navigation menus by convention. You
+ just define a property in your controllers to determine what actions are
+ shown and in what groups. http://www.grails.org/Navigation+Plugin
-- update the backlog
-- test reporting of svn conflicts during edit (and add to test suite, should
- be easier now not using canoo...)
+- gate-top on g8rs.net, inc. gate-server-redesign [HC]
+- upgrade CoW to Grails 1.1 [IR for a week plus HC/AR/NA as needed]
+ - and get cow+mimir+gus running in the same instance (base of gc.net)
+- more conversion of gate.ac.uk material [HC,GG,NA]
+- non-native pages like javadocs: [HC, AR, IR]
+ - any directory that now contains a file called ^.cow:raw-html^ will now
+ render any non-YAM HTML files directly (see
+ %(gatewiki.html#raw-html)). this means you can serve e.g. javadocs.
+ *BUT* it is a potentially nasty security hole... so we need to add a
+ better mechanism (and the ability to turn off the ^.cow:raw-html^ if I
+ didn't do that already?):
+ - add a list of path patterns to each wiki area, which would match either
+ files or directories (AR might know the GORM invocations? a new table
+ RawHtmlPatterns?)
+ - do an Ant API path match in PageController.show, according to config
+ settings (IR would know the Ant API call?)
+ - when a non-native HTML (see %(gatewiki.html#raw-html, the developer
+ guide discussion) path matches serve it raw as with the ^.cow:raw-html^
+ mechanism
+ - check this works for javadocs and for other gate.ac.uk pages (tao etc.)
+ - finish the documentation in the user guide at
+ %(gatewiki.html#raw-html)
+ - do we need a link back to the Wiki area from pages served raw? this
+ could be nice, but a) isn't typical, e.g. for javadocs, and b) would
+ need some munging of the page, e.g. by insertion (maybe of iframe?) just
+ after the body tag or similar. so perhaps not worth it?
+ - another (older?) note about this stuff:
+ - serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):
+ - perhaps in cow-managed svn trees we would allow something like a
+ special file called ^cow:layout.yam^ which might have entries like
+ ^non-yam-html=iframe^ or ^non-yam-html=raw^; in the first case serve
+ it in an iframe, in the second case serve it raw
-- 0.3 remaining
- - team wiki ... [MG, HC]
- - done
- - upgrade sam wiki [MG, IR]
- - tag the gatewiki repository as 0.3 [MG]
- - fix dependencies - dependent files are not being committed after changes
- [MG]
- - a daemon script that can be linked from /etc/init.d which does a
- run-prod [MG]
- - gate.ac.uk trialing [IR, MG, HC]
- - Hudson testing against the production instances - heartbeat runs on most
- servers[MG]
- - document tables / lists newlines thing [HC]
- - shift to future tasks
- - Look at Sventon proxying problems [IR]
- - gate-top on g8rs.net [HC]
- - non-native pages like javadocs: [HC, AR, IR]
- - any directory that now contains a file called ^.cow:raw-html^ will now
- render any non-YAM HTML files directly (see
- %(gatewiki.html#raw-html)). this means you can serve e.g. javadocs.
- *BUT* it is a potentially nasty security hole... so we need to add a
- better mechanism:
- - add a list of path patterns to each wiki area, which would match
- either files or directories (AR might know the GORM invocations? a
- new table RawHtmlPatterns?)
- - do an Ant API path match in PageController.show, according to config
- settings (IR would know the Ant API call?)
- - when a non-native HTML (see %(gatewiki.html#raw-html, the developer
- guide discussion) path matches serve it raw as with the
- ^.cow:raw-html^ mechanism
- - check this works for javadocs and for other gate.ac.uk pages (tao
- etc.)
- - finish the documentation in the user guide at
- %(gatewiki.html#raw-html)
- - do we need a link back to the Wiki area from pages served raw? this
- could be nice, but a) isn't typical, e.g. for javadocs, and b) would
- need some munging of the page, e.g. by insertion (maybe of iframe?)
- just after the body tag or similar. so perhaps not worth it?
+- bugs and features missing for gate.ac.uk: [from GG, comments from HC]
+ - \%contents links do not include path to current page, therefore links you
+ back to front page, i.e. http://localhost:8080/#section_0.1. rather than
+ http://localhost:8080/mydoc.html#section_0.1. [I tried to replicate this
+ but could not; I believe that a link to a bare ^#...^ anchor in any html
+ file will be relativised to the current page by the browser so I'm not
+ sure how this could be happening?]
+ - relative links in areas other than area 2 do not work because they assume
+ you are in the default area (i.e. %(page1.html) links to
+ http://localhost:8080/page1.html even if it should be
+ http://localhost:8080/page/show/4/page1.html) [I can't replicate this
+ either; again a relative link will be dealt with the browser, not the
+ server? perhaps you made a link \%(/page.html), i.e. included the /
+ yourself?]
+ - make a page containing a table with two rows, one of which is empty. Save
+ or preview results in the entire page content being dropped without
+ warning. [i.e. the error reporting seems broken; faults in table syntax
+ generate yam errors; need to look into this]
+ - if the last thing in a table is a verbatim (\%\<...\>\%) item, that thing
+ will not be verbatimised [need to check if this is in the list of known
+ yam bugs below nad if not add it]
+ - no apparent way to make a picture into a link [just upload the file and
+ link to it? if this works for you add a note to the user guide?]
+ - tables need more power if we are to use them for layout, i.e. control over
+ borders and width [I think we will do layout differently, see above. the
+ borders thing may need changing, or just the ability to set it from CSS?]
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%1 Future Tasks
-
-- Move ^cowrc.groovy^ inside ^cowrc.d^? One less thing to reconfigure when you
- want to run more than one CoW on the same machine.
-
-- Fix conflict between Quartz versions
- - Grails provides Quartz 1.6.x
- - the Quartz plugin uses 1.5.2
- - these are incompatiable
- - currently fixed by placing 1.6.1 in the quartz plugin directory
- - *THIS IS A NASTY HACK!*
-- Sventon integration
+- finish sventon integration [IR]
- proper proxying of sventon requests through a CoW controller
(/admin/sventon)
- - sventon pages contain all sorts of absolute path links:
- <a href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
- <div id="/sventon/ajax/...">
- (where _/sventon_ is the context path where sventon is deployed)
+ - sventon pages contain all sorts of absolute path links: <a
+ href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
+ <div id="/sventon/ajax/..."> (where _/sventon_ is the context path where
+ sventon is deployed)
- need to fix these up to point through cow, i.e. /sventon/repos ->
/admin/sventon/repos (for root-level CoW) or /sam/sventon/ajax ->
/sam/admin/sventon/ajax (for Cow deployed under /sam)
@@ -83,22 +100,38 @@
contextPath, so don't need to massage the JavaScript code (phew).
- when fetching the proxied content from sventon, add
;jsessionid=<session-id-from-cow> to the URLs, to keep sventon and cow
- sessions in sync. Any jsessionid in URLs generated by sventon need to be
- stripped during the HTML massaging process.
+ sessions in sync. Any jsessionid in URLs generated by sventon need to
+ be stripped during the HTML massaging process.
- once proxying works, we can link from pages direct to their history.
- - Simpler idea:
- - Remove the localhost filter, allowing direct access to /sventon, but...
- - Add a filter that checks for an object in the session before permitting
+ - simpler idea:
+ - remove the localhost filter, allowing direct access to /sventon, but...
+ - add a filter that checks for an object in the session before permitting
access.
- - This object is put in the session by CoW, posting to a URL that _is_
+ - this object is put in the session by CoW, posting to a URL that _is_
still restricted to localhost only.
+- test reporting of svn conflicts during edit (and add to test suite, should
+ be easier now not using canoo...)
+ - do some stress-testing and logic checking of concurrent editing
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%1 Future Tasks
+
+- team wiki ... [MG, HC]
+- move ^cowrc.groovy^ inside ^cowrc.d^? One less thing to reconfigure when you
+ want to run more than one CoW on the same machine.
+- fix conflict between Quartz versions
+ - Grails provides Quartz 1.6.x
+ - the Quartz plugin uses 1.5.2
+ - these are incompatiable
+ - currently fixed by placing 1.6.1 in the quartz plugin directory
+ - *THIS IS A NASTY HACK!*
- saving space in deployed instances: see %(gatewiki.html#saving-space)
- new page bug (as found by milan)
- if you put a link in an existing page to a new (non-existant) page in a
subdirectory, you should get the same error message that you get if you
try to do this via the new page form, but this doesn't work
- user guide to logging in, editing etc., revise %(gatewiki.html)
-- do some stress-testing and logic checking of concurrent editing
- regeneration
- setContext on the YamFile
- use the PageService edit-related methods for regeneration (have a fake
@@ -127,37 +160,10 @@
- trawl for security holes with ratproxy: http://code.google.com/p/ratproxy/
- better build.xml
- use the grails ant tasks
- - site-specific layout and config
- - layouts for whole wiki-areas
- - add a "areaLayoutName" to Wiki, which would reference a layout GSP in
- the site-specific plugin; PageLinkTabLib would then use this for the
- layout in that wiki area
- - layouts/navigation for specific directory trees
- - support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?
- - perhaps have them percolate down directory trees? they would need to
- be picked up by JS or by yam2html
- - example sites: gate.ac.uk or nlp.shef.ac.uk or ucu.group.shef.ac.uk or
- icon.shef.ac.uk
- - perhaps use
- - the Navigation Plugin gives you site navigation menus by convention.
- You just define a property in your controllers to determine what
- actions are shown and in what groups.
- http://www.grails.org/Navigation+Plugin
- - serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):
- - perhaps in cow-managed svn trees we would allow something like a
- special file called ^cow:layout.yam^ which might have entries like
- ^non-yam-html=iframe^ or ^non-yam-html=raw^; in the first case serve
- it in an iframe, in the second case serve it raw
- other bugs, see
http://sourceforge.net/tracker2/?func=browse&group_id=208243&atid=1004913
- titles including markup incorrectly include the markup in the html title
(e.g. \%br puts a <br/> into the title)
- - breadcrumbs: see %(http://www.useit.com/alertbox/breadcrumbs.html); a
- simple design where the directories above the current page are listed
- along with the top-level is probably enough, e.g. for the page
- doc/yam/summary.html we would have "You're here: Home > Help > Doc > Yam"
- as breadcrumbs. see also Darryl Pentz discussion in Jan on the mailing
- list.
- [CoW] dependencies
- at the moment, dependencies regeneration runs in the foreground. But
should it be a background job? background would be good e.g. overnight,
@@ -234,9 +240,6 @@
- possible optimisations of the PageService check-out-to-staging code:
- use the SVNRep API, see:
http://www.nabble.com/Re%3A-check-out-a-single-file--p15719277.html
- - PC.newpageFlow does at least one and possible two redundant calls to
- PS.analyse: can replace these by making references to flow instead of
- thisPage
- [CoW] config, DBs and other user data: CowDataArea (CDA) <HC>
- trawl for constants and put them in Config.groovy
- create roles when doing new Wiki in ApplicationBootStrap
@@ -284,7 +287,7 @@
directories). This could be changed to (a) allow a list of regular
expressions on each permission and (b) use the easier ant syntax, rather
than java regexp syntax.
-- [TAOWeb] "what we do page" <DD,VT>:
+- [GATE.ac.uk] "what we do page" <DD,VT> (or: MIMIR search):
- A JSP that displays Di/Wim's taxonomy and allows users to select one or
more concepts
- When they hit "search" these concepts then become a keyword search against
@@ -387,20 +390,6 @@
defined over sets of controllers, in the same way we do for actions:
- CowPermission(Wiki 1, directory "", controller [page, search], actions
[Read])
-- GG (Check to see if these really are bugs :)
- - \%contents links do not include path to current page, therefore links you back to
- front page, i.e. http://localhost:8080/#section_0.1. rather than
- http://localhost:8080/mydoc.html#section_0.1.
- - relative links in areas other than area 2 do not work because they assume
- you are in the default area (i.e. %(page1.html) links to
- http://localhost:8080/page1.html even if it should be http://localhost:8080/page/show/4/page1.html)
- - Make a page containing a table with two rows, one of which is empty. Save or
- preview results in the entire page content being dropped without warning.
- - If the last thing in a table is a verbatim (\%\<...\>\%) item, that thing will not
- be verbatimised
- - No apparent way to make a picture into a link
- - Tables need more power if we are to use them for layout, i.e. control over borders and
- width
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Modified: trunk/cow/doc/cow-done.html
===================================================================
--- trunk/cow/doc/cow-done.html 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-done.html 2009-07-02 16:59:48 UTC (rev 1437)
@@ -2060,4 +2060,27 @@
</ul>
</ul>
+<ul>
+<li>0.3</li>
+ <ul>
+ <li>upgrade sam wiki [MG, IR]</li>
+ <li>tag the gatewiki repository as 0.3 [MG]</li>
+ <li>fix dependencies - dependent files are not being committed after changes
+ [MG]</li>
+ <li>a daemon script that can be linked from /etc/init.d which does a run-prod
+ [MG]</li>
+ <li>gate.ac.uk trialing [IR, MG, HC]</li>
+ <li>Hudson testing against the production instances - heartbeat runs on most
+ servers[MG]</li>
+ <li>document tables / lists newlines thing [HC]</li>
+ </ul>
+</ul>
+
+<ul>
+<li>breadcrumbs: see <a class="cow-url" href="http://www.useit.com/alertbox/breadcrumbs.html">http://www.useit.com/alertbox/breadcrumbs.html</a>; a simple
+ design where the directories above the current page are listed along with
+ the top-level is probably enough, e.g. for the page doc/yam/summary.html we
+ would have "You're here: Home > Help > Doc > Yam" as breadcrumbs. see also
+ Darryl Pentz discussion in Jan on the mailing list. [NA]</li>
+</ul>
</body></html>
\ No newline at end of file
Modified: trunk/cow/doc/cow-done.yam
===================================================================
--- trunk/cow/doc/cow-done.yam 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-done.yam 2009-07-02 16:59:48 UTC (rev 1437)
@@ -1407,3 +1407,20 @@
- ^gate.ac.uk^: think further if it makes sense on gatewiki
- ^gate-top^ index and install on gate-compute2 *[Done]*
+- 0.3
+ - upgrade sam wiki [MG, IR]
+ - tag the gatewiki repository as 0.3 [MG]
+ - fix dependencies - dependent files are not being committed after changes
+ [MG]
+ - a daemon script that can be linked from /etc/init.d which does a run-prod
+ [MG]
+ - gate.ac.uk trialing [IR, MG, HC]
+ - Hudson testing against the production instances - heartbeat runs on most
+ servers[MG]
+ - document tables / lists newlines thing [HC]
+
+- breadcrumbs: see %(http://www.useit.com/alertbox/breadcrumbs.html); a simple
+ design where the directories above the current page are listed along with
+ the top-level is probably enough, e.g. for the page doc/yam/summary.html we
+ would have "You're here: Home > Help > Doc > Yam" as breadcrumbs. see also
+ Darryl Pentz discussion in Jan on the mailing list. [NA]
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
------------------------------------------------------------------------------
_______________________________________________
gatewiki-commits mailing list
gatewiki-commits@...
https://lists.sourceforge.net/lists/listinfo/gatewiki-commits
http://gatewiki.svn.sourceforge.net/gatewiki/?rev=1437&view=rev
Author: hcunningham
Date: 2009-07-02 16:59:48 +0000 (Thu, 02 Jul 2009)
Log Message:
-----------
updated the backlog
Modified Paths:
--------------
trunk/cow/doc/cow-backlog.html
trunk/cow/doc/cow-backlog.yam
trunk/cow/doc/cow-done.html
trunk/cow/doc/cow-done.yam
Modified: trunk/cow/doc/cow-backlog.html
===================================================================
--- trunk/cow/doc/cow-backlog.html 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-backlog.html 2009-07-02 16:59:48 UTC (rev 1437)
@@ -49,7 +49,7 @@
<div class="cow-contents"><h2 class="cow-heading">Contents</h2>
<p><ul>
-<li><a href="#section-1.">1. Roadmap (finalisation of version 0.3)</a></li>
+<li><a href="#section-1.">1. Roadmap (version 0.4)</a></li>
<li><a href="#section-2.">2. Future Tasks</a></li>
<li><a href="#section-3.">3. Completed Tasks</a></li>
<li><a href="#section-4.">4. Work areas</a></li>
@@ -57,97 +57,122 @@
</ul></p></div>
<!--%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-->
-<a class="cow-section-anchor" name="section-1."/><h1 class="cow-heading"><span class="cow-sec-number">1. </span>Roadmap (finalisation of version 0.3)</h1>
+<a class="cow-section-anchor" name="section-1."/><h1 class="cow-heading"><span class="cow-sec-number">1. </span>Roadmap (version 0.4)</h1>
-<p>incoming:</p>
-
<ul>
-<li>update the backlog</li>
-<li>test reporting of svn conflicts during edit (and add to test suite, should
- be easier now not using canoo...)</li>
-</ul>
-
-
-<ul>
-<li>0.3 remaining </li>
+<li>add layouts capabilities appropriate for gate.ac.uk and the lifesci work
+ [NA, HC]</li>
+ <ul>
+ <li>layouts for whole wiki-areas</li>
<ul>
- <li>team wiki ... [MG, HC]</li>
+ <li>add a "areaLayoutName" to Wiki, which would reference a layout GSP in
+ the site-specific plugin; PageLinkTabLib would then use this for the
+ layout in that wiki area</li>
</ul>
- <li>done</li>
+ <li>layouts/navigation for specific directory trees</li>
<ul>
- <li>upgrade sam wiki [MG, IR]</li>
- <li>tag the gatewiki repository as 0.3 [MG]</li>
- <li>fix dependencies - dependent files are not being committed after changes
- [MG]</li>
- <li>a daemon script that can be linked from /etc/init.d which does a
- run-prod [MG]</li>
- <li>gate.ac.uk trialing [IR, MG, HC]</li>
- <li>Hudson testing against the production instances - heartbeat runs on most
- servers[MG]</li>
- <li>document tables / lists newlines thing [HC]</li>
+ <li>support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?</li>
+ <li>perhaps have them percolate down directory trees? they would need to be
+ picked up by JS or by yam2html</li>
</ul>
- <li>shift to future tasks</li>
+ <li>perhaps use</li>
<ul>
- <li>Look at Sventon proxying problems [IR] </li>
- <li>gate-top on g8rs.net [HC] </li>
- <li>non-native pages like javadocs: [HC, AR, IR]</li>
- <ul>
- <li>any directory that now contains a file called <tt>.cow:raw-html</tt> will now
- render any non-YAM HTML files directly (see
- <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a>). this means you can serve e.g. javadocs.
- <b>BUT</b> it is a potentially nasty security hole... so we need to add a
- better mechanism:</li>
- <ul>
- <li>add a list of path patterns to each wiki area, which would match
- either files or directories (AR might know the GORM invocations? a
- new table RawHtmlPatterns?)</li>
- <li>do an Ant API path match in PageController.show, according to config
- settings (IR would know the Ant API call?)</li>
- <li>when a non-native HTML (see <a class="cow-url" href="gatewiki.html#raw-html">the developer
- guide discussion</a> path matches serve it raw as with the
- <tt>.cow:raw-html</tt> mechanism</li>
- <li>check this works for javadocs and for other gate.ac.uk pages (tao
- etc.)</li>
- <li>finish the documentation in the user guide at
- <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a></li>
- <li>do we need a link back to the Wiki area from pages served raw? this
- could be nice, but a) isn't typical, e.g. for javadocs, and b) would
- need some munging of the page, e.g. by insertion (maybe of iframe?)
- just after the body tag or similar. so perhaps not worth it?</li>
- </ul>
- </ul>
+ <li>the Navigation Plugin gives you site navigation menus by convention. You
+ just define a property in your controllers to determine what actions are
+ shown and in what groups. <a class="cow-url" href="http://www.grails.org/Navigation+Plugin">http://www.grails.org/Navigation+Plugin</a></li>
</ul>
+ </ul>
</ul>
-
-<!--%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-->
-<a class="cow-section-anchor" name="section-2."/><h1 class="cow-heading"><span class="cow-sec-number">2. </span>Future Tasks</h1>
-
<ul>
-<li>Move <tt>cowrc.groovy</tt> inside <tt>cowrc.d</tt>? One less thing to reconfigure when you
- want to run more than one CoW on the same machine.</li>
+<li>gate-top on g8rs.net, inc. gate-server-redesign [HC] </li>
+<li>upgrade CoW to Grails 1.1 [IR for a week plus HC/AR/NA as needed]</li>
+ <ul>
+ <li>and get cow+mimir+gus running in the same instance (base of gc.net)</li>
+ </ul>
+<li>more conversion of gate.ac.uk material [HC,GG,NA]</li>
</ul>
<ul>
-<li>Fix conflict between Quartz versions</li>
+<li>non-native pages like javadocs: [HC, AR, IR]</li>
<ul>
- <li>Grails provides Quartz 1.6.x</li>
- <li>the Quartz plugin uses 1.5.2</li>
- <li>these are incompatiable</li>
+ <li>any directory that now contains a file called <tt>.cow:raw-html</tt> will now
+ render any non-YAM HTML files directly (see
+ <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a>). this means you can serve e.g. javadocs.
+ <b>BUT</b> it is a potentially nasty security hole... so we need to add a
+ better mechanism (and the ability to turn off the <tt>.cow:raw-html</tt> if I
+ didn't do that already?):</li>
<ul>
- <li>currently fixed by placing 1.6.1 in the quartz plugin directory</li>
- <li><b>THIS IS A NASTY HACK!</b></li>
+ <li>add a list of path patterns to each wiki area, which would match either
+ files or directories (AR might know the GORM invocations? a new table
+ RawHtmlPatterns?)</li>
+ <li>do an Ant API path match in PageController.show, according to config
+ settings (IR would know the Ant API call?)</li>
+ <li>when a non-native HTML (see <a class="cow-url" href="gatewiki.html#raw-html">the developer
+ guide discussion</a> path matches serve it raw as with the <tt>.cow:raw-html</tt>
+ mechanism</li>
+ <li>check this works for javadocs and for other gate.ac.uk pages (tao etc.)</li>
+ <li>finish the documentation in the user guide at
+ <a class="cow-url" href="gatewiki.html#raw-html">gatewiki.html#raw-html</a></li>
+ <li>do we need a link back to the Wiki area from pages served raw? this
+ could be nice, but a) isn't typical, e.g. for javadocs, and b) would
+ need some munging of the page, e.g. by insertion (maybe of iframe?) just
+ after the body tag or similar. so perhaps not worth it?</li>
</ul>
+ <li>another (older?) note about this stuff:</li>
+ <ul>
+ <li>serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):</li>
+ <ul>
+ <li>perhaps in cow-managed svn trees we would allow something like a
+ special file called <tt>cow:layout.yam</tt> which might have entries like
+ <tt>non-yam-html=iframe</tt> or <tt>non-yam-html=raw</tt>; in the first case serve
+ it in an iframe, in the second case serve it raw</li>
+ </ul>
+ </ul>
</ul>
-<li>Sventon integration</li>
+</ul>
+
+<ul>
+<li>bugs and features missing for gate.ac.uk: [from GG, comments from HC]</li>
<ul>
+ <li><span class="cow-escape">%</span>contents links do not include path to current page, therefore links you
+ back to front page, i.e. <a class="cow-url" href="http://localhost:8080/#section_0.1.">http://localhost:8080/#section_0.1.</a> rather than
+ <a class="cow-url" href="http://localhost:8080/mydoc.html#section_0.1.">http://localhost:8080/mydoc.html#section_0.1.</a> [I tried to replicate this
+ but could not; I believe that a link to a bare <tt>#...</tt> anchor in any html
+ file will be relativised to the current page by the browser so I'm not
+ sure how this could be happening?]</li>
+ <li>relative links in areas other than area 2 do not work because they assume
+ you are in the default area (i.e. <a class="cow-non-existant-url" href="page1.html">page1.html</a> links to
+ <a class="cow-url" href="http://localhost:8080/page1.html">http://localhost:8080/page1.html</a> even if it should be
+ <a class="cow-url" href="http://localhost:8080/page/show/4/page1.html)">http://localhost:8080/page/show/4/page1.html)</a> [I can't replicate this
+ either; again a relative link will be dealt with the browser, not the
+ server? perhaps you made a link <span class="cow-escape">%</span>(/page.html), i.e. included the /
+ yourself?]</li>
+ <li>make a page containing a table with two rows, one of which is empty. Save
+ or preview results in the entire page content being dropped without
+ warning. [i.e. the error reporting seems broken; faults in table syntax
+ generate yam errors; need to look into this]</li>
+ <li>if the last thing in a table is a verbatim (<span class="cow-escape">%</span><span class="cow-escape"><</span>...<span class="cow-escape">></span><span class="cow-escape">%</span>) item, that thing
+ will not be verbatimised [need to check if this is in the list of known
+ yam bugs below nad if not add it]</li>
+ <li>no apparent way to make a picture into a link [just upload the file and
+ link to it? if this works for you add a note to the user guide?]</li>
+ <li>tables need more power if we are to use them for layout, i.e. control over
+ borders and width [I think we will do layout differently, see above. the
+ borders thing may need changing, or just the ability to set it from CSS?]</li>
+ </ul>
+</ul>
+
+<ul>
+<li>finish sventon integration [IR]</li>
+ <ul>
<li>proper proxying of sventon requests through a CoW controller
(/admin/sventon)</li>
<ul>
- <li>sventon pages contain all sorts of absolute path links:
- <a href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
- <div id="/sventon/ajax/...">
- (where <em>/sventon</em> is the context path where sventon is deployed)</li>
+ <li>sventon pages contain all sorts of absolute path links: <a
+ href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
+ <div id="/sventon/ajax/..."> (where <em>/sventon</em> is the context path where
+ sventon is deployed)</li>
<li>need to fix these up to point through cow, i.e. /sventon/repos ->
/admin/sventon/repos (for root-level CoW) or /sam/sventon/ajax ->
/sam/admin/sventon/ajax (for Cow deployed under /sam)</li>
@@ -158,19 +183,44 @@
contextPath, so don't need to massage the JavaScript code (phew).</li>
<li>when fetching the proxied content from sventon, add
;jsessionid=<session-id-from-cow> to the URLs, to keep sventon and cow
- sessions in sync. Any jsessionid in URLs generated by sventon need to be
- stripped during the HTML massaging process.</li>
+ sessions in sync. Any jsessionid in URLs generated by sventon need to
+ be stripped during the HTML massaging process.</li>
</ul>
<li>once proxying works, we can link from pages direct to their history.</li>
- <li>Simpler idea:</li>
+ <li>simpler idea:</li>
<ul>
- <li>Remove the localhost filter, allowing direct access to /sventon, but...</li>
- <li>Add a filter that checks for an object in the session before permitting
+ <li>remove the localhost filter, allowing direct access to /sventon, but...</li>
+ <li>add a filter that checks for an object in the session before permitting
access.</li>
- <li>This object is put in the session by CoW, posting to a URL that <em>is</em>
+ <li>this object is put in the session by CoW, posting to a URL that <em>is</em>
still restricted to localhost only.</li>
</ul>
</ul>
+<li>test reporting of svn conflicts during edit (and add to test suite, should
+ be easier now not using canoo...)</li>
+ <ul>
+ <li>do some stress-testing and logic checking of concurrent editing</li>
+ </ul>
+</ul>
+
+
+<!--%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-->
+<a class="cow-section-anchor" name="section-2."/><h1 class="cow-heading"><span class="cow-sec-number">2. </span>Future Tasks</h1>
+
+<ul>
+<li>team wiki ... [MG, HC]</li>
+<li>move <tt>cowrc.groovy</tt> inside <tt>cowrc.d</tt>? One less thing to reconfigure when you
+ want to run more than one CoW on the same machine.</li>
+<li>fix conflict between Quartz versions</li>
+ <ul>
+ <li>Grails provides Quartz 1.6.x</li>
+ <li>the Quartz plugin uses 1.5.2</li>
+ <li>these are incompatiable</li>
+ <ul>
+ <li>currently fixed by placing 1.6.1 in the quartz plugin directory</li>
+ <li><b>THIS IS A NASTY HACK!</b></li>
+ </ul>
+ </ul>
<li>saving space in deployed instances: see <a class="cow-url" href="gatewiki.html#saving-space">gatewiki.html#saving-space</a></li>
<li>new page bug (as found by milan)</li>
<ul>
@@ -179,7 +229,6 @@
try to do this via the new page form, but this doesn't work</li>
</ul>
<li>user guide to logging in, editing etc., revise <a class="cow-url" href="gatewiki.html">gatewiki.html</a></li>
-<li>do some stress-testing and logic checking of concurrent editing</li>
<li>regeneration</li>
<ul>
<li>setContext on the YamFile</li>
@@ -221,49 +270,12 @@
<ul>
<li>use the grails ant tasks</li>
</ul>
- <li>site-specific layout and config</li>
- <ul>
- <li>layouts for whole wiki-areas</li>
- <ul>
- <li>add a "areaLayoutName" to Wiki, which would reference a layout GSP in
- the site-specific plugin; PageLinkTabLib would then use this for the
- layout in that wiki area</li>
- </ul>
- <li>layouts/navigation for specific directory trees</li>
- <ul>
- <li>support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?</li>
- <li>perhaps have them percolate down directory trees? they would need to
- be picked up by JS or by yam2html</li>
- <li>example sites: gate.ac.uk or nlp.shef.ac.uk or ucu.group.shef.ac.uk or
- icon.shef.ac.uk</li>
- <li>perhaps use</li>
- <ul>
- <li>the Navigation Plugin gives you site navigation menus by convention.
- You just define a property in your controllers to determine what
- actions are shown and in what groups.
- <a class="cow-url" href="http://www.grails.org/Navigation+Plugin">http://www.grails.org/Navigation+Plugin</a></li>
- </ul>
- </ul>
- <li>serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):</li>
- <ul>
- <li>perhaps in cow-managed svn trees we would allow something like a
- special file called <tt>cow:layout.yam</tt> which might have entries like
- <tt>non-yam-html=iframe</tt> or <tt>non-yam-html=raw</tt>; in the first case serve
- it in an iframe, in the second case serve it raw</li>
- </ul>
- </ul>
<li>other bugs, see
<a class="cow-url" href="http://sourceforge.net/tracker2/?func=browse&group_id=208243&atid=1004913">http://sourceforge.net/tracker2/?func=browse&group_id=208243&atid=1004913</a></li>
<ul>
<li>titles including markup incorrectly include the markup in the html title
(e.g. <span class="cow-escape">%</span>br puts a <br/> into the title)</li>
</ul>
- <li>breadcrumbs: see <a class="cow-url" href="http://www.useit.com/alertbox/breadcrumbs.html">http://www.useit.com/alertbox/breadcrumbs.html</a>; a
- simple design where the directories above the current page are listed
- along with the top-level is probably enough, e.g. for the page
- doc/yam/summary.html we would have "You're here: Home > Help > Doc > Yam"
- as breadcrumbs. see also Darryl Pentz discussion in Jan on the mailing
- list.</li>
</ul>
<li>[CoW] dependencies</li>
<ul>
@@ -372,9 +384,6 @@
<li>use the SVNRep API, see:
<a class="cow-url" href="http://www.nabble.com/Re%3A-check-out-a-single-file--p15719277.html">http://www.nabble.com/Re%3A-check-out-a-single-file--p15719277.html</a></li>
</ul>
- <li>PC.newpageFlow does at least one and possible two redundant calls to
- PS.analyse: can replace these by making references to flow instead of
- thisPage</li>
</ul>
<li>[CoW] config, DBs and other user data: CowDataArea (CDA) <HC></li>
<ul>
@@ -435,7 +444,7 @@
expressions on each permission and (b) use the easier ant syntax, rather
than java regexp syntax.</li>
</ul>
-<li>[TAOWeb] "what we do page" <DD,VT>:</li>
+<li>[GATE.ac.uk] "what we do page" <DD,VT> (or: MIMIR search):</li>
<ul>
<li>A JSP that displays Di/Wim's taxonomy and allows users to select one or
more concepts</li>
@@ -562,22 +571,6 @@
<li>CowPermission(Wiki 1, directory "", controller [page, search], actions
[Read])</li>
</ul>
-<li>GG (Check to see if these really are bugs :)</li>
- <ul>
- <li><span class="cow-escape">%</span>contents links do not include path to current page, therefore links you back to
- front page, i.e. <a class="cow-url" href="http://localhost:8080/#section_0.1.">http://localhost:8080/#section_0.1.</a> rather than
- <a class="cow-url" href="http://localhost:8080/mydoc.html#section_0.1.">http://localhost:8080/mydoc.html#section_0.1.</a></li>
- <li>relative links in areas other than area 2 do not work because they assume
- you are in the default area (i.e. <a class="cow-non-existant-url" href="page1.html">page1.html</a> links to
- <a class="cow-url" href="http://localhost:8080/page1.html">http://localhost:8080/page1.html</a> even if it should be <a class="cow-url" href="http://localhost:8080/page/show/4/page1.html)">http://localhost:8080/page/show/4/page1.html)</a></li>
- <li>Make a page containing a table with two rows, one of which is empty. Save or
- preview results in the entire page content being dropped without warning.</li>
- <li>If the last thing in a table is a verbatim (<span class="cow-escape">%</span><span class="cow-escape"><</span>...<span class="cow-escape">></span><span class="cow-escape">%</span>) item, that thing will not
- be verbatimised</li>
- <li>No apparent way to make a picture into a link</li>
- <li>Tables need more power if we are to use them for layout, i.e. control over borders and
- width</li>
- </ul>
</ul>
Modified: trunk/cow/doc/cow-backlog.yam
===================================================================
--- trunk/cow/doc/cow-backlog.yam 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-backlog.yam 2009-07-02 16:59:48 UTC (rev 1437)
@@ -5,74 +5,91 @@
%contents
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%1 Roadmap (finalisation of version 0.3)
+%1 Roadmap (version 0.4)
-incoming:
+- add layouts capabilities appropriate for gate.ac.uk and the lifesci work
+ [NA, HC]
+ - layouts for whole wiki-areas
+ - add a "areaLayoutName" to Wiki, which would reference a layout GSP in
+ the site-specific plugin; PageLinkTabLib would then use this for the
+ layout in that wiki area
+ - layouts/navigation for specific directory trees
+ - support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?
+ - perhaps have them percolate down directory trees? they would need to be
+ picked up by JS or by yam2html
+ - perhaps use
+ - the Navigation Plugin gives you site navigation menus by convention. You
+ just define a property in your controllers to determine what actions are
+ shown and in what groups. http://www.grails.org/Navigation+Plugin
-- update the backlog
-- test reporting of svn conflicts during edit (and add to test suite, should
- be easier now not using canoo...)
+- gate-top on g8rs.net, inc. gate-server-redesign [HC]
+- upgrade CoW to Grails 1.1 [IR for a week plus HC/AR/NA as needed]
+ - and get cow+mimir+gus running in the same instance (base of gc.net)
+- more conversion of gate.ac.uk material [HC,GG,NA]
+- non-native pages like javadocs: [HC, AR, IR]
+ - any directory that now contains a file called ^.cow:raw-html^ will now
+ render any non-YAM HTML files directly (see
+ %(gatewiki.html#raw-html)). this means you can serve e.g. javadocs.
+ *BUT* it is a potentially nasty security hole... so we need to add a
+ better mechanism (and the ability to turn off the ^.cow:raw-html^ if I
+ didn't do that already?):
+ - add a list of path patterns to each wiki area, which would match either
+ files or directories (AR might know the GORM invocations? a new table
+ RawHtmlPatterns?)
+ - do an Ant API path match in PageController.show, according to config
+ settings (IR would know the Ant API call?)
+ - when a non-native HTML (see %(gatewiki.html#raw-html, the developer
+ guide discussion) path matches serve it raw as with the ^.cow:raw-html^
+ mechanism
+ - check this works for javadocs and for other gate.ac.uk pages (tao etc.)
+ - finish the documentation in the user guide at
+ %(gatewiki.html#raw-html)
+ - do we need a link back to the Wiki area from pages served raw? this
+ could be nice, but a) isn't typical, e.g. for javadocs, and b) would
+ need some munging of the page, e.g. by insertion (maybe of iframe?) just
+ after the body tag or similar. so perhaps not worth it?
+ - another (older?) note about this stuff:
+ - serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):
+ - perhaps in cow-managed svn trees we would allow something like a
+ special file called ^cow:layout.yam^ which might have entries like
+ ^non-yam-html=iframe^ or ^non-yam-html=raw^; in the first case serve
+ it in an iframe, in the second case serve it raw
-- 0.3 remaining
- - team wiki ... [MG, HC]
- - done
- - upgrade sam wiki [MG, IR]
- - tag the gatewiki repository as 0.3 [MG]
- - fix dependencies - dependent files are not being committed after changes
- [MG]
- - a daemon script that can be linked from /etc/init.d which does a
- run-prod [MG]
- - gate.ac.uk trialing [IR, MG, HC]
- - Hudson testing against the production instances - heartbeat runs on most
- servers[MG]
- - document tables / lists newlines thing [HC]
- - shift to future tasks
- - Look at Sventon proxying problems [IR]
- - gate-top on g8rs.net [HC]
- - non-native pages like javadocs: [HC, AR, IR]
- - any directory that now contains a file called ^.cow:raw-html^ will now
- render any non-YAM HTML files directly (see
- %(gatewiki.html#raw-html)). this means you can serve e.g. javadocs.
- *BUT* it is a potentially nasty security hole... so we need to add a
- better mechanism:
- - add a list of path patterns to each wiki area, which would match
- either files or directories (AR might know the GORM invocations? a
- new table RawHtmlPatterns?)
- - do an Ant API path match in PageController.show, according to config
- settings (IR would know the Ant API call?)
- - when a non-native HTML (see %(gatewiki.html#raw-html, the developer
- guide discussion) path matches serve it raw as with the
- ^.cow:raw-html^ mechanism
- - check this works for javadocs and for other gate.ac.uk pages (tao
- etc.)
- - finish the documentation in the user guide at
- %(gatewiki.html#raw-html)
- - do we need a link back to the Wiki area from pages served raw? this
- could be nice, but a) isn't typical, e.g. for javadocs, and b) would
- need some munging of the page, e.g. by insertion (maybe of iframe?)
- just after the body tag or similar. so perhaps not worth it?
+- bugs and features missing for gate.ac.uk: [from GG, comments from HC]
+ - \%contents links do not include path to current page, therefore links you
+ back to front page, i.e. http://localhost:8080/#section_0.1. rather than
+ http://localhost:8080/mydoc.html#section_0.1. [I tried to replicate this
+ but could not; I believe that a link to a bare ^#...^ anchor in any html
+ file will be relativised to the current page by the browser so I'm not
+ sure how this could be happening?]
+ - relative links in areas other than area 2 do not work because they assume
+ you are in the default area (i.e. %(page1.html) links to
+ http://localhost:8080/page1.html even if it should be
+ http://localhost:8080/page/show/4/page1.html) [I can't replicate this
+ either; again a relative link will be dealt with the browser, not the
+ server? perhaps you made a link \%(/page.html), i.e. included the /
+ yourself?]
+ - make a page containing a table with two rows, one of which is empty. Save
+ or preview results in the entire page content being dropped without
+ warning. [i.e. the error reporting seems broken; faults in table syntax
+ generate yam errors; need to look into this]
+ - if the last thing in a table is a verbatim (\%\<...\>\%) item, that thing
+ will not be verbatimised [need to check if this is in the list of known
+ yam bugs below nad if not add it]
+ - no apparent way to make a picture into a link [just upload the file and
+ link to it? if this works for you add a note to the user guide?]
+ - tables need more power if we are to use them for layout, i.e. control over
+ borders and width [I think we will do layout differently, see above. the
+ borders thing may need changing, or just the ability to set it from CSS?]
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%1 Future Tasks
-
-- Move ^cowrc.groovy^ inside ^cowrc.d^? One less thing to reconfigure when you
- want to run more than one CoW on the same machine.
-
-- Fix conflict between Quartz versions
- - Grails provides Quartz 1.6.x
- - the Quartz plugin uses 1.5.2
- - these are incompatiable
- - currently fixed by placing 1.6.1 in the quartz plugin directory
- - *THIS IS A NASTY HACK!*
-- Sventon integration
+- finish sventon integration [IR]
- proper proxying of sventon requests through a CoW controller
(/admin/sventon)
- - sventon pages contain all sorts of absolute path links:
- <a href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
- <div id="/sventon/ajax/...">
- (where _/sventon_ is the context path where sventon is deployed)
+ - sventon pages contain all sorts of absolute path links: <a
+ href="/sventon/repos/...">, <script src="/sventon/js/sventon.js" />,
+ <div id="/sventon/ajax/..."> (where _/sventon_ is the context path where
+ sventon is deployed)
- need to fix these up to point through cow, i.e. /sventon/repos ->
/admin/sventon/repos (for root-level CoW) or /sam/sventon/ajax ->
/sam/admin/sventon/ajax (for Cow deployed under /sam)
@@ -83,22 +100,38 @@
contextPath, so don't need to massage the JavaScript code (phew).
- when fetching the proxied content from sventon, add
;jsessionid=<session-id-from-cow> to the URLs, to keep sventon and cow
- sessions in sync. Any jsessionid in URLs generated by sventon need to be
- stripped during the HTML massaging process.
+ sessions in sync. Any jsessionid in URLs generated by sventon need to
+ be stripped during the HTML massaging process.
- once proxying works, we can link from pages direct to their history.
- - Simpler idea:
- - Remove the localhost filter, allowing direct access to /sventon, but...
- - Add a filter that checks for an object in the session before permitting
+ - simpler idea:
+ - remove the localhost filter, allowing direct access to /sventon, but...
+ - add a filter that checks for an object in the session before permitting
access.
- - This object is put in the session by CoW, posting to a URL that _is_
+ - this object is put in the session by CoW, posting to a URL that _is_
still restricted to localhost only.
+- test reporting of svn conflicts during edit (and add to test suite, should
+ be easier now not using canoo...)
+ - do some stress-testing and logic checking of concurrent editing
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%1 Future Tasks
+
+- team wiki ... [MG, HC]
+- move ^cowrc.groovy^ inside ^cowrc.d^? One less thing to reconfigure when you
+ want to run more than one CoW on the same machine.
+- fix conflict between Quartz versions
+ - Grails provides Quartz 1.6.x
+ - the Quartz plugin uses 1.5.2
+ - these are incompatiable
+ - currently fixed by placing 1.6.1 in the quartz plugin directory
+ - *THIS IS A NASTY HACK!*
- saving space in deployed instances: see %(gatewiki.html#saving-space)
- new page bug (as found by milan)
- if you put a link in an existing page to a new (non-existant) page in a
subdirectory, you should get the same error message that you get if you
try to do this via the new page form, but this doesn't work
- user guide to logging in, editing etc., revise %(gatewiki.html)
-- do some stress-testing and logic checking of concurrent editing
- regeneration
- setContext on the YamFile
- use the PageService edit-related methods for regeneration (have a fake
@@ -127,37 +160,10 @@
- trawl for security holes with ratproxy: http://code.google.com/p/ratproxy/
- better build.xml
- use the grails ant tasks
- - site-specific layout and config
- - layouts for whole wiki-areas
- - add a "areaLayoutName" to Wiki, which would reference a layout GSP in
- the site-specific plugin; PageLinkTabLib would then use this for the
- layout in that wiki area
- - layouts/navigation for specific directory trees
- - support cow:top-bar.yam, cow:left-bar.yam etc. in the wiki SVN trees?
- - perhaps have them percolate down directory trees? they would need to
- be picked up by JS or by yam2html
- - example sites: gate.ac.uk or nlp.shef.ac.uk or ucu.group.shef.ac.uk or
- icon.shef.ac.uk
- - perhaps use
- - the Navigation Plugin gives you site navigation menus by convention.
- You just define a property in your controllers to determine what
- actions are shown and in what groups.
- http://www.grails.org/Navigation+Plugin
- - serving HTML that shouldn't be modified by cow (e.g. javadoc, the TAO):
- - perhaps in cow-managed svn trees we would allow something like a
- special file called ^cow:layout.yam^ which might have entries like
- ^non-yam-html=iframe^ or ^non-yam-html=raw^; in the first case serve
- it in an iframe, in the second case serve it raw
- other bugs, see
http://sourceforge.net/tracker2/?func=browse&group_id=208243&atid=1004913
- titles including markup incorrectly include the markup in the html title
(e.g. \%br puts a <br/> into the title)
- - breadcrumbs: see %(http://www.useit.com/alertbox/breadcrumbs.html); a
- simple design where the directories above the current page are listed
- along with the top-level is probably enough, e.g. for the page
- doc/yam/summary.html we would have "You're here: Home > Help > Doc > Yam"
- as breadcrumbs. see also Darryl Pentz discussion in Jan on the mailing
- list.
- [CoW] dependencies
- at the moment, dependencies regeneration runs in the foreground. But
should it be a background job? background would be good e.g. overnight,
@@ -234,9 +240,6 @@
- possible optimisations of the PageService check-out-to-staging code:
- use the SVNRep API, see:
http://www.nabble.com/Re%3A-check-out-a-single-file--p15719277.html
- - PC.newpageFlow does at least one and possible two redundant calls to
- PS.analyse: can replace these by making references to flow instead of
- thisPage
- [CoW] config, DBs and other user data: CowDataArea (CDA) <HC>
- trawl for constants and put them in Config.groovy
- create roles when doing new Wiki in ApplicationBootStrap
@@ -284,7 +287,7 @@
directories). This could be changed to (a) allow a list of regular
expressions on each permission and (b) use the easier ant syntax, rather
than java regexp syntax.
-- [TAOWeb] "what we do page" <DD,VT>:
+- [GATE.ac.uk] "what we do page" <DD,VT> (or: MIMIR search):
- A JSP that displays Di/Wim's taxonomy and allows users to select one or
more concepts
- When they hit "search" these concepts then become a keyword search against
@@ -387,20 +390,6 @@
defined over sets of controllers, in the same way we do for actions:
- CowPermission(Wiki 1, directory "", controller [page, search], actions
[Read])
-- GG (Check to see if these really are bugs :)
- - \%contents links do not include path to current page, therefore links you back to
- front page, i.e. http://localhost:8080/#section_0.1. rather than
- http://localhost:8080/mydoc.html#section_0.1.
- - relative links in areas other than area 2 do not work because they assume
- you are in the default area (i.e. %(page1.html) links to
- http://localhost:8080/page1.html even if it should be http://localhost:8080/page/show/4/page1.html)
- - Make a page containing a table with two rows, one of which is empty. Save or
- preview results in the entire page content being dropped without warning.
- - If the last thing in a table is a verbatim (\%\<...\>\%) item, that thing will not
- be verbatimised
- - No apparent way to make a picture into a link
- - Tables need more power if we are to use them for layout, i.e. control over borders and
- width
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Modified: trunk/cow/doc/cow-done.html
===================================================================
--- trunk/cow/doc/cow-done.html 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-done.html 2009-07-02 16:59:48 UTC (rev 1437)
@@ -2060,4 +2060,27 @@
</ul>
</ul>
+<ul>
+<li>0.3</li>
+ <ul>
+ <li>upgrade sam wiki [MG, IR]</li>
+ <li>tag the gatewiki repository as 0.3 [MG]</li>
+ <li>fix dependencies - dependent files are not being committed after changes
+ [MG]</li>
+ <li>a daemon script that can be linked from /etc/init.d which does a run-prod
+ [MG]</li>
+ <li>gate.ac.uk trialing [IR, MG, HC]</li>
+ <li>Hudson testing against the production instances - heartbeat runs on most
+ servers[MG]</li>
+ <li>document tables / lists newlines thing [HC]</li>
+ </ul>
+</ul>
+
+<ul>
+<li>breadcrumbs: see <a class="cow-url" href="http://www.useit.com/alertbox/breadcrumbs.html">http://www.useit.com/alertbox/breadcrumbs.html</a>; a simple
+ design where the directories above the current page are listed along with
+ the top-level is probably enough, e.g. for the page doc/yam/summary.html we
+ would have "You're here: Home > Help > Doc > Yam" as breadcrumbs. see also
+ Darryl Pentz discussion in Jan on the mailing list. [NA]</li>
+</ul>
</body></html>
\ No newline at end of file
Modified: trunk/cow/doc/cow-done.yam
===================================================================
--- trunk/cow/doc/cow-done.yam 2009-07-02 11:09:57 UTC (rev 1436)
+++ trunk/cow/doc/cow-done.yam 2009-07-02 16:59:48 UTC (rev 1437)
@@ -1407,3 +1407,20 @@
- ^gate.ac.uk^: think further if it makes sense on gatewiki
- ^gate-top^ index and install on gate-compute2 *[Done]*
+- 0.3
+ - upgrade sam wiki [MG, IR]
+ - tag the gatewiki repository as 0.3 [MG]
+ - fix dependencies - dependent files are not being committed after changes
+ [MG]
+ - a daemon script that can be linked from /etc/init.d which does a run-prod
+ [MG]
+ - gate.ac.uk trialing [IR, MG, HC]
+ - Hudson testing against the production instances - heartbeat runs on most
+ servers[MG]
+ - document tables / lists newlines thing [HC]
+
+- breadcrumbs: see %(http://www.useit.com/alertbox/breadcrumbs.html); a simple
+ design where the directories above the current page are listed along with
+ the top-level is probably enough, e.g. for the page doc/yam/summary.html we
+ would have "You're here: Home > Help > Doc > Yam" as breadcrumbs. see also
+ Darryl Pentz discussion in Jan on the mailing list. [NA]
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
------------------------------------------------------------------------------
_______________________________________________
gatewiki-commits mailing list
gatewiki-commits@...
https://lists.sourceforge.net/lists/listinfo/gatewiki-commits
« Return to Thread: [gatewiki-commits] SF.net SVN: gatewiki:[1437] trunk/cow/doc
| Free embeddable forum powered by Nabble | Forum Help |
