The following comment has been added to this issue:
Author: David Crossley
Created: Thu, 24 Feb 2005 12:46 AM
Body:
I have done some investigation. The issue only happens on the link/@href and
a/@href and img/@src attributes. Other attributes are okay, e.g. link/@title
and img/@a
This changes causes breakages when doing 'forrest' in docs-author.
Every document gets errors like the following. Do we need an upgraded
Cocoon 2.2?
X [0] libre-intro.html BROKEN:
org.apache.cocoon.environment.commandline.CommandLineRequest.getLocales()
method not yet implemented!
--David
> Au
The following issue has been updated:
Updater: David Crossley (mailto:[EMAIL PROTECTED])
Date: Wed, 23 Feb 2005 7:16 PM
Changes:
Fix Version changed to 0.7
-
For a full history of the issue, see:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-447
Here is an overview of the issue:
-
Key
Thorsten Scherler wrote:
On Wed, 2005-02-23 at 12:00 +, Ross Gardler wrote:
I am doing this with forrest:views. I think that is the way for a
on-page basis.
fbits
-
How does this contribute to/intefere with work on fbits?
fbits are based on forrest:views. Anyway the RT gave me some good
The following comment has been added to this issue:
Author: David Crossley
Created: Wed, 23 Feb 2005 5:09 PM
Body:
I expect that these troubles will go away when we release 0.7 because the 0.7
and 0.8 docs will have consistent layout. But yes, it is a job to be done
either immedi
The following comment has been added to this issue:
Author: Ross Gardler
Created: Wed, 23 Feb 2005 4:50 PM
Body:
Excellent contribution to our docs. There are a few spelling/grammatical
errors, but I've ignored them for the moment. Here are the more important
points:
---
"In do
On Wed, 2005-02-23 at 12:00 +, Ross Gardler wrote:
> Johannes Schaefer wrote:
> > Is there a valid way to specify a specific style for a
> > single element in document-v1.3 (or v2.0)?
> >
> > The only way I see is to use a class attribute but this is
> > not possible because each and every cel
The following issue has been updated:
Updater: Ross Gardler (mailto:[EMAIL PROTECTED])
Date: Wed, 23 Feb 2005 4:07 PM
Changes:
Fix Version changed to 0.7
-
For a full history of the issue, see:
h
The following comment has been added to this issue:
Author: Ross Gardler
Created: Wed, 23 Feb 2005 4:03 PM
Body:
+1, I had missed the fact it messed up PDF generation, we'll need to add a note
on the issue we raise to fix this.
-
Jason End wrote:
> I was wondering if anyone would object to me rewriting
> the Plugin documentation. My understanding is that the
> 0.7 documentation isn't finished and hence I find some
> of the topics slightly confusing.
Please do. Documentation is never finished :-) and
there is always room f
Message:
The following issue has been closed.
Resolver: Ross Gardler
Date: Wed, 23 Feb 2005 3:54 PM
Rather than running all plugin tests we are running one of each type of plugin
(internal, output, input). This is faster and should be almost as thorough,
afterall each individual p
The following comment has been added to this issue:
Author: Florian G. Haas
Created: Wed, 23 Feb 2005 3:53 PM
Body:
OK, but I suggest that in that case a do-nothing template for the
[Please don't reply to a mail and change the subject completely it makes
the archives hard to search - start a completely new thread]
Jason End wrote:
I was wondering if anyone would object to me rewriting
the Plugin documentation. My understanding is that the
0.7 documentation isn't finished and
The following comment has been added to this issue:
Author: Ross Gardler
Created: Wed, 23 Feb 2005 3:32 PM
Body:
The style element in head is there for a reason. It is a hack to allow OOo
documents to be created without using the template. However, it is true that
this makes the
On Wed, Feb 23, 2005 at 09:30:12PM +0100, Juan Jose Pablos wrote:
> Florian,
>
> Florian G. Haas wrote:
>
> >Not trying to sound like the impatient type -- which I nonetheless am,
> >as I'll readily admit :-) -- but it seems to me that a few past
> >patches by contributors haven't made it into th
Hi,
I was wondering if anyone would object to me rewriting
the Plugin documentation. My understanding is that the
0.7 documentation isn't finished and hence I find some
of the topics slightly confusing.
I have some technical doubts that might require a
couple answers from someone, but beyond th
Florian,
Florian G. Haas wrote:
Not trying to sound like the impatient type -- which I nonetheless am,
as I'll readily admit :-) -- but it seems to me that a few past
patches by contributors haven't made it into the trunk simply for
having gone unnoticed, rather than being rejected by committers.
T
I just checked the new howto in as issue
http://issues.cocoondev.org/browse/FOR-446.
Somebody checking for content and language much appreciated.
--
Ferdinand Soethe
The following issue has been updated:
Updater: Ferdinand Soethe (mailto:[EMAIL PROTECTED])
Date: Wed, 23 Feb 2005 2:25 PM
Comment:
zip file contains index.xml (the howto) and three html-files that are
referenced in the howto and need to be in the same directory.
Changes:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-446
Here is an overview of the issue:
-
Key
The following issue has been updated:
Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED])
Date: Wed, 23 Feb 2005 2:13 PM
Changes:
Fix Version changed to 0.7
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED])
Date: Wed, 23 Feb 2005 2:10 PM
Changes:
Fix Version changed to 0.7
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED])
Date: Wed, 23 Feb 2005 1:58 PM
Changes:
Fix Version changed to 0.7
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED])
Date: Wed, 23 Feb 2005 1:57 PM
Changes:
Version changed to 0.7
Version changed from HEAD
-
For
Hello,
considering prerelease time is usually bugfix time, are any committers
currently reviewing FOR-430 and FOR-430? I submitted patches for these
a few weeks ago (like I suppose other contributors have for issues
reported by them, too).
Not trying to sound like the impatient type -- which I no
Ross Gardler wrote:
Nicola Ken Barozzi wrote:
Ross Gardler wrote:
...
my-project/
forrest.xml
documentation/
status.xml
--> content.xml
--> content.meta.xml
** all other content
FORREST-INF/
skinconf.xml
Nicola Ken Barozzi wrote:
Ross Gardler wrote:
...
I agree to the intent, and in fact I had done a similar proposal,
although without considering the impact for the plugins.
Read this and tell me what you think, and how the two may fit.
[RT] Directory structure and configuration
http://marc.theaim
Ross Gardler wrote:
...
I agree to the intent, and in fact I had done a similar proposal,
although without considering the impact for the plugins.
Read this and tell me what you think, and how the two may fit.
[RT] Directory structure and configuration
http://marc.theaimsgroup.com/?l=forrest-dev&
Johannes Schaefer wrote:
Is there a valid way to specify a specific style for a
single element in document-v1.3 (or v2.0)?
The only way I see is to use a class attribute but this is
not possible because each and every cell may have a
different bg-color.
[Note what I am thinking about here is quite
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
...
(Getting the documentation published, even if only in a manual way would
be important for example).
Do you mean the documentation for the various plugins?
Yes, and I mean I will do that (unless someone gets to it before I do).
Ro
On Mie, 23 de Febrero de 2005, 2:23, David Crossley dijo:
> I solved some of the remaining failures with the forrestbot.
> Both "forrest-site" and "forrest-docs-dev" needed to have a full
> 'svn checkout' done before the forrestbot starts. Forrestbot
> only does 'svn co' of part of the source tree
I solved some of the remaining failures with the forrestbot.
Both "forrest-site" and "forrest-docs-dev" needed to have a full
'svn checkout' done before the forrestbot starts. Forrestbot
only does 'svn co' of part of the source tree and so it misses
the "conf" directory for "forrest-site". Dunno wh
33 matches
Mail list logo
