Ross Gardler wrote:
>> But then, why not use an ID-Attribute to achieve this?
RG> Perhaps this is because we can't use an ID attribute in the site:
RG> protocol (I'm guessing, I do not know this to be the case).
Can anybody else tell me why?
--
Ferdinand Soethe
Message:
The following issue has been closed.
Resolver: David Crossley
Date: Wed, 20 Apr 2005 9:31 PM
The "site:" issues are actually fixed. See f.a.o/0.7/ and f.a.o/0.6/
The trouble that you are seeing is because we have not yet updated the
top-level docs. Actually we are going t
Taking the comments into account, we now have this ...
Apache Forrest is a standards-based documentation framework
which uses Apache Cocoon. Forrest emphasises separation of
presentation and content, using a plugin architecture to
transform and aggregate various input sources into various
Brett Presnell wrote:
> Ross Gardler <[EMAIL PROTECTED]> writes:
> >Brett Presnell wrote:
[ snip ]
> >> Getting better, but I don't like the last sentence because it sounds
> >> like a document collection generated from the command line would be
> >> deployed with an automated robot, and I think yo
Ross Gardler <[EMAIL PROTECTED]> writes:
>>
>>>Apache Forrest is a standards-based documentation framework based
>>>on Apache Cocoon. Forrest emphasizes separation of presentation
>>>and content through a plugin architecture for transforming and
>>>aggregating a variety of input sources into one or
Message:
The following issue has been closed.
Resolver: Ross Gardler
Date: Wed, 20 Apr 2005 3:23 PM
Applied, thank you.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-485
Here is an overview of the iss
The following issue has been updated:
Updater: Ross Gardler (mailto:[EMAIL PROTECTED])
Date: Wed, 20 Apr 2005 3:14 PM
Changes:
summary changed from Forrestbot documentation has gone to
Forrestbot proposal has bad links
description changed from The forrestb
The following issue has been updated:
Updater: Mark Eggers (mailto:[EMAIL PROTECTED])
Date: Wed, 20 Apr 2005 3:10 PM
Comment:
The following slight change appears to fix the problem.
Changes:
Attachment changed to howto2document.patch
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-485
Here is an overview of the issue:
-
Key
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-484
Here is an overview of the issue:
-
Key
Brett Presnell wrote:
Ross Gardler <[EMAIL PROTECTED]> writes:
Apache Forrest is a standards-based documentation framework based
on Apache Cocoon. Forrest emphasizes separation of presentation
and content through a plugin architecture for transforming and
aggregating a variety of input sources into
Ross Gardler <[EMAIL PROTECTED]> writes:
>
> Apache Forrest is a standards-based documentation framework based
> on Apache Cocoon. Forrest emphasizes separation of presentation
> and content through a plugin architecture for transforming and
> aggregating a variety of input sources into one or mor
Thorsten Scherler wrote:
On Wed, 2005-04-20 at 19:09 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
Sorry for the crosspost but it seems to be from interest for both
lists. ;-)
Hello devs,
my customer wants to have forrest in lenya (or vice versa). :)
The question that pops into to my head is
Gregor J. Rothfuss wrote:
Thorsten Scherler wrote:
...
What do both projects think which one should become the main app (lenya
or forrest)?
that's a funny question :)
afaik forrest has no workflow, user management etc, so if you need
those, the answer would be pretty clear.
I think the question i
hello all,
> >
> > > If no CSS is defined in the view then *no* css will be linked in the
> presentation.
> >
> > I don't think this is a very good idea. First users of forrest are
> > often novices, and by default, we want to output a slick-looking site.
> > We've already heard reports of peop
On Wed, 2005-04-20 at 19:09 +0100, Ross Gardler wrote:
> Thorsten Scherler wrote:
> > Sorry for the crosspost but it seems to be from interest for both
> > lists. ;-)
> >
> > Hello devs,
> >
> > my customer wants to have forrest in lenya (or vice versa). :)
> >
> > The question that pops into to
Thorsten Scherler wrote:
my customer wants to have forrest in lenya (or vice versa). :)
Lenya is officially supporting 2.1.6 (but 2.1.7 is working fine).
Forrest is using 2.2-dev.
1.2.3 and trunk require 2.1.7
i'd think cocoon 2.2 would work too after we take the new cocoon.xconf
format (with incl
Ross Gardler wrote:
Thorsten Scherler wrote:
Sorry for the crosspost but it seems to be from interest for both
lists. ;-)
Hello devs,
my customer wants to have forrest in lenya (or vice versa). :)
The question that pops into to my head is the compatibility between the
cocoon versions used by lenya/
Ferdinand Soethe wrote:
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
Well my answer may not be complete for the same reason, but...
Why does Forrest expect unique element names in site.xml.
Because of the site: linking
Thorsten Scherler wrote:
Sorry for the crosspost but it seems to be from interest for both
lists. ;-)
Hello devs,
my customer wants to have forrest in lenya (or vice versa). :)
The question that pops into to my head is the compatibility between the
cocoon versions used by lenya/forrest.
Lenya is of
Thorsten Scherler wrote:
Hello devs,
svn: Commit failed (details follow):
svn: OPTIONS request failed on '/repos/asf/forrest/trunk/plugins'
svn: OPTIONS of '/repos/asf/forrest/trunk/plugins': could not connect to
server (https://svn.apache.org)
Stay tuned. ;-)
It's been up and down like a yoyo toda
Cheers Ross. :)
I will have a look on the code as soon as I can. It seems that the cform
stuff right now is not priority one.
Anyway thx a million.
salu2
On Wed, 2005-04-20 at 12:44 +0100, Ross Gardler wrote:
> David Crossley wrote:
> > Thorsten Scherler wrote:
> >
> >>Seems to be that I am th
:)
Nice one, Brett, and welcome to forrest.
I only would change just one sentence.
On Wed, 2005-04-20 at 07:03 -0400, Brett Presnell wrote:
> David Crossley <[EMAIL PROTECTED]> writes:
> >
> > Here is the proposal so far ..
> >
> > Apache Forrest is an XML standards-oriented documen
Brett Presnell wrote:
David Crossley <[EMAIL PROTECTED]> writes:
Here is the proposal so far ..
Apache Forrest is an XML standards-oriented documentation
framework based upon Apache Cocoon and separation of concerns.
Using a plugin architecture, various source input formats are
transfo
Diwaker Gupta wrote:
Due to the way CSS works, if I have to define new properties for
the nav-bar say, then I first have to UNDO all of the changes made by
the CSS files loaded by default, and then define the CSS properties
the way I want them to.
...
A simple option that controls inclusion of defa
Juan Jose Pablos wrote:
Diwaker Gupta wrote:
Awesome! While we're at it, I wonder why we have those elaborate color
definitions in skinconf.xml? Since we are going to use CSS for
skinning anyways, doesn't it make more sense to put the color
definitions into CSS as well? Just a thought.
+1
These wer
Thorsten Scherler wrote:
Hello all,
I am looking into integrate some applications (mainly workflows) written
for cocoon with cforms and flow into forrest.
Not directly related, but you may find this work interesting
http://wiki.apache.org/cocoon/Schema2CocoonForms
Ross
David Crossley wrote:
Thorsten Scherler wrote:
Seems to be that I am the first one in trying to do it.
I just did some testing, but I actually I get
Message: null
Description: No details available.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
Request URI
dima/bearbeite
I know this has come up before, but I'm not sure which of the info in
old threads is still relevant today so I'll ask again:
Why does Forrest expect unique element names in site.xml.
One reason I found in the archives is that you need to have a unique
ID to distinguish between two entries pointin
David Crossley <[EMAIL PROTECTED]> writes:
>
> Here is the proposal so far ..
>
> Apache Forrest is an XML standards-oriented documentation
> framework based upon Apache Cocoon and separation of concerns.
> Using a plugin architecture, various source input formats are
> transformed an
Sorry for the crosspost but it seems to be from interest for both
lists. ;-)
Hello devs,
my customer wants to have forrest in lenya (or vice versa). :)
The question that pops into to my head is the compatibility between the
cocoon versions used by lenya/forrest.
Lenya is officially supporting 2
Hello devs,
svn: Commit failed (details follow):
svn: OPTIONS request failed on '/repos/asf/forrest/trunk/plugins'
svn: OPTIONS of '/repos/asf/forrest/trunk/plugins': could not connect to
server (https://svn.apache.org)
Stay tuned. ;-)
salu2
--
thorsten
"Together we stand, divided we fall!"
H
On Wed, 2005-04-20 at 11:19 +1000, David Crossley wrote:
> Thorsten Scherler wrote:
> > Seems to be that I am the first one in trying to do it.
> >
> > I just did some testing, but I actually I get
> >
> > Message: null
> >
> > Description: No details available.
> >
> > Sender: org.apache.coc
33 matches
Mail list logo
