Revision: 1462
http://gatewiki.svn.sourceforge.net/gatewiki/?rev=1462&view=revAuthor: hcunningham
Date: 2009-07-06 16:12:09 +0000 (Mon, 06 Jul 2009)
Log Message:
-----------
a bit more on layouts etc.
Modified Paths:
--------------
trunk/cow/doc/cow-backlog.html
trunk/cow/doc/cow-backlog.yam
Modified: trunk/cow/doc/cow-backlog.html
===================================================================
--- trunk/cow/doc/cow-backlog.html 2009-07-06 15:57:20 UTC (rev 1461)
+++ trunk/cow/doc/cow-backlog.html 2009-07-06 16:12:09 UTC (rev 1462)
@@ -69,7 +69,10 @@
<li>add layouts capabilities appropriate for gate.ac.uk and the lifesci work
[NA, HC]</li>
<ul>
- <li>note about where to implement this:</li>
+ <li>design: we're providing navigation (sets of links) that can be tailored on
+ a per-area or per-directory basis, plus layout (css, header structure,
+ etc.) on a per-site or per-area basis</li>
+ <li>navigation for specific directory trees [HC]</li>
<ul>
<li>this should all be dealt with at rendering time. otherwise we lose the
ability to work with YAM files outside of CoW. so at the place where CoW
@@ -89,12 +92,9 @@
</ul>
</ul>
</ul>
+ <li>names: cow:top-bar.yam, cow:left-bar.yam ?</li>
</ul>
- </ul>
-</ul>
-
- <ul>
- <li>layouts for whole wiki-areas</li>
+ <li>layouts for whole wiki-areas [NA]</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
@@ -104,20 +104,15 @@
Bootstrap in fact, and store the list of them in a config var, just like
setGuestLayoutPath() does when called from Bootstrap now</li>
</ul>
- <li>layouts/navigation for specific directory trees</li>
+ <li>other layout issues: [?]</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>
- </ul>
- <li>other layout issues:</li>
- <ul>
<li>don't show any layout or navigation if "?print=true"</li>
<li>give an id to tables so that we can easily control the default border
setting from the CSS, and verify that plugins / layouts can override the
default border created by yam2html</li>
</ul>
</ul>
+</ul>
<ul>
<li>gate-top on g8rs.net, inc. gate-server-redesign [HC] </li>
@@ -129,7 +124,7 @@
</ul>
<ul>
-<li>non-native pages like javadocs: [HC, AR, IR]</li>
+<li>non-native pages like javadocs: [NA, 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
@@ -153,16 +148,6 @@
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>
</ul>
@@ -247,14 +232,15 @@
</ul>
<ul>
-<li>edit cancellations should delete the staging copy</li>
+<li>edit cancellations should delete the staging copy, like Ian did previously</li>
</ul>
<ul>
<li>the g:paginate call in jsecUserRoleMappings/listByRole.gsp needs an id param
- adding</li>
+ adding ant -Dgate.cow.grails.command="install-plugin
+ /data/herd/gate-top/externals/gatewiki/site-plugins/grails-gate2-0.1.zip"
+ grails</li>
</ul>
-<p>ant -Dgate.cow.grails.command="install-plugin /data/herd/gate-top/externals/gatewiki/site-plugins/grails-gate2-0.1.zip" grails</p>
<!--%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-->
Modified: trunk/cow/doc/cow-backlog.yam
===================================================================
--- trunk/cow/doc/cow-backlog.yam 2009-07-06 15:57:20 UTC (rev 1461)
+++ trunk/cow/doc/cow-backlog.yam 2009-07-06 16:12:09 UTC (rev 1462)
@@ -13,7 +13,10 @@
- add layouts capabilities appropriate for gate.ac.uk and the lifesci work
[NA, HC]
- - note about where to implement this:
+ - design: we're providing navigation (sets of links) that can be tailored on
+ a per-area or per-directory basis, plus layout (css, header structure,
+ etc.) on a per-site or per-area basis
+ - navigation for specific directory trees [HC]
- this should all be dealt with at rendering time. otherwise we lose the
ability to work with YAM files outside of CoW. so at the place where CoW
reads the body of a YAM-derived HTML file it should also be given a) the
@@ -26,8 +29,8 @@
FU.getBody called over any available layout info from the wiki
- for each layout file in conf.navigation.files
- find the nearest one to current dir, up the tree to wiki top
-
- - layouts for whole wiki-areas
+ - names: cow:top-bar.yam, cow:left-bar.yam ?
+ - layouts for whole wiki-areas [NA]
- 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
@@ -35,11 +38,7 @@
- the check to see which area layouts are present should be done in
Bootstrap in fact, and store the list of them in a config var, just like
setGuestLayoutPath() does when called from Bootstrap now
- - 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
- - other layout issues:
+ - other layout issues: [?]
- don't show any layout or navigation if "?print=true"
- give an id to tables so that we can easily control the default border
setting from the CSS, and verify that plugins / layouts can override the
@@ -50,7 +49,7 @@
- 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]
+- non-native pages like javadocs: [NA, 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.
@@ -71,12 +70,6 @@
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
- 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
@@ -140,11 +133,12 @@
(org.tmatesoft.svn.core.SVNException: svn: CowAuthenticationManager only
provides a single authentication token) but it isn't reported to the user
-- edit cancellations should delete the staging copy
+- edit cancellations should delete the staging copy, like Ian did previously
- the g:paginate call in jsecUserRoleMappings/listByRole.gsp needs an id param
- adding
-ant -Dgate.cow.grails.command="install-plugin /data/herd/gate-top/externals/gatewiki/site-plugins/grails-gate2-0.1.zip" grails
+ adding ant -Dgate.cow.grails.command="install-plugin
+ /data/herd/gate-top/externals/gatewiki/site-plugins/grails-gate2-0.1.zip"
+ grails
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
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