Nathaniel Alfred wrote:
From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
Instead of ? one could also use another character provided it is sufficiently
unlikely that the sequence curly-char appears in XSP-embedded content or where
XSP can be embedded (XSL). The special character should not be
Vadim Gritsenko [EMAIL PROTECTED] wrote on 06.06.2005 16:28:19:
I think it is a bad idea to use exactly the same syntax as for
XSLT because it
makes really awkward to use XSP attribute interpolation inside
logicsheets.
You haven't written any XSLT producing Ant files recently, have you?
-Original Message-
From: Jochen Kuhnle [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 31. Mai 2005 14:07
To: dev@cocoon.apache.org
Subject: RE: [RFE] Some enhancements to XSP
Any preferrences which character to use?
Out of purely unrational affection, I prefer #{ and }.
The fact
-Original Message-
From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 31. Mai 2005 15:30
To: dev@cocoon.apache.org
Subject: Re: [RFE] Some enhancements to XSP
Instead of ? one could also use another character provided it is
sufficiently
unlikely that the sequence
Nathaniel Alfred [EMAIL PROTECTED] wrote on 30.05.2005
18:09:59:
I would suggest a syntax as {?expr} which must be transformed by a
preprocessor
applied to XSPs and logicsheets:
img src={?logo}.gif/
== imgxsp:attribute name=srcxsp:expr(logo)+/xsp:expr.
gifxsp:attribute/img
Nathaniel Alfred wrote:
-Original Message-
From: Jochen Kuhnle [mailto:[EMAIL PROTECTED]
Sent: Freitag, 27. Mai 2005 15:02
To: dev@cocoon.apache.org
Subject: RE: [RFE] Some enhancements to XSP
and if(expr) code really starts to look bad.
XSP attribute interpolation makes
Nathaniel Alfred wrote:
But I agree that the xsp:attribute markup is too verbose. I'd rather
wish for the XSLT analogy:
xsp:attribute name=src value=source/
That can be trivially added - on top of what we have now. Not sure why it was
missing...
Shall we add it then?
Here's my +1.
+1.
Nathaniel Alfred wrote:
But I agree that the xsp:attribute markup is too verbose. I'd rather
wish for the XSLT analogy:
xsp:attribute name=src value=source/
That can be trivially added - on top of what we have now. Not sure why it was
missing...
Shall we add it then?
Here's my +1.
+1.
-Original Message-
From: Jochen Kuhnle [mailto:[EMAIL PROTECTED]
Sent: Freitag, 27. Mai 2005 15:02
To: dev@cocoon.apache.org
Subject: RE: [RFE] Some enhancements to XSP
If we filter the logic sheets, too, we can still move code back and forth
between XSP and logic sheet
Nathaniel Alfred [EMAIL PROTECTED] wrote on 26.05.2005
16:34:13:
I think I was too terse to make myself understand. With in-text
replacement
I meant
h1Hello {username}/h1
as shortcut for
h1Hello xsp:exprusername/xsp:expr/h1
I am against that because it risks to break
-Original Message-
From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 25. Mai 2005 20:47
To: dev@cocoon.apache.org
Subject: Re: [RFE] Some enhancements to XSP
3. A mechanism for expression replacement as in XSLT or JXTG, replacing
{expression} with a xsp:attribute element
-Original Message-
From: Antonio Gallardo [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 24. Mai 2005 23:53
To: dev@cocoon.apache.org
Subject: RE: [RFE] Some enhancements to XSP
On Mar, 24 de Mayo de 2005, 15:40, Nathaniel Alfred dijo:
Also for the src={source} shortcut I am sceptic
Nathaniel Alfred [EMAIL PROTECTED] wrote on 24.05.2005
22:40:32:
-Original Message-
From: Jochen Kuhnle [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 24. Mai 2005 13:45
To: dev@cocoon.apache.org
Subject: [RFE] Some enhancements to XSP
Hi, I know XSPs are supposed to go away, but I
Nathaniel Alfred wrote:
From: Jochen Kuhnle [mailto:[EMAIL PROTECTED]
Hi, I know XSPs are supposed to go away, but I still like 'em... I would
like to propose some enhancements, and if they're accepted also volunteer
to implement them (including documentation and examples :).
1. A
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:40, Nathaniel Alfred dijo:
Also for the src={source} shortcut I am sceptic. It breaks when
you want to move your img content markup from XSP to logicsheet.
But I agree that the xsp:attribute markup is too verbose. I'd rather
wish for
On Mie, 25 de Mayo de 2005, 14:06, Vadim Gritsenko dijo:
Antonio Gallardo wrote:
On Mar, 24 de Mayo de 2005, 15:40, Nathaniel Alfred dijo:
Also for the src={source} shortcut I am sceptic. It breaks when
you want to move your img content markup from XSP to logicsheet.
But I agree that the
Hi, I know XSPs are supposed to go away, but I still like 'em... I would
like to propose some enhancements, and if they're accepted also volunteer
to implement them (including documentation and examples :).
1. A logicsheet for cache key control to have an easy way to override
getKey. Something
-Original Message-
From: Jochen Kuhnle [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 24. Mai 2005 13:45
To: dev@cocoon.apache.org
Subject: [RFE] Some enhancements to XSP
Hi, I know XSPs are supposed to go away, but I still like 'em... I would
like to propose some enhancements
On Mar, 24 de Mayo de 2005, 15:40, Nathaniel Alfred dijo:
Also for the src={source} shortcut I am sceptic. It breaks when
you want to move your img content markup from XSP to logicsheet.
But I agree that the xsp:attribute markup is too verbose. I'd rather
wish for the XSLT analogy:
19 matches
Mail list logo
