Adam R. B. Jack wrote:
If it is ok with all, I'd like to wait until I get a CVS id before I
continue. I have a script gumpy.sh that (1) updates gump from CVS [getting
latest Python code] (2) runs integrate (which checks environment/loads
workspace/updates/builds/update statistics/documents/and generates RSS). It
is easier for me to test on a number of workspaces at once if I can cron
that script rather than copying files, running, fixing, etc.
As soon as I have the id I will complete this (building site.xml and
book.xml per directory). I'd still appreciate input/help on the skin from
some Forrest experts. The Red/Yellow/White is out of my league, and may be
just plain anti-forrest, but I do miss it...
In the end we can write our own XSLT do do anything we want but ?
To start with we can just you a ICON
Also, what ought be done about proposals/aj_python? Ought I keep working in
there until I've proven that this works (builds all succeed) and it builds
nice xdocs/RSS? What is your pleasure?
As soon as it build even a few projects, I think we should move your
code to the ptyhon head.
regards,
Adam
--
Experience Sybase Technology...
http://www.try.sybase.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
