Apologies, I now realise that my mail client auto completed the wrong
address - no wonder I was getting no response.
Ross
2009/11/23 Ross Gardler rgard...@apache.org:
http://community.apache.org is not showing the updates to the wiki, it
still shows the original CWiki index page. Anyone know
http://community.apache.org is not showing the updates to the wiki, it
still shows the original CWiki index page. Anyone know how the export
thingy works?
Ross
--
Ross Gardler
OSS Watch - supporting open source in education and research
http://www.oss-watch.ac.uk
Can someone please kick the Daisy server on the Zone.
Ross
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
...
[copy] Copying 1 file to /var/apache2/htdocs/ft/build/cocoon-docs
[echo] Oops, something broke
Can whoever broke this please fix it - the nags are annoying and I don't
have the time to
Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
...
[copy] Copying 1 file to
/var/apache2/htdocs/ft/build/cocoon-docs
[echo] Oops, something broke
Can whoever broke this please fix it - the nags are annoying and I don't
Joerg Heinicke wrote:
On 18.10.2008 14:25, [EMAIL PROTECTED] wrote:
[java] X [0]
2.1/prepare-mojo.htmlBROKEN:
/export/opt/forrest-trunk/build/plugins/org.apache.forrest.plugin.input.Daisy
(Is a directory)
[java] ^
Jeremy Quinn wrote:
On 29 Jul 2008, at 10:18, Andrew Savory wrote:
It's my pleasure to propose Jasha Joachimsthal as a new committer on
the Apache Cocoon project.
My +1
+1
Ross
Ard Schrijvers wrote:
I propose Thorsten Scherler as a new Cocoon committer and PMC member.
+1
+1
Ross
On 08/10/2007, Reinhard Poetz [EMAIL PROTECTED] wrote:
Ross Gardler wrote:
On 08/10/2007, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Am I correct in thinking Cocoon does not use the Forrest built docs anymore?
Can we (Forrest) remove
On 08/10/2007, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Am I correct in thinking Cocoon does not use the Forrest built docs anymore?
Can we (Forrest) remove this automated build or do we need to fix this?
(Note the fix is easy, I can make the fix in
Andrew Savory wrote:
Once again a big round of applause to Thien.
Absolutely. Many thanks, Thien, excellent work!
I've kept quiet throughout this work due to other commitments and not
wanting to get in the way.
Now you reached the end it is time to speak up.
Well done! I love the end
Joerg Heinicke wrote:
On 14.03.2007 09:27, Ross McDonald wrote:
I suppose a list of active committers will prevent people who are no
longer active from receiving emails they don't want to receive from
those looking for help.. so it may stop dead end investigations?
In that way an up-to-date
Carsten Ziegeler wrote:
Bertrand Delacretaz wrote:
On 12/21/06, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Could someone please assemble the docs archive for the 2.1.10 release?
The generated docs are available as a tar.gz archive from the
cocoon-docs.tar.gz direct download link at
Carsten Ziegeler wrote:
Ross Gardler schrieb:
...
Thanks for the info! One final question :) where do I find the docs for
2.1 in Daisy?
Fairly important I suppose...
http://cocoon.zones.apache.org/daisy/documentation/659.html
Ross
Bertrand Delacretaz wrote:
On 10/19/06, Ross Gardler [EMAIL PROTECTED] wrote:
...But is there any need for the news item to be sent to the
live server immediately? I don't think so. A daily update will do just
fine. For now use the Forrest generated tar, or a maven generated tar if
someone
/06, Ross Gardler [EMAIL PROTECTED] wrote:
...Which publishing tool to use? I don't care. Forrest does it well
(but it
does need a new skin,...
Is there a way to republish only a few pages quickly from Daisy to the
online site? Or how hard is that to implement?
A very good question - and one
hepabolu wrote:
I know that the current process of updating the cocoon.apache.org
website is cumbersome, but still it's a whole lot better than the
previous process. I really don't care if it takes one step or twenty, if
in the end all I need to do is set a timer that reminds me to provide my
Daniel Fagerstrom wrote:
we have plenty of activity in our community, so a couple of news
items per month would be a much better reflection of our reality. So how
do we achieve this?
Some options (which don't require new tools):
Daisy can be used to create blog like pages that can be
David Crossley wrote:
See the new section at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
to explain the quick way to update the Cocoon 2.1 docs.
Any committer can do it.
I followed this today (it has been 2 months since last update).
However i don't have time to find out what is going
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
This is due to a change in the way Forrest SVN head is configured. Will
fix ASAP.
Ross
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
I am looking into this. Sorry it's taken me so long to find the time.
(we need someone else who knows how this works)
Ross
hepabolu wrote:
Carsten Ziegeler said the following on 28/7/06 14:00:
We have currently a split storage for our docs (and different ways to
update the docs). While the main docs for a version of Cocoon are stored
in Daisy, the more general stuff, is stored in the cocoon-site module in
the
Carsten Ziegeler wrote:
Ross Gardler wrote:
hepabolu wrote:
...
I'm not absolutely sure, but we could, as an itermediate solution,
create a separate collection in Daisy in which we move those documents,
which are then exported in the same way as the current Daisy docs. I
don't think
Niels van Kampenhout wrote:
Reinhard Poetz wrote:
Niels van Kampenhout wrote:
Hi,
I just noticed that there is an incorrect link in the Cocoon Forms
documentation. In [1], at the end of the section Selection lists,
there is a link which should lead to more info on selection lists
[2],
Niels van Kampenhout wrote:
Ross Gardler wrote:
Niels van Kampenhout wrote:
Hmm. I understand from Arje that the documentation I refered to in my
post is outdated and not updated anymore. The latest documentation
apparently is at cocoon.zones.apache.org. To be honest, I was under
Joerg Heinicke wrote:
1. Andreas Hochsteger
+1
2. Peter Hunsberger
+1
3. Jason Johnston
+1
Welcome to all three.
Ross
Bruno Dumon wrote:
On Fri, 2006-05-05 at 16:28 +0100, Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
...
http://cocoon.zones.apache.org/daisy/documentation/864/forms/widgets/739.html
In this document we can see that daisy is using a pseudo protocol
Bruno Dumon wrote:
On Fri, 2006-05-05 at 16:28 +0100, Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
...
This looks like someone has used a javadoc: protocol in the source
files. Unfortunately, Daisy does not recognise
...
Oops! I knew
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
...
[java] X [0]
2.1/userdocs/widgets/javadoc:org.apache.cocoon.forms.formmodel.tree.TreeModel
BROKEN: No pipeline matched request:
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
This failure is because I am working on the docs right now. Please ignore.
Ross
Ross Gardler wrote:
Carsten Ziegeler wrote:
Antonio Gallardo schrieb:
Carsten Ziegeler escribió:
Can someone please generate the docs for the 2.1.9 release, so we can
put an archive of the docs in the download area like we did for 2.1.8?
Carsten
Thanks Carsten for the release
Andreas Hochsteger wrote:
Congratulations to all who were involved - you did an awesome job!
BTW the page changes.html still shows TBD as release date.
This will be corrected when someone updates the website with the new
docs build I created tonight.
Ross
Carsten Ziegeler wrote:
Antonio Gallardo schrieb:
Carsten Ziegeler escribió:
Can someone please generate the docs for the 2.1.9 release, so we can
put an archive of the docs in the download area like we did for 2.1.8?
Carsten
Thanks Carsten for the release. As usual, I will take care of
David Crossley wrote:
Carsten Ziegeler wrote:
I can't speak for Daniel, but my idea/suggestion was to forget about the
different environments and let Cocoon always run in a servlet container.
The CLI would then be kind of a http client which starts up jetty and
then generates the site using
Jean-Baptiste Quenot wrote:
Hello,
Is it possible to propagate the update of this page from Daisy to
the website:
http://cocoon.apache.org/community/members.html
Or please tell me where to edit it.
That part of the site is not in Daisy. It is still in SVN - only the
2.1.x docs are currently
David Crossley wrote:
Ross Gardler wrote:
Perhaps there is a time out occuring. Is there a way of increasing the
timeout on files being generated from http: sources? Not a solution, but
it would be a workaround.
I don't know if it proves anything, but just completed
a local build
Daniel Fagerstrom wrote:
Hi all!
I'd like to propose Niclas Hedhman as a new Cocoon committer. He has
been around at cocoon-dev since 2000, regularly delivering insight full
comments about technical as well as community questions, high quality
patches and strong opinions in various topics ;)
Bruno Dumon wrote:
On Tue, 2006-03-21 at 19:11 +1100, David Crossley wrote:
David Crossley wrote:
Bruno Dumon wrote:
BTW, this time not because the zone was restarted. Not sure what the
problem is though.
I investigated a bit yesterday, but cannot see what
is the problem. Notice that
Bruno Dumon wrote:
The goal of all this would be that the basic facts about each component
are taken from the source code, and longer (user-oriented) documentation
could then be added in Daisy (in a document part that is left alone by
this tool).
Super cool!
Ross
Bruno Dumon wrote:
On Mon, 2006-03-06 at 18:39 +0100, Reinhard Poetz wrote:
hepabolu wrote:
Finally, adding the proposed plugin can always be added later without
loosing the effort of the current setup.
ok, that's right. Anyway, I can't do it myself now but if somebody is
interested, I
Reinhard Poetz wrote:
As written in my mail Status of block development
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I
propose a change in the Cocoon documentation creation:
We have put a lot of work into the Mavenization of the Cocoon build
system. As you might
Bruno Dumon wrote:
On Wed, 2006-03-01 at 14:01 +, Ross Gardler wrote:
A couple of weeks ago I promised to set up a FAQ system in Daisy. I've
now done this.
Creating a FAQ
==
There is a FAQ document Type. This is a simple document in which the
document title should
A couple of weeks ago I promised to set up a FAQ system in Daisy. I've
now done this.
Creating a FAQ
==
There is a FAQ document Type. This is a simple document in which the
document title should be the question and the content should be the answer.
To illustrate things I have
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
...
[java]
[copy] Copying 6 files to /var/apache2/htdocs/ft/build/cocoon-docs/skin
[echo] Copying project skin css and js files to site ...
[copy] Warning:
hepabolu wrote:
David Crossley wrote:
Today i re-generated the cocoon.apache.org/2.1/ website
which incorporates a few changes to the Daisy sources,
fixes some links that used local hrefs, removes the
old ApacheCon logo.
There were some new documents generated which do not
have any mapping in
Alexander Lochschmied wrote:
Hello,
pretty much on top of this page the link to InputModules Wiki Page is
broken.
http://wiki.apache.org/cocoonInputModules/
should be replaced by
http://wiki.apache.org/cocoon/InputModules
as it’s a good page.
If you register on Daisy, the CMS we use for our
David Crossley wrote:
hepabolu wrote:
BTW do you like the layout of the Notes, Warnings and Fixes? (See
samples page)
The main trouble that i see, is that it puts each note
out-of-context with the main page, i.e. not sure what the
warning refers to.
Thanks David, I meant to say that, but
hepabolu wrote:
http://web.inter.nl.net/users/hepabolu/cocoondocsskin/index.html
and
http://web.inter.nl.net/users/hepabolu/cocoondocsskin/samples/sample.html
I'll send Ross the set of files offlist so he can figure out what to
change to integrate it in Forrest.
Great stuff Helma.
I've
Derek Hohls wrote:
I like the idea of a categorised FAQ - a simple QA list
is fine for a simple project - but Cocoon is *not* that
by any measure. Can one have other categories as well?
Yes, the category field is a multivalued field.
Alternativley, we could just use a tags field allowing
Berin Loritsch wrote:
This is really a three pronged question:
1. Do we have a project FAQ?
2. Where is it? on daisy?
(assumption - there isn't a FAQ already)
I use Daisy on an in-house project for documentation. One of the things
we have done is create a FAQ document type which has a
Bruno Dumon wrote:
I restarted them now.
Is it necessary that the forrestbot runs so often? Seems like now it
runs every 3 hours. IMO once or twice a day would be enough.
No it isn't necessary anymore - was handy when doing the work to create
the new docs.
The idea of frequent builds is to
Ross Gardler wrote:
Bruno Dumon wrote:
I restarted them now.
Is it necessary that the forrestbot runs so often? Seems like now it
runs every 3 hours. IMO once or twice a day would be enough.
No it isn't necessary anymore - was handy when doing the work to create
the new docs.
The idea
David Crossley wrote:
Ross Gardler wrote:
Ross Gardler wrote:
Bruno Dumon wrote:
I restarted them now.
Is it necessary that the forrestbot runs so often? Seems like now it
runs every 3 hours. IMO once or twice a day would be enough.
No it isn't necessary anymore - was handy when doing
hepabolu wrote:
Ross Gardler wrote:
hepabolu wrote:
Ross Gardler wrote:
2) are there any web designers here willing to work on the skin (you
don't need to learn how to get it into Forrest at first, just provide
CSS patches and I'll integrate with Forrest for you - you'll quickly
see
how
David Crossley wrote:
hepabolu wrote:
David Crossley wrote:
It seems that despite our concerns and attempts to address it
at the time, we still broke the URL space when publishing the
2.1 docs.
Vadim, Helma, ... does anyone still have a list of the
filenames from when we investigated this.
John L. Webber wrote:
Following the link http://cocoon.apache.org/2.1/installing/jars.html
brings the message:
This is now an autogenerated document. If you see this message, then
something is wrong with the build!
Is this a known problem? ;-)
It is now ;-) Thanks for reporting this.
What
Joerg Heinicke wrote:
On 19.01.2006 17:01, Ross Gardler wrote:
http://cocoon.apache.org/2.1/installing/jars.html
What *should* be going in here and how did it get there with the old
build system? Is this something Forrest needs to handle?
AFAIR it was generated from our jars.xml
When we were doing the work to generate the Docs from Daisy some people
showed an interest in developing a new skin for the Cocoon site.
Those people may be interested to know that I recently developed a skin
to mimic the look and feel at http://www.apache.org
This is a much simpler skin, much
Upayavira wrote:
Sumit wrote:
Hi All,
I have one issue i.e. while developing a dynamic web page i want the
response in any particular format required by user, it can be in PDF,
TXT, DOC, HTML,
...
You should ask this question on the user list. It is a better place for
such a question.
Geert Josten wrote:
You could use input-modules to convert a relative path to an absolute
one. It should be possible with the realpath input module for instance.
The locationmap in Forrest is an input module that can be used to do
this, and much more.
Docs at
Vadim Gritsenko wrote:
[ ] +1, Let's do it!
[ ] 0, What is CForms?
[ ] -1, It's not stable, because...
+1 - been stable for a long time as far as I am concerned ;-)
Ross
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Jan 2006, Reinhard Poetz wrote:
[1] http://cocoon.zones.apache.org/daisy/documentation/g2/796.html
[2] http://cocoon.zones.apache.org/daisy/documentation/g2/797.html
If I want to edit those Daisy docs above I
Gianugo Rabellino wrote:
On 12/30/05, Sylvain Wallez [EMAIL PROTECTED] wrote:
Hi all,
The W3C recently set up an XML Processing working group[1] whose
primary goal is to define an XML processing language (i.e. pipelines).
...
My impression is that what this WG will end up defining yet
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
...
[java] X [0] linkmap.html BROKEN:
Connection refused
This is because the daisy instance on the Cocoon Zone is down.
Ross
Jorg Heymans wrote:
Antonio Gallardo wrote:
Also, please don't forget the ajax block. It is needed by forms. ;-)
Is ajax really a block on it's own ? I mean i know it can be plugged
into cforms to make forms ajax aware, but is it useable by other blocks
as well ? I'm not really uptodate
Jorg Heymans wrote:
Ross | David ,
Would you mind describing the dependency that forrest has on cocoon?
Are you guys using branch or trunk? If the latter, how does the current
M10N and a possible repository reorganisation affect you ?
We are using a complied version of trunk. We are not
Reinhard Poetz wrote:
Sylvain Wallez wrote:
Hi all,
An ASF members meeting was held yesterday evening here in San Diego
during which new members were voted in. Among the 33 new members, some
are well known here:
- Bruno Dumon
- Antonio Gallardo
- Ross Gardler
- Reinhard Poetz
- Jeremy
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
...
Copying broken links file to site root.
[copy] Copying 1 file to /var/apache2/htdocs/ft/build/cocoon-docs
[echo] Oops, something broke
Looks like something in Forrest has broken. Since it
Sylvain Wallez wrote:
Ross Gardler wrote:
Now I'd better stop before I start convincing myself that people will
find all 600 pages of my PhD interesting ;-)
Any pointer for those that might be interested?
This research is fairly old now (6 years), and things have moved on a
little
Ross Gardler wrote:
Sylvain Wallez wrote:
Ross Gardler wrote:
Now I'd better stop before I start convincing myself that people will
find all 600 pages of my PhD interesting ;-)
Any pointer for those that might be interested?
This research is fairly old now (6 years), and things have
Sylvain Wallez wrote:
Berin Loritsch wrote:
In all the talks of redesign or not, there has been a recurring
question as to the vision. Sylvain has outlined some things that he
would like to see, but they really don't constitute a vision. They
are a nice list of improvements, but they
Bertrand Delacretaz wrote:
Le 7 déc. 05, à 09:10, Ross Gardler a écrit :
...I envision being able to build a Cocoon application by saying
given these input types, I want this output type and to have the
resulting application automatically tested against my test inputs...
Not sure if I
Berin Loritsch wrote:
Ralph Goers wrote:
None of these. I have a vision where the business services are
implemented in Java, the web application is defined in a stateful flow
controller (xml config) and the views are generated using pipelines
with standard components. So my answer is - No
Mats Norén wrote:
Ross Gardler wrote:
Bertrand Delacretaz wrote:
Le 7 déc. 05, à 09:10, Ross Gardler a écrit :
...I envision being able to build a Cocoon application by saying
given these input types, I want this output type and to have the
resulting application automatically tested
Ugo Cei wrote:
Il giorno 07/dic/05, alle ore 11:43, Ross Gardler ha scritto:
Most businesses are made up of common business processes. The odd one
will be unique to that business, but most are common. In the case of
the unique practices the software needs to be customised
[X] Mix and match (not as simple, but is status quo with today)
However, to be effective we need a core development effort, therefore
the *official* support should be for a limited subset of what is in use
today:
Javascript + Java
Ross
hepabolu wrote:
Reinhard Poetz wrote:
Bertrand Delacretaz wrote:
Maybe we could use the private committer's SVN area to coordinate and
review stuff once we start writing, not to hide it from our public
community but to respect the (assumed) magazine's desire for keeping
things private
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Joerg Heinicke wrote:
Antonio Fiol Bonn?n wrote:
This can't possibly be what we need, as anyone would have done it
faster than me, but anyway, here it goes.
IIRC the problem was not the pure removal, but the mentioning
David Crossley wrote:
Joerg Heinicke wrote:
Antonio Fiol Bonn?n wrote:
This can't possibly be what we need, as anyone would have done it
faster than me, but anyway, here it goes.
IIRC the problem was not the pure removal, but the mentioning of the
authors in a contrib file file.
Carsten Ziegeler wrote:
The changes list is not current; although it contains the entry for
2.1.9, many entries for 2.1.8 are missing.
It should be generated directly from the status.xml file in SVN so I
don't understand how any can be missing.
Please give an example of a missing item so I
You can get the most recent build of the 2.1.8 docs from my cocoon zone
home (~rgardler), filename docs-2.1.8.tar.gz
I'm away from a net connection for most of the day. If there are any
problems ask one of the Forrest devs to help out by retrieving the docs
from the Forrest Zone.
I'll check
Upayavira wrote:
Carsten Ziegeler wrote:
The release is built and I'll announce everything tomorrow. This means
we should update the website (and docs) tomorrow as well. Can someone
please do this?
A request, from a marketing perspective. Could we write a special
announcement for this that
hepabolu wrote:
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 16 November 08:16 AM
Using Forrest 0.8-dev
Forrestbot administrator: ForrestBot
--
I suppose this is due to my changing of the navigation document in
hepabolu wrote:
Ross Gardler wrote:
I suppose this is due to my changing of the navigation document in
Daisy, so I suppose Ross needs to fix the Forrest side of things.
There should be nothing needs doing on the Forrest side, but obviously
something is wrong somewhere ;-)
I'm
I promised to create a tarball of the docs for release, but I can't do
that until the status.xml file has been verified as being complete and
the release date has been entered into it.
Can people please give it a look over. We generate from the version in
SVN so just update SVN as appropriate
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
don't worry about that one, I was doing a test build and the cron job to
update forrest occurred during the build. I've done another one since.
Ross
Carsten Ziegeler wrote:
Hmm, so it seems that we can release on thursday (I hope).
Can someone please provide me an archive (zip/tgz) of the docs (e.g. on
our zone) that I can put in our download section?
I will be able to do that (including changes.html) tomorrow (wednesday)
as long as
hepabolu wrote:
Ross Gardler wrote:
Carsten Ziegeler wrote:
Hmm, so it seems that we can release on thursday (I hope).
Can someone please provide me an archive (zip/tgz) of the docs (e.g. on
our zone) that I can put in our download section?
I will be able to do that (including
hepabolu wrote:
Ross Gardler wrote:
Vadims diff should be helpful, I can't find it in the archives right
now, but it was posted late last week.
Just had a look, but I can't figure out what has yet to be done. Vadim
could you run the diff one more time please?
Vadim, here is the latest
hepabolu wrote:
David Crossley wrote:
There are a number of places in the source documents with the
token @released.version@, e.g.
http://forrest.zones.apache.org/ft/build/cocoon-docs/2.1/index.html
I'll see to this.
I don't know how big a job this is. But if it is still worthwhile the
hepabolu wrote:
Carsten Ziegeler wrote:
What is the status of the 2.1.8 docs? I would like to release 2.1.8 by
the end of this week. If there are only minor issues, we could perhaps
use the docs as of now and then perhaps release a docs update some weeks
later?
From my POV there are no or
David Crossley wrote:
Ross Gardler wrote:
Vadim Gritsenko wrote:
Ross Gardler wrote:
Vadim Gritsenko wrote:
Forgot to add... Can we loose page toc which now appears within left
navigation bar? I'm not sure we should have it there, it certainly
looks strange...
It was moved
Bertrand Delacretaz wrote:
Le 14 nov. 05, à 10:09, hepabolu a écrit :
...From my POV there are no or only minor issues in the docs. Let's
see what the others have to say...
IMHO the only critical thing is to have these pages updated when the
release is done:
David Crossley wrote:
Ross Gardler wrote:
...
* Extra URI segments:
Some of these are a result of the lack of a clean build space (i.e.
about/), but others are the same problem with the daisy navigation, for
example, the extra dirs under /userdocs/forms/
Helma did warns us
Bertrand Delacretaz wrote:
Le 11 nov. 05, à 04:26, David Crossley a écrit :
...The top-level docs are now building the changes page
by getting the status.xml file from the 2.1 branch svn.
Not ideal, but it works
Great!
http://forrest.zones.apache.org/ft/build/cocoon-site/changes.html
hepabolu wrote:
Ross Gardler wrote:
Note, somehow only the menu is up on forrest.zones, all linked pages
are gone. I suspect this is due to the split in the navigation doc in
Daisy and should be fixed when Ross adjusts the appropriate files in
Forrest.
I'm not seeing this. I see the full
Vadim Gritsenko wrote:
Vadim Gritsenko wrote:
Ross Gardler wrote:
Perhaps Vadim can create a diff for us again to check this status,
once the build has completed in around 3 hours.
Cool stuff.
Forgot to add... Can we loose page toc which now appears within left
navigation bar? I'm
hepabolu wrote:
Ross Gardler wrote:
Two of the others had the same problem: 2.1/forms/binding.html and
2.1/forms/xmlbinding.html.
Since this concerns only 2 files, just remove the grouping in Daisy so
the url space matches. They both have binding in their label, so it
should stand out
Vadim Gritsenko wrote:
Ross Gardler wrote:
Perhaps Vadim can create a diff for us again to check this status,
once the build has completed in around 3 hours.
Cool stuff.
Send me result of
find . -name *.html
I just sent it offlist, but I sent it from the zone, not sure if mail is
set
Vadim Gritsenko wrote:
Ross Gardler wrote:
Vadim Gritsenko wrote:
Forgot to add... Can we loose page toc which now appears within left
navigation bar? I'm not sure we should have it there, it certainly
looks strange...
It was moved there as a test, come people like it in the body, come
1 - 100 of 278 matches
Mail list logo
