David Crossley wrote:
> Ferdinand Soethe wrote:
>
>>Nicola Ken Barozzi wrote:
>>
>>>AFAIK, from what I have read as answers to this question over the years,
>>>the range should contain the year of creation and the year of the last
>>>modification.
>>
>>>If it's a legal necessity or just customary.
Nicola Ken Barozzi wrote:
>
> First of all, please read the XHTML2 spec in the latest form ATOP:
>
> http://www.w3.org/TR/2005/WD-xhtml2-20050527/
>
> Don't cheat, have you really read it? ;-P
>
> To be sure, I'll leave some space on this page...
More space please - i read the Introduction to
[ http://issues.apache.org/jira/browse/FOR-647?page=all ]
David Crossley closed FOR-647:
--
Fix Version: 0.8-dev
Resolution: Fixed
applied thanks.
> Locationmap View needs to handle drop requests from the Repository Browser
> --
Tim Williams wrote:
> I've followed the Plugin-How-to and gotten to the point of testing.
> When I run "ant test" it fails out at the "configure-cocoon" target
> saying MyPluginName\conf not found. Any idea where I may have gone
> astray?
My guess is that this comes from the xpatch task at
main/
Addi wrote:
>
> I went ahead and cleaned the test files with my editor. How would you
> like to check/compare them to your editor to make sure we are on the
> same page?
I tried doing a reformat using IDEA and it was too zealous.
It could be configured to be more minimal, but i bet that
it woul
I fixed some non-native line-endings problems with this
commit and some other recent commits.
However that might be creating just the problem we are
trying to avoid when doing the whitespace cleanup.
People might be getting conflicts if they have been
editing these files.
-David
> Author: crossl
Diwaker Gupta wrote:
> > Jalopy was mentioned during that big cocoon-dev thread.
> > Follow the links from http://issues.apache.org/jira/browse/FOR-644
> >
> > For some reason, we decided not to use it. Perhaps because
> > periodic cleanups can still cause havoc for people who
> > are working on t
addi wrote:
> David Crossley wrote:
> >
> > Did you use the UNIX command 'tree' or create it manually?
> > The former i hope.
>
> No, I did it manually. Everything that I know about computers has been
> self-taught so unfortunately I have huge gaps in my knowledge. I end up
> being a big Rube q
[ http://issues.apache.org/jira/browse/FOR-646?page=all ]
David Crossley closed FOR-646:
--
Resolution: Fixed
applied thanks.
> Corrected whitespace cleanup dir tree
> -
>
> Key: FOR-646
> URL: http:
[
http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12319954 ]
David Crossley commented on FOR-605:
That is an effect of just adding new features, without consolidating what we
already have. At the last release, we urgently needed a way
Gavin (JIRA) wrote:
> [
> http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12317899 ]
>
> Gavin commented on FOR-605:
> ---
>
> I removed the comment tags from the motd in /forrest/site-author/skinconf.xml
> but it has made no difference.
> Can you
I've followed the Plugin-How-to and gotten to the point of testing.
When I run "ant test" it fails out at the "configure-cocoon" target
saying MyPluginName\conf not found. Any idea where I may have gone
astray?
Thanks,
--tim
Ferdinand Soethe wrote:
> Any reason not to move these to sitemap.xmap?
This was discussed on the dev list a few weeks ago.
I think that the answer was that someone needs to go
through all the sitemaps, plugins included, and move
any common definitions up to the main core sitemap.
For all componen
Thorsten would you please configure your svn client ...
http://www.apache.org/dev/version-control.html#https-svn
has a .subversion/config file list of filename extensions.
I need to regularly clean up your commits.
-David
> Author: crossley
> D
Ferdinand Soethe wrote:
> Nicola Ken Barozzi wrote:
>
> > AFAIK, from what I have read as answers to this question over the years,
> > the range should contain the year of creation and the year of the last
> > modification.
>
> > If it's a legal necessity or just customary... IANAL.
>
> Just gue
[ http://issues.apache.org/jira/browse/FOR-647?page=all ]
Anil Ramnanan updated FOR-647:
--
Attachment: locationmapView.240805.diff
Creates the appropriate entries when an item is dropped from the Repository
Viewer
> Locationmap View needs to handle drop re
Locationmap View needs to handle drop requests from the Repository Browser
--
Key: FOR-647
URL: http://issues.apache.org/jira/browse/FOR-647
Project: Forrest
Type: New Feature
Components: Tool:
David Crossley wrote:
Addi wrote:
David Crossley wrote:
I suggest that we do a test of one quiet directory,
to ensure that our various text editors do the job
consistently.
Agreed. Not much point to cleaning up if we have to clean up afterwards
because someone's editor was out
[ http://issues.apache.org/jira/browse/FOR-646?page=all ]
Addison Berry updated FOR-646:
--
Attachment: whitespace-cleanup.txt.diff
Cleaned it up using tree command...
> Corrected whitespace cleanup dir tree
> -
>
>
Corrected whitespace cleanup dir tree
-
Key: FOR-646
URL: http://issues.apache.org/jira/browse/FOR-646
Project: Forrest
Type: Task
Components: Other
Versions: 0.8-dev
Reporter: Addison Berry
Priority: Trivial
A
> Jalopy was mentioned during that big cocoon-dev thread.
> Follow the links from http://issues.apache.org/jira/browse/FOR-644
>
> For some reason, we decided not to use it. Perhaps because
> periodic cleanups can still cause havoc for people who
> are working on those files. A lot of Cocoon peopl
On Wed, 2005-08-24 at 09:54 -0400, Tim Williams wrote:
...
> > >>If I understand you the functionality is the same, and appears to be
> > >>more flexible in the locationmap (although I'm in a noisy net cafe and
> > >>cannot concentrate fully). Can we stick to just one solution?
> > >
> > >
> > > Ye
First of all, we need a sample XHTML2 document that we will use to
render. It will contain all the module elements and attributes that we
will use and should be regularly updated to keep the new ones as we
progress. The content should be a description of the tags being used, so
to keep the documen
On 8/24/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
> Thorsten Scherler wrote:
> > On Mon, 2005-08-22 at 18:13 +0100, Ross Gardler wrote:
> >
> >>Thorsten Scherler wrote:
> >>
> >>>On Fri, 2005-08-19 at 09:52 +0100, Ross Gardler wrote:
> >>>
> >>>
> [EMAIL PROTECTED] wrote:
>
>
>
David Crossley wrote:
I am going to use this example to help explain some
of the problems with line-endings.
Ross, svn log shows that you added the initial
MANIFEST.MF file.
It already had mixed line endings. (By the way,
that makes me wonder about the origin of the code.)
In Eclipse there ar
Thorsten Scherler wrote:
On Mon, 2005-08-22 at 16:29 -0400, Tim Williams wrote:
Assuming I understand what this is doing, I don't immediately see why
this couldn't be done with either the locationmap or a
ResourceExistsSelector in the sitemap itself.
We had the ResourceExistsSelector in the
[ http://issues.apache.org/jira/browse/FOR-605?page=all ]
Gavin updated FOR-605:
--
Attachment: forrest_faq.png
I am investigating this, and it seems there is doubled up use of margins and
padding in adjacent areas of the stylesheet. For instance the width of a page
Thorsten Scherler wrote:
On Mon, 2005-08-22 at 18:13 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
On Fri, 2005-08-19 at 09:52 +0100, Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Author: thorsten
Date: Thu Aug 18 17:44:00 2005
New Revision: 233401
...
Added:
forrest/trunk/
David Podunavac wrote:
sorry for late responding to your questions! was busy
[Note I am confused about this publication-sitemap.xmap file. Does
publication in its title mean the publication of documents, or is it
the publication that make up a Lenya site? I suspect it is the later
very confusi
Subject: Re: Problems transforming XHTML
|
| Ferdinand Soethe wrote:
|
| > Problem solved or rather 'gone away'. After updating to today's version
| > of Forrest and freshly seeding the site XHTML is supported as
| > expected.
|
| After some more experimenting:
|
| For XHTML to work properly
On Tuesday August 23 2005 10:58 pm, David Crossley wrote:
> Addi wrote:
> > David Crossley wrote:
> > >We could add a list of all directories to a file in the
> > >"etc" directory. You can still see remnants of previous
> > >half-finished jobs there. That list could provide notice
> > >of which sec
On Wed, 2005-08-24 at 12:15 +0200, Ferdinand Soethe wrote:
> Thorsten Scherler wrote:
>
> > grep "ForrestTable" * -r|grep -v .svn|grep class
>
> > brings:
> > forrest-trunk/main/webapp/skins/common/xslt/html/document2html.xsl:
> >
>
> Hmm. Taking one closer look at this document I realized that
Ferdinand Soethe wrote:
> But then (pardon my desire to understand this), how do you explain
> that I already get
>
>
> when I call http://localhost:/body-lernorte.html
Although removing the fixed class in
forrest-trunk/main/webapp/skins/common/xslt/html/document2html.xsl
does indeed fix
Thorsten Scherler wrote:
> grep "ForrestTable" * -r|grep -v .svn|grep class
> brings:
> forrest-trunk/main/webapp/skins/common/xslt/html/document2html.xsl:
>
Hmm. Taking one closer look at this document I realized that this is
part of the skinning.
But then (pardon my desire to understand thi
Thorsten Scherler wrote:
> May the power of grep be with you. ;-) BTW any decent IDE let you search
> for test occurrence within a directory.
Thanks oh thee wizard of grep :-)
But I was really trying to understand the sequence of steps in the
pipeline to fix this among other problems.
One rea
On Wed, 2005-08-24 at 11:15 +0200, Ferdinand Soethe wrote:
> I keep finding bugs in the html pipeline that I'm using for xhtml.
> One of them is that the transformation will overwrite any existing
> class-attributes in with class='forresttable'.
>
> In order to fix that I'm trying to identify the
I keep finding bugs in the html pipeline that I'm using for xhtml.
One of them is that the transformation will overwrite any existing
class-attributes in with class='forresttable'.
In order to fix that I'm trying to identify the current html-pipeline
in head but keep getting tangled up in my lack
Ferdinand Soethe wrote:
> Problem solved or rather 'gone away'. After updating to today's version
> of Forrest and freshly seeding the site XHTML is supported as
> expected.
After some more experimenting:
For XHTML to work properly you may have a doctype declaration but must
NOT have a namespac
On Wed, 2005-08-24 at 10:31 +0200, Nicola Ken Barozzi wrote:
> First of all, please read the XHTML2 spec in the latest form ATOP:
>
> http://www.w3.org/TR/2005/WD-xhtml2-20050527/
>
> Don't cheat, have you really read it? ;-P
>
> To be sure, I'll leave some space on this page...
>
>
>
>
>
Any reason not to move these to sitemap.xmap?
>
>
>src="org.apache.cocoon.generation.HTMLGenerator">
> WEB-INF/jtidy.properties
>
> src="org.apache.cocoon.generation.TextGenerator">
>
>
> src="org.apache
Addi wrote:
> David Crossley wrote:
> >
> >I suggest that we do a test of one quiet directory,
> >to ensure that our various text editors do the job
> >consistently.
>
> Agreed. Not much point to cleaning up if we have to clean up afterwards
> because someone's editor was out of line.
I added so
First of all, please read the XHTML2 spec in the latest form ATOP:
http://www.w3.org/TR/2005/WD-xhtml2-20050527/
Don't cheat, have you really read it? ;-P
To be sure, I'll leave some space on this page...
Have you really read it?
I'll wait some more time
Diwaker Gupta wrote:
> Can we use something like Jalopy (http://jalopy.sf.net) to periodically clean
> up all the Java files? It doesn't need to be a Forrest. One of us can run it
> through once in a while (I'm happy to volunteer). I've used Jalopy in the
> past -- it works really well, its high
Ross Gardler wrote:
...
> Here's what I think is required (off the top of my head whilst the
> cricket is rained off, this is in no way complete or well thought out):
>
> - agree the subset of XHTML2 to be used
> - create DTD's
Decide how to make the pipeline process.
Now we have body-*.html and
Nicola Ken Barozzi wrote:
> AFAIK, from what I have read as answers to this question over the years,
> the range should contain the year of creation and the year of the last
> modification.
> If it's a legal necessity or just customary... IANAL.
Just guessing:
To include the year of creation i
Can we use something like Jalopy (http://jalopy.sf.net) to periodically clean
up all the Java files? It doesn't need to be a Forrest. One of us can run it
through once in a while (I'm happy to volunteer). I've used Jalopy in the
past -- it works really well, its highly customizable, and has exce
David Crossley wrote:
> Jan Materne wrote:
>
>>David Crossley wrote:
...
>>>I have no idea what a range of years is supposed to mean.
>>>
>>>We could go through our SVN and get rid of the range and just
>>>put the year of creation. That would make our job easier.
>>
>>In Ant we are using the crea
47 matches
Mail list logo
