On Sat, 2005-11-05 at 00:39 +, Ross Gardler wrote:
Steven Noels wrote:
On 04 Nov 2005, at 17:53, Bruno Dumon wrote:
Hi,
any reason the sites on
http://cocoon.zones.apache.org/daisy/
have been made inaccessible?
I saw the ACL change notification message this morning but
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 08:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 08:10:12
... Rendering docs in
On 04.11.2005 15:36, Sylvain Wallez wrote:
Can't follow you? What do you have in mind?
This is related to the Ajax BrowserUpdateTransformer:
Ok, convinced. Your explanation sounds reasonable.
Jörg
On 05.11.2005 08:46, Sylvain Wallez wrote:
So let's make other proposals. Let's consider wiget foo.bar (e.g. a
fd:field in a fd:group) and the ID of its input.
- foo.bar..input: the '.' is doubled, which can never conflict with
a widget's full name
- foo.bar._input: generated element's name
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 09:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 09:10:06
... Rendering docs in
Le 5 nov. 05, à 08:46, Sylvain Wallez a écrit :
...Another one, which looks more natural: foo.bar.input.: the
trailing '.' ensures it cannot conflict with a widget's full name...
I also like this option better.
-Bertrand
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 10:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 10:10:06
... Rendering docs in
Il giorno 05/nov/05, alle ore 08:46, Sylvain Wallez ha scritto:
So let's make other proposals. Let's consider wiget
foo.bar (e.g. a fd:field in a fd:group) and the ID of its input.
- foo.bar..input: the '.' is doubled, which can never conflict
with a widget's full name
- foo.bar._input:
Bruno Dumon wrote:
On Sat, 2005-11-05 at 00:39 +, Ross Gardler wrote:
Steven Noels wrote:
On 04 Nov 2005, at 17:53, Bruno Dumon wrote:
Hi,
any reason the sites on
http://cocoon.zones.apache.org/daisy/
have been made inaccessible?
I saw the ACL change notification message this
Le 4 nov. 05, à 23:27, David Crossley a écrit :
...The whole top-level site is described here.
[1] http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
... same as it has always been...
Of course, I should have known that. My confusion came from the removal
of xdocs in the 2.1 branch - I have
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 11:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 11:10:06
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 12:12 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 12:10:47
... Rendering docs in
On 05.11.2005 13:12, [EMAIL PROTECTED] wrote:
Automated build for cocoon-site FAILED
Every hour?
Jörg
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 01:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 01:10:14
... Rendering docs in
Joerg Heinicke wrote:
On 05.11.2005 13:12, [EMAIL PROTECTED] wrote:
Automated build for cocoon-site FAILED
Every hour?
Unfortunately this is set in Davids crontab, so the frequency can opnly
be changed by him. Of course, someone could fix the broken link, then
the nags would go away ;-)
hepabolu wrote:
Ross or David,
on verifying that the FAQ pages are now correctly generated I came
across a cosmetic glitch:
http://forrest.zones.apache.org/ft/build/cocoon-docs/2.1/documentation/faq/gettingstarted/faq-configure-environment.html
has an empty TOC at the top.
The other FAQ
Patrick Ahles wrote:
What's more, there are 4 links in this page, 3 of them not working...
These should also be fixed on the next build in couple of hours from now
(in fact they were fixed some time ago, but the page was not being
regenerated).
Ross
Mark Lundquist wrote:
On Nov 4, 2005, at 2:15 PM, Ross Gardler wrote:
Looks like a side effect of the move of the TOC to the menu. I'll look
at it ASAP (should manage over the weekend).
Speakin' of...
Would it be possible/desirable to display this page with the first level
of cascading
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 02:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 02:10:12
... Rendering docs in
On 05.11.2005 14:45, Ross Gardler wrote:
Of course, someone could fix the broken link, then the nags would go
away ;-)
To do this myself I have to get more to know about the current docs
infrastructure. Can somebody give me an overview about it or does a
document exist to read about it? How
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 03:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 03:10:06
... Rendering docs in
Vadim Gritsenko wrote:
Daniel Fagerstrom wrote:
I explained about tags above. For branches it depends, quoting Niclas:
I understand about tags. Please help me out with branches. Here is
current situation, in english:
cocoon 2.1 branch depends on cocoon-blocks-xsp 2.1 branch
cocoon
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 04:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 04:10:11
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 05:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 05:10:07
... Rendering docs in
Guys,
just to get the confusion level down I'd like to verify that my ideas
about the current docs are complete and correct.
From what I've gathered from the various threads the idea is currently
as follows:
In general:
- Daisy at the cocoon.zones is our staging server for the
Sylvain Wallez wrote:
So let's make other proposals. Let's consider wiget foo.bar (e.g. a
fd:field in a fd:group) and the ID of its input.
- foo.bar..input: the '.' is doubled, which can never conflict with
a widget's full name
- foo.bar._input: generated element's name starts with a character
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 06:13 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 06:10:56
... Rendering docs in
Daniel Fagerstrom wrote:
Block development
=
During block development the block can depend on released versions of
other blocks. This means that you just need to check out the block you
want to work with, the rest of the blocks are downloaded from a maven
repository when
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 07:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 07:10:14
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 08:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 08:10:11
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 09:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 09:10:09
... Rendering docs in
hepabolu wrote:
just to get the confusion level down I'd like to verify that my ideas
about the current docs are complete and correct.
Good idea, I've been a little confused by the need for continuing the
cocoon-site build. Here's what I think I understand...
From what I've gathered from
Joerg Heinicke wrote:
On 05.11.2005 14:45, Ross Gardler wrote:
Of course, someone could fix the broken link, then the nags would go
away ;-)
To do this myself I have to get more to know about the current docs
infrastructure.
Of course I wasn't suggesting you personally do it, but if you
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 10:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 10:10:06
... Rendering docs in
Ross Gardler wrote:
Yes, although sine the 2.2 xdocs are still in SVN (cocoon/site) so there
may be overlap at present.
Hmm, I haven't looked lately but I was under the impression that they
were moved out already. I'll see about that as soon as I find some time.
- cocoon.apache.org is our
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 05 November 11:10 PM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-05 11:10:13
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 12:12 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-06 12:11:19
... Rendering docs in
Motivation:
CForms user would like to display instructions or some other hint to
the end user in the text input widget itself (as opposed to a tool-tip
on-hover). This text should not be submitted, and if a user wants to
enter text into the input, the tip text should automatically disappear
so
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 02:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-06 02:10:11
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 03:12 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-06 03:10:33
... Rendering docs in
Hi Eric and Rus:
Please provide a link, where the community can see this working. As I
told before, I found very useful this enhancement. :-)
Best Regards,
Antonio Gallardo.
Quoin Developers wrote:
Motivation:
CForms user would like to display instructions or some other hint to
the end
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 04:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-06 04:10:13
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 05:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-06 05:10:07
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 06:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-06 06:10:08
... Rendering docs in
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 07:10 AM
Using Forrest 0.7
Forrestbot administrator: Cocoon developers
--
[echo]
... Forrest render START 2005-11-06 07:10:06
... Rendering docs in
Is this an effort to get our message traffic numbers even higher?
Sorry, but these messages are now filtered straight to the trash.
[EMAIL PROTECTED] wrote:
Automated build for cocoon-site FAILED
Log attached.
--
Forrestbot run ended at 06 November 07:10 AM
Using Forrest 0.7
46 matches
Mail list logo
