I think we can all agree that there are varying issues here. For some
environments, especially those that allow "htmlers" (which we all are) to
dink with backend code, jsp probably is not the best solution. For other
environments, it is a boon.
At 01:21 AM 10/8/2002 +0100, you wrote:
>On 8/1
on 2002/10/7 6:56 PM, "Martin Cooper" <[EMAIL PROTECTED]> wrote:
> You mean this, taken from the page, don't you?
>
>
> Hello
>
>
> #if ($request.getParameter("name") == null)
> Hello World
> #else
> Hello, $request.getParameter("name")
> #end
>
>
>
> At least if you're using JSP/JSTL, y
> -Original Message-
> From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 07, 2002 6:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Differences between Structs and Turbine ???
>
>
> on 2002/10/7 5:41 PM, "Martin Cooper"
> <[EMAIL PROTECTED]> wrote:
>
> > Of cour
on 2002/10/7 5:41 PM, "Martin Cooper" <[EMAIL PROTECTED]> wrote:
> Of course, I know Velocity fans won't like this any better, but if you bring
> the JSP example on that page up to date, using JSTL, you'll have this:
>
>
>
> Hello World
>
>
> Hello,
>
>
I dunno about you, but I would
Scott Eade <[EMAIL PROTECTED]> wrote on 08/10/2002 10:12:33 AM:
> > From: [EMAIL PROTECTED]
> >
> > #if (..)
> > #end
> >
> > in Velocity...?
> >
> >> "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote on 08/10/2002 09:50:15
AM:
> >>
> >> <%
> >> if (you.have(this).in.your(html)) {
> >>out.pr
> -Original Message-
> From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 07, 2002 5:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Differences between Structs and Turbine ???
>
>
> Actually, yes.
>
> Here is the specific reason(s):
>
> http://jakarta.apache.or
on 2002/10/7 5:21 PM, "Pier Fumagalli" <[EMAIL PROTECTED]> wrote:
> JSPs are the "root of all evil" because HTMLers think to have the power (and
> obligation, after a while) to blatantly destroy your entire container in
> less than 2 minutes of uptime... To that respect, even ASP are better...
>
on 2002/10/7 4:45 PM, "Pier Fumagalli" <[EMAIL PROTECTED]> wrote:
> It is, actually, but more than Mickey Mouse, it's the "Speedy Gonzales"
> version of JSP, given that per equivalent template (and rewriting tag
> libraries in Tea Applications), we kinda get a 3x performance boost! :-)
>
> Plus
On 8/10/02 1:12, "Scott Eade" <[EMAIL PROTECTED]> wrote:
> But the Velocity is much easier to teach to a web designer (non-programmer)
> than the JSP.
> http://jakarta.apache.org/velocity/ymtd/ymtd.html
More than easier to teach, is that it _forbids_ them to do what they're not
supposed to do...
Actually, yes.
Here is the specific reason(s):
http://jakarta.apache.org/velocity/ymtd/ymtd-saying-hello.html
Most specifically, if you want to make the word "doesn't" in the example
below bold...now, you have embedded HTML into your println...and we know it
isn't MVC to embed HTML into Java c
On 8/10/02 1:13, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> And to resurface the old issue, this is so much worse than
>
> #if (..)
> #end
>
> in Velocity...?
I believe that Andy doesn't quite know what "templates" are ! :-) Dude,
we're not talking about the beauty of XML around here, bu
> From: [EMAIL PROTECTED]
>
> #if (..)
> #end
>
> in Velocity...?
>
>> "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote on 08/10/2002 09:50:15 AM:
>>
>> <%
>> if (you.have(this).in.your(html)) {
>>out.println("Andy doesn't think its good");
>> }
>> %>
But the Velocity is much easier to teac
Nope. That sucks too. Not that my opinion should matter.
On Mon, 2002-10-07 at 20:13, [EMAIL PROTECTED] wrote:
> And to resurface the old issue, this is so much worse than
>
> #if (..)
> #end
>
> in Velocity...?
> --
> dIon Gillard, Multitask Consulting
> Work: http://www.multitask.com.a
And to resurface the old issue, this is so much worse than
#if (..)
#end
in Velocity...?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
"Andrew C. Oliver" <[EMAIL PROTECTED]> wrote on 08/10/2002 09:50:15 A
Right...my problem with JSP isn't its dogged speed its the conceptual
nastiness of it.
<%
if (you.have(this).in.your(html)) {
out.println("Andy doesn't think its good");
}
%>
-Andy
On Mon, 2002-10-07 at 19:45, Pier Fumagalli wrote:
> On 8/10/02 0:18, "Andrew C. Oliver" <[EMAIL P
On 8/10/02 0:18, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote:
> Looks like kind of a mickey mouse version of JSP to me... ;-) (I just
> couldn't resist...I just couldn't!)
It is, actually, but more than Mickey Mouse, it's the "Speedy Gonzales"
version of JSP, given that per equivalent template
Looks like kind of a mickey mouse version of JSP to me... ;-) (I just
couldn't resist...I just couldn't!)
On Mon, 2002-10-07 at 18:08, Pier Fumagalli wrote:
> On 7/10/02 22:01, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote:
>
> > While I think there are places that struts could learn a lot from
On 7/10/02 22:01, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote:
> While I think there are places that struts could learn a lot from
> turbine... Struts has a bit more "design cohesion" shall we say? Where
> turbine is a bit moreorganic in places.
>
> The nice thing about Turbine is that it
While I think there are places that struts could learn a lot from
turbine... Struts has a bit more "design cohesion" shall we say? Where
turbine is a bit moreorganic in places.
The nice thing about Turbine is that it does favor containment over
inheritance, same thing with Struts (not nec
On Sat, 2002-10-05 at 19:36, John McNally wrote:
> This is not really the correct place, but a short answer is struts is
> jsp-centric while turbine attempts to be neutral on the actual
> templating mechanism. Given that most jsp developers gravitate to
> struts means you get the best support if
20 matches
Mail list logo
