Hi Thorsten and list,
Has anyone got pdf-link and txt-link contracts working in views? I
tried them out today. The pdf-link contract doesn't even run -- I get
the following exception:
X [0] linkmap.html BROKEN:
javax.xml.transform.TransformerException:
The only requried information in the sitemap is the URL. This means we
can create the Google sitemap now, with minimal effort. Over time we can
enhance this by adding further meta-data once it becomes available.
I'm happy to go for the Google format, I just thought that our
commitment to
Hello devs,
I propose to set the reply-to header of this mailing list to
forrest-dev by default.
How can I do that (as moderator) and should I call a vote before doing
it?
salu2
--
thorsten
Together we stand, divided we fall!
Hey you (Pink Floyd)
On Sat, 2005-06-04 at 21:03 -0700, Diwaker Gupta wrote:
Yes that would be great. :) That could be the 'last-published-net'
contract.
Its funny, I chose the *exact* same name even before I wrote my first mail :)
lol :)
Yeah, once started working with views and contracts the naming for
On Sat, 2005-06-04 at 23:03 -0400, Pedro I. Sanchez wrote:
On Sun, 2005-05-06 at 04:19 +0200, Thorsten Scherler wrote:
On Sat, 2005-06-04 at 20:55 -0400, Pedro I. Sanchez wrote:
snip/
My version of the Spanish messages would be the following:
catalogue
message key=Font
On Sun, 2005-06-05 at 02:16 -0700, Diwaker Gupta wrote:
Hi Thorsten and list,
Has anyone got pdf-link and txt-link contracts working in views? I
tried them out today. The pdf-link contract doesn't even run -- I get
the following exception:
X [0]
Ferdinand Soethe wrote:
The only requried information in the sitemap is the URL. This means we
can create the Google sitemap now, with minimal effort. Over time we can
enhance this by adding further meta-data once it becomes available.
I'm happy to go for the Google format, I just thought
Pedro I. Sanchez wrote:
On Sun, 2005-05-06 at 04:19 +0200, Thorsten Scherler wrote:
On Sat, 2005-06-04 at 20:55 -0400, Pedro I. Sanchez wrote:
...
Nice, can you prepare a patch and add it to this issue? I will apply it
then, thx. I reckon there are more to come. ;-)
Index:
Thorsten Scherler wrote:
Hello devs,
I propose to set the reply-to header of this mailing list to
forrest-dev by default.
How can I do that (as moderator) and should I call a vote before doing
it?
I have no problem with this since we already reply to [EMAIL PROTECTED] as far
as I am
Ross Gardler wrote:
Ferdinand Soethe wrote:
The only requried information in the sitemap is the URL. This means we
can create the Google sitemap now, with minimal effort. Over time we can
enhance this by adding further meta-data once it becomes available.
I'm happy to go for the Google
Thorsten Scherler wrote:
hello devs,
I just work on the i18n integration for pelt and crossed again the whys
for using views. ;-)
This mail makes for a pretty good piece of documentation.
A number of times over the last couple of weeks I have wanted to write a
mail asking you to write some
Trying to test the checksums-uri in cli.conf, I got really confused
and I'm not sure what is happening. Did I miss something or are there
indeed several nonfunctional settings in cli.conf?
I'd appreciate some comments on this.
Regards,
Ferdinand Soethe
Here is what I did
1. Seeded a new
After reading, studying *.xmap, and re-reading, I think I'm
understanding this a bit better. My question is should the
locationmap match be moved earlier in the pipeline? I got the
behaviour I would have expected by moving it immediately before all of
the i18n matches for regular source content.
On Sun, 2005-06-05 at 14:37 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
hello devs,
I just work on the i18n integration for pelt and crossed again the whys
for using views. ;-)
This mail makes for a pretty good piece of documentation.
:) It explains a wee bit better what I
Tim Williams wrote:
After reading, studying *.xmap, and re-reading, I think I'm
understanding this a bit better. My question is should the
locationmap match be moved earlier in the pipeline? I got the
behaviour I would have expected by moving it immediately before all of
the i18n matches for
Thorsten Scherler wrote:
On Sun, 2005-06-05 at 14:37 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
...
So I was going to ask you to write a simple How-To on
creating a new contract, and then embedding it in my own site.
Yeah I can understand that. Did you see
Thorsten Scherler wrote:
I need as well to write some slides for the upcoming workshop about
views. How did you do it again within forrest. ;-)
You need the s5 plugin http://forrest.apache.org/0.7/docs/plugins/#s5 .
This is not available in our SVN because it includes some GPL code.
You
Thorsten Scherler wrote:
Hello devs,
I propose to set the reply-to header of this mailing list to
forrest-dev by default.
How can I do that (as moderator) and should I call a vote before doing
it?
salu2
¿?¿?¿?¿?¿ is not the default behaviour?
I can see this:
Reply-To:
On 6/5/05, Ross Gardler [EMAIL PROTECTED] wrote:
Tim Williams wrote:
After reading, studying *.xmap, and re-reading, I think I'm
understanding this a bit better. My question is should the
locationmap match be moved earlier in the pipeline? I got the
behaviour I would have expected by
I added the real txt-link into trunk. Thx for the report.
Muchas gracias
de nada :)
Couple of suggestions:
o keep the contracts consistent. For instance, the div tag in pdf-link
has an id of 'pdf', while the one in txt-link has a _class_ of
'podlink'
o since we expect only one pdf-link and
Forgot one more thing:
The *-link contracts currently generate a br/ tag after the link. I
don't think this is a good idea, since it interferes with the layout.
Ideally, we can just leave the div tags and let the skin authors worry
about the placement.
--
Diwaker Gupta
Hi everyone,
I'm working on a new skin using views/viewHelper. Its nothing
fantastic. Just has the following goals:
o minimalistic, yet functional view
o use as few images as possible (read none, apart from the txt/pdf icons)
o render reliably across majority of browsers.
You can check it out
On Sun, 2005-06-05 at 12:10 -0700, Diwaker Gupta wrote:
Hi everyone,
I'm working on a new skin using views/viewHelper. Its nothing
fantastic. Just has the following goals:
o minimalistic, yet functional view
o use as few images as possible (read none, apart from the txt/pdf icons)
o
On Wed, 2005-06-01 at 11:28 +0200, Juan Jose Pablos wrote:
Thorsten Scherler wrote:
Hello devs,
I propose to set the reply-to header of this mailing list to
forrest-dev by default.
How can I do that (as moderator) and should I call a vote before doing
it?
salu2
¿?¿?¿?¿?¿
Tim Williams wrote:
On 6/5/05, Ross Gardler [EMAIL PROTECTED] wrote:
Tim Williams wrote:
After reading, studying *.xmap, and re-reading, I think I'm
understanding this a bit better. My question is should the
locationmap match be moved earlier in the pipeline? I got the
behaviour I would
Thorsten Scherler wrote:
I like it. Actually since we dropped the css support on a contract base
we need a default.css for the viewHelper.xhtml. That is the only reason
why I have not deleted the css stuff out of the contracts.
Something with the above mentioned goals would work great for us
I *really* like it. Especially if it is using views. Fantastic!
Thanks :)
Some observations:
http://resolute.ucsd.edu/diwaker/articles/index.html The first bullet in
the lists (not the TOC) have a blank line.
http://resolute.ucsd.edu/diwaker/articles/why-forrest.html (and many
other
I am +1 to use your skin as dev version for views this will allow to
concentrate on the contracts and not the css.
Can we use yours? Then I do not have to worry anymore about tweaking the
scale-dev and finally got rid of the css-overhead.
Sure!
For submitting a skin with view/viewHelper
Hi everyone,
I know that Forrest allows using JTidy to clean up raw-HTML pages. I
would like to use JTidy by default to clean up the HTML *after the
final processing stage*. Right now the HTML that is produced is ok,
but a nicely formatted HTML would be nice (and easier to debug!)
I not
On Sun, 2005-06-05 at 15:10 -0700, Diwaker Gupta wrote:
I am +1 to use your skin as dev version for views this will allow to
concentrate on the contracts and not the css.
Can we use yours? Then I do not have to worry anymore about tweaking the
scale-dev and finally got rid of the
Diwaker Gupta wrote:
Some observations:
http://resolute.ucsd.edu/diwaker/articles/index.html The first bullet in
the lists (not the TOC) have a blank line.
http://resolute.ucsd.edu/diwaker/articles/why-forrest.html (and many
other pages) there is a change in font towards the end of Take One.
Thorsten Scherler wrote:
On Sun, 2005-06-05 at 15:10 -0700, Diwaker Gupta wrote:
I reckon a new element in the forrest.properties would be the best. e.g.
view.xhmtl.skin.name=minimalistic
or
view.xhmtl.skin.name=scale
As long as it is not added to the default properties, that would serve
to
Ross Gardler wrote:
Ferdinand Soethe wrote:
David Crossley wrote:
Cocoon-related questions would get better answers on cocoon-users.
Is there an easy way to do this w/o subscribing to their list? My
mailbox is already getting a bit crowded :-)
You might be able to send email to their
[ http://issues.apache.org/jira/browse/FOR-520?page=all ]
Diwaker Gupta updated FOR-520:
--
Attachment: minimalistic.zip
Added zip file. Contains default.fv and default.css. No additional contracts
required.
new skin using views
Ferdinand Soethe wrote:
Trying to test the checksums-uri in cli.conf, I got really confused
and I'm not sure what is happening. Did I miss something or are there
indeed several nonfunctional settings in cli.conf?
I'd appreciate some comments on this.
As we already said, cocoon-users list.
On Sun, 2005-06-05 at 23:01 +0100, Shaun Evans wrote:
I like it too, and I'm glad to see that there is some progress that is
visible to end users! I would like to continue to maintain scale-dev but
I have ran into problems with view/viewHelper, namely the lack of a
getting started guide.
Thorsten Scherler wrote:
Juan Jose Pablos wrote:
Thorsten Scherler wrote:
Hello devs,
I propose to set the reply-to header of this mailing list to
forrest-dev by default.
How can I do that (as moderator) and should I call a vote before doing
it?
salu2
On Sun, 2005-06-05 at 23:01 +0100, Shaun Evans wrote:
I like it too, and I'm glad to see that there is some progress that is
visible to end users! I would like to continue to maintain scale-dev but
I have ran into problems with view/viewHelper, namely the lack of a
getting started guide.
On Sun, 2005-06-05 at 16:19 -0700, Diwaker Gupta wrote:
Actually something is terribly wrong with the recent versions of
Firefox. They don't render the skin correctly. I have validated the
XHTML on validator.w3.org and apart from the namespace issue, the skin
validates *perfectly*.
On Mon, 2005-06-06 at 00:10 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
On Sun, 2005-06-05 at 15:10 -0700, Diwaker Gupta wrote:
I reckon a new element in the forrest.properties would be the best. e.g.
view.xhmtl.skin.name=minimalistic
or
view.xhmtl.skin.name=scale
As long as
On Mon, 2005-06-06 at 02:40 +0200, Thorsten Scherler wrote:
I hope I fixed it in trunk (e.g. txt-link.ft):
I just committed.
hopes that is better now. ;-)
salu2
--
thorsten
Together we stand, divided we fall!
Hey you (Pink Floyd)
[
http://issues.apache.org/jira/browse/FOR-510?page=comments#action_12312705 ]
David Crossley commented on FOR-510:
No need for special instructions for Mac OS X (== UNIX) unless you are meaning
the old
Mac OS.
Setting Environment Variables
On Sun, 2005-06-05 at 16:19 -0700, Diwaker Gupta wrote:
Actually something is terribly wrong with the recent versions of
Firefox. They don't render the skin correctly. I have validated the
XHTML on validator.w3.org and apart from the namespace issue, the skin
validates *perfectly*.
[ http://issues.apache.org/jira/browse/FOR-465?page=all ]
David Crossley reopened FOR-465:
Assign To: (was: David Crossley)
You must be confused. This message still exists.
Logging Error: Writing event to closed stream.
On Sun, 2005-06-05 at 21:55 +0100, Ross Gardler wrote:
Diwaker Gupta wrote:
Hi everyone,
I'm working on a new skin using views/viewHelper. Its nothing
fantastic. Just has the following goals:
o minimalistic, yet functional view
o use as few images as possible (read none, apart
[ http://issues.apache.org/jira/browse/FOR-520?page=all ]
Thorsten Scherler reassigned FOR-520:
-
Assign To: Thorsten Scherler
new skin using views
Key: FOR-520
URL:
[ http://issues.apache.org/jira/browse/FOR-520?page=all ]
Thorsten Scherler closed FOR-520:
-
Resolution: Fixed
I appllied the patch to trunk. Thanks. I guess in the beginning we will focus
on the bugs of the selected contracts. ;-) Mostly it is
On Mon, 2005-06-06 at 03:43 +0200, Thorsten Scherler wrote:
On Sun, 2005-06-05 at 21:55 +0100, Ross Gardler wrote:
Diwaker Gupta wrote:
Hi everyone,
I'm working on a new skin using views/viewHelper. Its nothing
fantastic. Just has the following goals:
o minimalistic, yet
On 6/5/05, Ross Gardler [EMAIL PROTECTED] wrote:
Tim Williams wrote:
On 6/5/05, Ross Gardler [EMAIL PROTECTED] wrote:
Tim Williams wrote:
After reading, studying *.xmap, and re-reading, I think I'm
understanding this a bit better. My question is should the
locationmap match be moved
Ross Gardler wrote:
Ross Gardler wrote:
I would like to suggest yet another alternative for 0.7 for the issue of
raw HTML. This would be one in the form of a FAQ, a link to the FAQ from
the upgrade doc and a demo in fresh-site - in other words there is no
complex implementation to hold
Ross Gardler wrote:
I can't remember who wrote the locationmap code it was so long ago.
It was Unico Hommes, a Cocoon developer.
svn log java/org/apache/forrest/locationmap/lm/LocationMap.java
--David
[
http://issues.apache.org/jira/browse/FOR-514?page=comments#action_12312710 ]
David Crossley commented on FOR-514:
(Bringing over a comment and a patch from Cyriaque Dupoirieux which were added
during the move of our Jira.)
- Udpate of the Status DTD
[ http://issues.apache.org/jira/browse/FOR-514?page=all ]
David Crossley updated FOR-514:
---
Attachment: 514-patch.txt
Do not limit status.xml contexts in project info plugin
---
Key: FOR-514
I'd like to clarify my understanding of the use of cocoon protocols in
forrest. The cocoon documentation says:
# context:// - get a resource using the servlet context
# cocoon:/ - get a pipeline from the current sitemap
# cocoon:// - get a pipeline using the root sitemap
# resource:// - get a
Wow, too many mails in a flurry! :)
I can't reply to all of them, but let me just say 'perfecto! muy bien
señor!!' :)
This thread has become quite long, I think I'll start a new one for
the rest of my mail.
I recommend you to make an update of your production site. ;-)
Done!
--
Diwaker
55 matches
Mail list logo
