On Mon, 25 Nov 2002, Andrew Hill wrote:
>
> A DOM based rendering methodology might be more appropriate for this sort of
> thing.
>
Those interested in DOM-based rendering, which you can then run through an
appropriate XSLT processing pipeline, should also take a look at STXX:
http://stxx.so
om: Andrew Hill [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 24, 2002 10:40 PM
To: Struts Developers List
Subject: RE: Velocity vs. JSP: objective tests?
A DOM based rendering methodology might be more appropriate for this
sort of thing.
For example the home baked view technology Im using
using the org.w3c.dom classes or with a whole bunch of
convienience methods XMLC provides).
-Original Message-
From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Dave Johnson
Sent: Saturday, November 23, 2002 06:53
To: [EMAIL PROTECTED]
Subject: Re: Velocity vs. JSP: objective tests?
Dav
t: Re: Velocity vs. JSP: objective tests?
On Friday, November 22, 2002, at 04:47 PM, Craig R. McClanahan wrote:
>>
>>> #foreach $result in $results {
>>>
>>> $result.ID
>>> $result.Name
>>>
>>> }
>>
>>
On Friday, November 22, 2002, at 04:47 PM, Craig R. McClanahan wrote:
#foreach $result in $results {
$result.ID
$result.Name
}
actually, this is syntax is almost completely wrong. :)
a more fitting example would be:
#foreach( $result in $sometool.results )
$re
Dave said:
> No offence taken, but I do have some comments, which are below...
>
> >>>yeah, no offense intended to David Johnson, but that's a
> >>>really poor way to use Velocity. it looks as though that
> >>>method is intended to spit out some HTML hardcoded into
> >>>whatever $macros is or some
No offence taken, but I do have some comments, which are below...
yeah, no offense intended to David Johnson, but that's a
really poor way to use Velocity. it looks as though that
method is intended to spit out some HTML hardcoded into
whatever $macros is or some such thing. the HTML shouldn'
On Fri, 22 Nov 2002, Nathan Bubna wrote:
[big snip]
> > >
> > > #showNavBar( true)
> > >
> >
> > Fine ... still looks like a scriptlet to me :-).
>
> looks can be deceiving! with a proper velocimacro, the HTML isn't
> hard-coded into java classes. that may not be important to some folks, but
David Graham wrote:
JSP wouldn't be an option anyways because ordinary users wouldn't
understand it. The vast majority of situations are not like the one
you describe.
You are correct. More imporantly, if you are choosing
between JSP and Velocity as your Struts View technology
then the scenar
o: [EMAIL PROTECTED]
Subject: Re: Velocity vs. JSP: objective tests?
Date: Fri, 22 Nov 2002 17:53:28 -0500
David Graham wrote:
I've always found it amusing that people are worried about page authors
totally screwing up the application by executing arbitrary code. Who are
these rogue page authors
David Graham wrote:
I've always found it amusing that people are worried about page
authors totally screwing up the application by executing arbitrary
code. Who are these rogue page authors you're hiring that will
destroy your app?
What if, for example, you have an e-Commerce catalog and yo
Craig said:
...
> Sorry ... I was following an example from a published article (don't
> remember where) so I presume that it (at least) *used* to be correct :-0.
yeah, it may have been right (or closer) once, but not since at least two
years ago (when i started using velocity).
> > ...
> > > * V
Matt said:
> See comments below...
>
> > yeah, no offense intended to David Johnson, but that's a
> > really poor way to use Velocity. it looks as though that
> > method is intended to spit out some HTML hardcoded into
> > whatever $macros is or some such thing. the HTML shouldn't
> > come from t
On Fri, 22 Nov 2002, David Graham wrote:
> Date: Fri, 22 Nov 2002 14:55:55 -0700
> From: David Graham <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Velocity vs. JSP: objective tests?
>
> I'
" <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: Velocity vs. JSP: objective tests?
Date: Fri, 22 Nov 2002 13:47:48 -0800 (PST)
On Fri, 22 Nov 2002, Nathan Bubna wrote:
> Date: Fri, 22 Nov 2002 13:12:19 -0800
> From: Nathan Bubna <[EMA
On Fri, 22 Nov 2002, Matt Raible wrote:
> Date: Fri, 22 Nov 2002 14:38:02 -0700
> From: Matt Raible <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: 'Struts Developers List' <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
On Fri, 22 Nov 2002, Nathan Bubna wrote:
> Date: Fri, 22 Nov 2002 13:12:19 -0800
> From: Nathan Bubna <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Velocity vs. JSP
att
> -Original Message-
> From: Nathan Bubna [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 22, 2002 2:12 PM
> To: Struts Developers List
> Subject: Re: Velocity vs. JSP: objective tests?
>
>
> Craig said:
> ...
> > For example, here&
Craig said:
...
> For example, here's a simple little loop example in
> Velocity syntax and a couple approaches in JSP:
>
> Velocity:
>
>
> (Note -- it's assumed that the Customer collection has been stored in the
> VelocityContext by some preceding business logic.)
actually, if you are
David said:
> I believe the Velocity site has a comparison to JSP. Of course, they like
> Velocity better. If it's important that new developers be productive
> immediately I would go with JSP because that's a java standard that they
> will already know.
also, if you haven't already, be sure you
11/22/2002 1:14:45 PM, micael <[EMAIL PROTECTED]> wrote:
>I have settled on Struts as my application framework, assuming
>that there will continue to major shifts in the future (like the
>shift to 1.1 has been, which I like). However, I have not
>decided on the scripting language, if that is wha
On Fri, 22 Nov 2002, Karr, David wrote:
> Date: Fri, 22 Nov 2002 11:08:49 -0800
> From: "Karr, David" <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: RE: Velocity v
One thing that should be considered is not a technical issue. It's
clear that the number of JSP developers is much larger than Velocity
developers. That doesn't mean JSP is "better" than Velocity, but it
means that people and training will be more portable when using JSP.
Assuming that same popul
I believe the Velocity site has a comparison to JSP. Of course, they like
Velocity better. If it's important that new developers be productive
immediately I would go with JSP because that's a java standard that they
will already know.
David
From: micael <[EMAIL PROTECTED]>
Reply-To: "St
24 matches
Mail list logo