What exactly do you mean by "needs work"? Are there parts of the spec that are not implemented? Things that are implemented but broken?
Maybe there's another solution you can recommend. Here's my problem: I have a pretty large application deployed on Turbine. So far so good. The previous developer on this project used Velocity for all of the user interface. As the project team has grown, we have absorbed a couple of front-end designers. They all use Dreamweaver, and want the nice code-highlighting and other nifty stuff it can do. We haven't been able to make it work with Velocity, and are considering transitioning to JSP, which Dreamweaver has pretty good support for. Our existing codebase is simply too large to consider changing with our limited staff resources, so we were thinking about using JSP moving forward, while maintaining our existing Velocity stuff, and changing it to JSP as time/workload allows. Is there an easier way to do this? Is anybody else in this situation? -------------------------------------------- Nathan McMinn Application Developer NequalsOne - HealthCare marketing tools mailto:[EMAIL PROTECTED] http://www.NequalsOne.com -----Original Message----- From: Eric Pugh [mailto:[EMAIL PROTECTED] Sent: Monday, February 16, 2004 10:00 AM To: 'Turbine Users List' Subject: RE: Velocity and JSP Yes. But the JSP support needs work. > -----Original Message----- > From: Nathan Mcminn [mailto:[EMAIL PROTECTED] > Sent: Monday, February 16, 2004 4:41 PM > To: [EMAIL PROTECTED] > Subject: Velocity and JSP > > > Is it possible to use Velocity and JSP concurrently in a > single turbine > instance? > > -------------------------------------------- > Nathan McMinn > Application Developer > NequalsOne - HealthCare marketing tools > mailto:[EMAIL PROTECTED] > http://www.NequalsOne.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
