Pls note: There were no objections. So the views-workshop is moved to
Monday night. I'll try and write the announcement tomorrow.
Ferdinand
Ferdinand Soethe wrote:
OK, this all being explained, I now propose to move the views workshop
to Monday night for four reasons:
1. Nicola Ken will
Ferdinand Soethe wrote:
Pls note: There were no objections. So the views-workshop is moved to
Monday night. I'll try and write the announcement tomorrow.
I have our new Events web page almost finished. I will get that
published too.
--David
Tim Williams wrote:
I've got resources in resources.xmap looking at locationmap now. I
haven't done it for any non-image resource though.Should the
following matches be resolvable through locationmaps too? I can't
off the top of my head think of any reason why not but thought it
important
I tried to check back with Peter if Monday is
OK, too. Give me time until tomorrow 12:00 MEST
to get through to him. Thanks!
Johannes
Ferdinand Soethe schrieb:
Pls note: There were no objections. So the views-workshop is moved to
Monday night. I'll try and write the announcement tomorrow.
Tim Williams wrote:
I'm struggling determining whether the matching order of images can be
different from xml specifically with respect to locationmaps. Should
images *always* resolve through locationmaps as a last resort the same
as xml?
We should have two locationmaps: Forrest's and the
Diwaker asked me once about the naming conventions the contracts should
follow. I believe I never gave you an answer.
no problemas :)
Now leather-dev is based on this contracts. I reckon you can remember
the discussion about leather/scale-dev where we agreed that the designer
needs design
I got the OK from Peter for Monday!
So, please go ahead with the announcements
and events page.
Johannes
Johannes Schaefer schrieb:
I tried to check back with Peter if Monday is
OK, too. Give me time until tomorrow 12:00 MEST
to get through to him. Thanks!
Johannes
Ferdinand Soethe
[
http://issues.apache.org/jira/browse/FOR-530?page=comments#action_12313137 ]
Diwaker Gupta commented on FOR-530:
---
There's a small improvement in the compliance-links contract -- basically the
CSS validator was not using the referer field to
Johannes Schaefer wrote:
I got the OK from Peter for Monday!
So, please go ahead with the announcements
and events page.
Johannes
Thanks very much to Johannes and Peter.
So that is two events at HfT Monday evening and Wednesday evening,
plus your usability professionals meeting on Tuesday
for tue i already sent a link
for mon and wed we can decide shorthand
Peter said.
js
(leaving office NOW)
David Crossley schrieb:
Johannes Schaefer wrote:
I got the OK from Peter for Monday!
So, please go ahead with the announcements
and events page.
Johannes
Thanks very much to Johannes
Ross Gardler wrote:
Tim Williams wrote:
The way I understand it we're not depending on LinkRewriterTransformer
to resolve lm links so I don't understand why adding it to it's
schemes could help?
...
See the demo for the locationmap in fresh-site (locationmap branch
obviously). There is an
David Crossley wrote:
Tim Williams wrote:
I apologize up front for being a pest while you guys are prepping for
the release but...
No worries. Development continues on. You are not being a pest,
far from it. Thanks anyway for being so considerate.
Quite right, I am finding Tims help
[
http://issues.apache.org/jira/browse/FOR-530?page=comments#action_12313146 ]
Juan Jose Pablos commented on FOR-530:
--
done. ( we need to give a hand to Thorsten with your patches diwaker)
[views] New contract; compliance-links
David Crossley wrote:
Here is my proposal for the release plan. If people have
any concerns with the plan, then please raise them now.
Code freeze and testing starts on Sunday 2005-06-12 at 14:00 UTC [1].
During code freeze we cannot add any new functionality, just bug
fixes and documentation
Mikler wrote:
Hello! Ross!
For the benefit of other devs. Mikler wanted to do the forrest-voice
project, however, I already had considerable interest in that project. I
have said that I will consider any project put forward if the community
view it as useful. Hence Mikler has posted this
Juan Jose Pablos wrote:
David,
[EMAIL PROTECTED] wrote:
-html
+html xmlns:i18n=http://apache.org/cocoon/i18n/2.1;
-script type=text/javascript language=JavaScript!--
- document.write(Published: + document.lastModified);
- // --/script
+script
Pedro I. Sanchez wrote:
The string $(env.LANG} works well inside main/forrest.build.xml. It was
the default before you made changes to the trunk. But the same string is
ignored when you use it inside webapp/sitemap.xmap (skin labels are
looked up in the English dictionary, even if LANG=es_ES).
David Crossley wrote:
Juan Jose Pablos wrote:
David,
[EMAIL PROTECTED] wrote:
-html
+html xmlns:i18n=http://apache.org/cocoon/i18n/2.1;
-script type=text/javascript language=JavaScript!--
- document.write(Published: + document.lastModified);
- // --/script
David Crossley wrote:
Juan Jose Pablos wrote:
David,
[EMAIL PROTECTED] wrote:
-html
+html xmlns:i18n=http://apache.org/cocoon/i18n/2.1;
-script type=text/javascript language=JavaScript!--
- document.write(Published: + document.lastModified);
- // --/script
Tim Williams wrote:
I apologize up front for being a pest while you guys are prepping for
the release but...
I started my queries into sitemaps with the cocoon:/ cocoon://
protocols but now I'm starting to wonder whether we have other sitemap
related issues too. (Not issues in the sense of
Hi!
Is anyone currently working on the Need better
documentation explaining how to use tabs issue as
listed in the Issue Navigator - ASF Jira (FOR 511).
The ASF JIRA said nobody is assigned the issue and
that it is still unresolved. I have myself encountered
this problem many times while working.
On 6/9/05, Ross Gardler [EMAIL PROTECTED] wrote:
Nicola Ken Barozzi wrote:
Tim Williams wrote:
I've got resources in resources.xmap looking at locationmap now. I
haven't done it for any non-image resource though.Should the
following matches be resolvable through locationmaps too?
Juan Jose Pablos wrote:
Tim Williams wrote:
Currently, in most, but not all of the subsitemaps there are duplicate
transformer, generator, serializer declarations.
Anyone know why this is the way it is?
There were some discussion about it. some developers where againts it.
That is why
Every source file, with any mime-type, must be resolvable through
locationmaps.
I need to slow down and actually read I guess... Thanks for the
answer, I'll try to get a patch in the next day or two for
resources.xmap -- this one is going to need lots of testing.
--tim
Ross Gardler wrote:
Nicola Ken Barozzi wrote:
Tim Williams wrote:
I'm struggling determining whether the matching order of images can be
different from xml specifically with respect to locationmaps. Should
images *always* resolve through locationmaps as a last resort the same
as xml?
Ross Gardler wrote:
Yes, this is my biggest complaint about Daisy right now. Every single
change gets the same priority in the version management system. So if
I change a single letter, it create a new version and generates a commit
mail.
Wiki's deal with this by allowing you to mark
David Crossley wrote:
Pls note: There were no objections. So the views-workshop is moved to
Monday night. I'll try and write the announcement tomorrow.
I have our new Events web page almost finished. I will get that
published too.
If you have already finished the events page, then I
Ross Gardler wrote:
David Crossley wrote:
Here is my proposal for the release plan. If people have
any concerns with the plan, then please raise them now.
Code freeze and testing starts on Sunday 2005-06-12 at 14:00 UTC [1].
During code freeze we cannot add any new functionality, just bug
Any comments on this proposal?
Ferdinand
Ferdinand Soethe wrote:
David Crossley wrote:
- Set your Java version to be the lowest specified of our supported
versions.
Where is the definitive info on the supported versions? The FAQ says
we need Java 1.4 or better. Does that mean it has
Ferdinand Soethe wrote:
Any comments on this proposal?
Yes i sent comments under another thread name:
required Java version
Would someone please follow up. It is a very important point.
--David
Ferdinand Soethe wrote:
David Crossley wrote:
- Set your Java version to be the lowest
Does anyone know why that empty messages directory was published?
Are those CommonMessages files meant to be included?
--David
Author: crossley
Date: Thu Jun 9 08:35:15 2005
New Revision: 189766
URL: http://svn.apache.org/viewcvs?rev=189766view=rev
Log:
Publish some new documents.
Ayush Gupta wrote:
Hi!
Is anyone currently working on the Need better
documentation explaining how to use tabs issue as
listed in the Issue Navigator - ASF Jira (FOR 511).
The ASF JIRA said nobody is assigned the issue and
that it is still unresolved. I have myself encountered
this problem many
David Crossley wrote:
Ferdinand Soethe wrote:
Any comments on this proposal?
Yes i sent comments under another thread name:
required Java version
Would someone please follow up. It is a very important point.
I've switched on my lazy consensus mode for this issue. In other words
I agree
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Here is my proposal for the release plan. If people have
any concerns with the plan, then please raise them now.
Code freeze and testing starts on Sunday 2005-06-12 at 14:00 UTC [1].
During code freeze we cannot add any new
On Fri, 2005-06-10 at 01:45 +1000, David Crossley wrote:
Does anyone know why that empty messages directory was published?
Are those CommonMessages files meant to be included?
I am not sure but the messages should be in that dir.
The other question: I guess not I reckon it is because they are
Sorry, I completely missed that response in the flurry of postings.
David Crossley wrote:
I have similar concerns. Using 1.4.0 sounds very risky.
However we could not expect everyone to use the most recent 1.4.x
So would a compromise of 1.4.1 be the most sensible?
I disagree. For several
Yes, cheche is right that is i18n stuff, but actual do not know why that
is happening.
I may find time tomorrow to have a look, but you can beat me to it. ;-)
salu2
On Thu, 2005-06-09 at 12:57 +0200, Juan Jose Pablos wrote:
David Crossley wrote:
Juan Jose Pablos wrote:
David,
[EMAIL
Ross Gardler wrote:
I'd prefer to be a little more restrictive than allowing the sitemap
restructuring.
As I understand it, and would prefer it, even a minor
commit will result in us (you?) having to rebuild the release
distribution and us retesting.
If this understanding is right
This Howto is far from be finished and please forget the last paragraph
(Using contracts) because it is wrong!!!
I found a problem to display the installed contracts that I need to fix
before I can go on writing.
All view how-to's need proofreading.
salu2
thorsten
On Fri, 2005-06-10 at 01:45
Ferdinand Soethe wrote:
Sorry, I completely missed that response in the flurry of postings.
David Crossley wrote:
I have similar concerns. Using 1.4.0 sounds very risky.
However we could not expect everyone to use the most recent 1.4.x
So would a compromise of 1.4.1 be the most sensible?
I agree again with a small addition. The idea is that contracts are
within groups:
- branding
- nav
- search
- content
- siteinfo
That makes it easier to group the contracts by this functionalities and
adding new contracts based on the above mentioned categories. Using your
input I
[ http://issues.apache.org/jira/browse/FOR-200?page=all ]
Tim Williams updated FOR-200:
-
Attachment: for-200-resources.patch
Here's the patch to make resources resolvable through locationmaps. I'll keep
testing this as I go along.
--tim
Locationmap
To make that clear before I argue any further:
I accept that there are at least two people in favor of using 1.4.1
and so we should do that of course.
But I'd still like to argue my case :-)
Ross Gardler wrote:
1. If we test against anything other than the most recent fix version
of
Ferdinand Soethe wrote:
Backwards compatibility obviously cannot mean that a version with bugs
(that might cause problems with Forrest) will not cause this problem
because the fix version (where that bug is fixed) is supposed to be
backward compatible.
It would only mean that this fixed
Gregor J. Rothfuss wrote:
doug chestnut is working on WebDAV integration right now, which might
help with this. as a start, people could do their docs offline, and then
add them to lenya through webdav. lenya then takes care of checking
them in to the lenya revision control, doing workflow
Ross Gardler wrote:
I would prefer to see us test on 1.4.0 but since I'm not doing the
release process I'm happy with 1.4.1 if it makes your lives easier (it
actually makes mine harder as I don't have 1.4.1, I have 1.4.0 and
1.4.2, but not 1.4.1).
I think that this is trivial. When I had
Thorsten Scherler wrote:
Yes, cheche is right that is i18n stuff, but actual do not know why that
is happening.
I may find time tomorrow to have a look, but you can beat me to it. ;-)
-html
+html xmlns:i18n=http://apache.org/cocoon/i18n/2.1;
done.
+document.write(Last Published:?? +
[
http://issues.apache.org/jira/browse/FOR-528?page=comments#action_12313207 ]
Ross Gardler commented on FOR-528:
--
Almost there, still to do:
- add build properties to all other plugins (up to listLocations)
- disable local deploy from root plugins
Juan Jose Pablos wrote:
Thorsten Scherler wrote:
Yes, cheche is right that is i18n stuff, but actual do not know why that
is happening.
I may find time tomorrow to have a look, but you can beat me to it. ;-)
-html
+html xmlns:i18n=http://apache.org/cocoon/i18n/2.1;
done.
Hello devs,
FAQ: today suddenly views haven't worked anymore.
Possible problem: If this happens for you then check
http://xobjex.com/service/date.xsl in a browser.
If you do not get an answer in your browser, that is the problem.
Solution: change in your view a contract that causes cocoon to
On Fri, 2005-06-10 at 10:31 +1000, David Crossley wrote:
Thorsten Scherler wrote:
This Howto is far from be finished and please forget the last paragraph
(Using contracts) because it is wrong!!!
I found a problem to display the installed contracts that I need to fix
before I can go on
I learned from this that
select=document('http://xobjex.com/service/date.xsl')/date
is a dangerous thing to do in contracts.
Its a simple script -- Forrest can host it on its own website.
But even that is not required -- I had supplied a simple Python script
that generates this document. All
On 6/9/05, Diwaker Gupta [EMAIL PROTECTED] wrote:
I learned from this that
select=document('http://xobjex.com/service/date.xsl')/date
is a dangerous thing to do in contracts.
IMHO, here is the simplest solution:
o since we already use Ant, can we use the tstamp target [1] to set
some
On Thu, 2005-09-06 at 12:56 +0200, Juan Jose Pablos wrote:
Pedro I. Sanchez wrote:
The string $(env.LANG} works well inside main/forrest.build.xml. It was
the default before you made changes to the trunk. But the same string is
ignored when you use it inside webapp/sitemap.xmap (skin labels
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
During code freeze we cannot add any new functionality, just bug
fixes and documentation tweaks [4].
Does this also apply to the locationmap branch, that is branch in note
[4] means the release branch
55 matches
Mail list logo
