Stefano Mazzocchi [EMAIL PROTECTED] wrote:
on 6/23/03 8:29 PM Pier Fumagalli wrote:
SetAttribute vs Well-formedness:
[...]
#if {something}
paragraph class=myClass
#else
paragraph type=outerType
#end
/paragraph
Or we have setattribute a-la:
on 6/23/03 8:29 PM Pier Fumagalli wrote:
SetAttribute vs Well-formedness:
Briefly, I wanted to check with you people if a functionality like the XSLT
setattribute is required, or the non-well-formedness of Garbage is better
(see previous messages on this
Pier Fumagalli wrote:
SetAttribute vs Well-formedness:
Briefly, I wanted to check with you people if a functionality like the XSLT
setattribute is required, or the non-well-formedness of Garbage is better
(see previous messages on this thread)... Both approaces
On 24/6/03 23:58, Joerg Heinicke [EMAIL PROTECTED] wrote:
Pier Fumagalli wrote:
SetAttribute vs Well-formedness:
paragraph
#if {something}
[EMAIL PROTECTED]myClass}
#else
[EMAIL PROTECTED]outerType}
#fi
/paragraph
Think also in the case in which
on 6/22/03 2:01 PM Christopher Oliver wrote:
OK, I added GarbageGenerator to the scratchpad and integrated it with
the flow layer. I also added a copy of the Calculator flowscript sample
using the garbage generator to the scratchpad samples.
Wow, you guys rock! community power at work!
I
On 23/6/03 23:37, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
on 6/22/03 2:01 PM Christopher Oliver wrote:
OK, I added GarbageGenerator to the scratchpad and integrated it with
the flow layer. I also added a copy of the Calculator flowscript sample
using the garbage generator to the
OK, I added GarbageGenerator to the scratchpad and integrated it with
the flow layer. I also added a copy of the Calculator flowscript sample
using the garbage generator to the scratchpad samples.
I would also like to add a Garbage view to Petstore, but I need you to
implement #include first
on 6/19/03 8:23 AM Peter Royal wrote:
On Wednesday, June 18, 2003, at 05:53 PM, Pier Fumagalli wrote:
Unless I'm not mistaken, the above example template is _NOT_ a well
formed
XML document! :-) :-)
Of course! I guess it was more of a, why (nearly) re-invent the
wheel.. But obviously
I completely agree.
Stefano Mazzocchi wrote:
on 6/19/03 8:23 AM Peter Royal wrote:
On Wednesday, June 18, 2003, at 05:53 PM, Pier Fumagalli wrote:
Unless I'm not mistaken, the above example template is _NOT_ a well
formed
XML document! :-) :-)
Of course! I guess it was more of
Thank you for your kind support guys...
As Chris wants to play with the toy, I'll start putting it into the
scratchpad, but please note, garbage for now has its own build system and
stuff... For now (part one) I'll simply copy the CVS repo I have here on
betaversion, then, god knows!!! :-)
on 6/21/03 4:00 PM Pier Fumagalli wrote:
Thank you for your kind support guys...
As Chris wants to play with the toy, I'll start putting it into the
scratchpad, but please note, garbage for now has its own build system and
stuff... For now (part one) I'll simply copy the CVS repo I have
Pier Fumagalli wrote:
On 18/6/03 22:17, Peter Royal [EMAIL PROTECTED] wrote:
On Wednesday, June 18, 2003, at 01:34 PM, Pier Fumagalli wrote:
Concise question, concise answer:
Forget the XML syntax, use JXPath instead of JEXL for expressions...
Like:
document
#foreach $header in
Sylvain Wallez [EMAIL PROTECTED] wrote:
Unless I'm not mistaken, the above example template is _NOT_ a well formed
XML document! :-) :-)
Does this mean you wrote a parser to parse SAX-like events in a
non-well-formed XML document ?
Yes, I did, JavaCC is a handy tool from time to time...
On Wednesday, June 18, 2003, at 05:53 PM, Pier Fumagalli wrote:
Unless I'm not mistaken, the above example template is _NOT_ a well
formed
XML document! :-) :-)
Of course! I guess it was more of a, why (nearly) re-invent the
wheel.. But obviously it was to escape the XML syntax :)
-pete
Peter Royal [EMAIL PROTECTED] wrote:
On Wednesday, June 18, 2003, at 05:53 PM, Pier Fumagalli wrote:
Unless I'm not mistaken, the above example template is _NOT_ a well
formed
XML document! :-) :-)
Of course! I guess it was more of a, why (nearly) re-invent the
wheel.. But obviously it
Pier Fumagalli wrote:
Jelly could have a surface syntax that looks similar to Velocity. i.e.
someone could make a parser of Jelly that had a look-and-feel of Velocity for
common directives and expressions.
Now, what do I mean by simpler sintax? Imagine, for example a foreach
statement:
In XML
Joerg Heinicke [EMAIL PROTECTED] wrote:
Pier Fumagalli wrote:
ul
#foreach {parameters}
li[EMAIL PROTECTED]: [EMAIL PROTECTED]/li
#end
/ul
Having only read one article about XQuery with a few samples this *looks*
like XQuery for me. But my knowledge is not deep of course :-)
On Thursday, June 19, 2003, at 10:25 AM, Pier Fumagalli wrote:
ul
#foreach {parameters}
li[EMAIL PROTECTED]: [EMAIL PROTECTED]/li
#end
/ul
Sorry if I like the latter :-)
i can't argue that isn't clean, concise syntax :)
Basically, yes, I reinvented the wheel... I took two of the
Peter Royal wrote:
On Thursday, June 19, 2003, at 10:25 AM, Pier Fumagalli wrote:
It seems like your creation might be a good front-end for the alternate
jelly syntax that was mentioned :)
-pete
:) Every time I hear Jelly mentioned I remember someone's opinion
regarding Jelly and build
On 19/6/03 17:51, Peter Royal [EMAIL PROTECTED] wrote:
It seems like your creation might be a good front-end for the alternate
jelly syntax that was mentioned :)
The original scope of this RFI requested a separate repository for Garbage
from Cocoon exactly for this peculiar re-use of the
On 19/06/2003 19:39 Pier Fumagalli wrote:
The original scope of this RFI requested a separate repository for Garbage
from Cocoon exactly for this peculiar re-use of the parsing/templating
component outside the scope of Cocoon itself.
xml-commons? jakarta-commons-sandbox?
I mean: if not inside
On 19/6/03 18:51, Steven Noels [EMAIL PROTECTED] wrote:
On 19/06/2003 19:39 Pier Fumagalli wrote:
The original scope of this RFI requested a separate repository for Garbage
from Cocoon exactly for this peculiar re-use of the parsing/templating
component outside the scope of Cocoon itself.
On Thursday, June 19, 2003, at 02:17 PM, Pier Fumagalli wrote:
The idea of having a CVS repo separate from cocoon-2.1/src/scratchpad
would
simply ease third party people to access the parser and tree processor
without having to download Cocoon in all its 112 megs of glorious
code.
For sure
Le Mercredi, 18 juin 2003, à 02:07 Europe/Zurich, Pier Fumagalli a
écrit :
...It might not go anywhere, it might go somewhere, but if there's
interest in
this community to host my Garbage template engine, all I ask is to
have a
CVS repo and the opportunity to show you my little pet, and maybe
Vadim Gritsenko [EMAIL PROTECTED] wrote:
Pier Fumagalli wrote:
...
So, what do you think? (Surely I need some help to put together the brat)
If it provides getKey and getValidity, than it's much better velocity
than velocity in the cocoon-land!
You talking about caching? Yes, I
Bertrand Delacretaz [EMAIL PROTECTED] wrote:
Le Mercredi, 18 juin 2003, à 02:07 Europe/Zurich, Pier Fumagalli a
écrit :
...It might not go anywhere, it might go somewhere, but if there's
interest in
this community to host my Garbage template engine, all I ask is to
have a
CVS repo and
On Tuesday, June 17, 2003, at 08:07 PM, Pier Fumagalli wrote:
The most peculiar one is that I always _hated_ the fact that Velocity
output
need to be passed through a parser _every_time_ the content is
generated
(Velocity is stream-based, not SAX-based), so what my little template
does
is that
Peter Royal [EMAIL PROTECTED] wrote:
On Tuesday, June 17, 2003, at 08:07 PM, Pier Fumagalli wrote:
The most peculiar one is that I always _hated_ the fact that Velocity
output
need to be passed through a parser _every_time_ the content is
generated
(Velocity is stream-based, not
On Wednesday, June 18, 2003, at 01:34 PM, Pier Fumagalli wrote:
Concise question, concise answer:
Forget the XML syntax, use JXPath instead of JEXL for expressions...
Like:
document
#foreach $header in {request/headers}
#if {starts-with($header/name, 'X-'}
paragraph bold=true
On 18/6/03 22:17, Peter Royal [EMAIL PROTECTED] wrote:
On Wednesday, June 18, 2003, at 01:34 PM, Pier Fumagalli wrote:
Concise question, concise answer:
Forget the XML syntax, use JXPath instead of JEXL for expressions...
Like:
document
#foreach $header in {request/headers}
#if
[RFI] is a new subject tag I invented right now... It means request for
incubation... And I'll let you imagine what I'm coming up with...
I spent the last few weeks writing a clone of Velocity (yes, yet another
Webmacro clone), and I was wondering if the Cocoon project wanted to
incubate it...
Pier Fumagalli wrote:
...
So, what do you think? (Surely I need some help to put together the brat)
If it provides getKey and getValidity, than it's much better velocity
than velocity in the cocoon-land!
disclamer value=could be irrelevant
Have you seen discussions on re-implementation of XSP
Cool. When can I try it? I'll help you as long as you stop calling it
garbage ;)
Pier Fumagalli wrote:
[RFI] is a new subject tag I invented right now... It means request for
incubation... And I'll let you imagine what I'm coming up with...
I spent the last few weeks writing a clone of Velocity
33 matches
Mail list logo
