Well, I for one loathe JSPs and avoid them like the plague ;-) Many of the original Jetspeed 1 devs feel the same way and that is why all of the layouts and decorations are done the way they are.
Fortunately, the learning curve for Velocity is almost non-existent, yes it's that easy. It is also much easier to manipulate and control the rendering process of Velocity as it does not require a servlet container to be rendered. Eventually I would like to see us get away from Velocity and use no scripting language at all and instead use an approach similar to Wicket or Tapestry using tag replacement. Regards, -Scott > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Evans > Sent: Wednesday, November 30, 2005 11:38 AM > To: [email protected] > Subject: Re: Extract from a discusion on open source LMS > > Greg Reddin <greddin <at> apache.org> writes: > > > > Interestingly, I've found that Jetspeed does not necessarily use the > > same standards as I do So I'm battling with whether to learn > > Velocity or try to introduce more JSP examples into J2. For now, > > I'll probably learn velocity just for the reasons mentioned in that > > post. I don't want to roll my own version of everything. Would > > probably be better to just stick with what's already being done. > > > > I for one would love to see jsp versions of the velocity components. > I don't really want to learn velocity, I'm already having to learn enough > new technologies! :) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
