Scott Eade <[EMAIL PROTECTED]> writes: >> From: Daniel Rall <[EMAIL PROTECTED]> >> Hey Scott. I'm using an extension to Veocity's >> ClasspathResourceLoader in Eyebrowse <http://eyebrowse.tigris.org/>. >> Not directly applicable, but might be of help to see a working >> example. Tigris has CVSWeb, so you can browse the source online if >> you like. > > Thanks Dan. Eyebrowse uses Velocity without Turbine. I think the use of > ClasspathResourceLoader (or the extension used in Eyebrowse) with straight > Velocity is tried and tested. Turbine however has the added complication of > the directory structure (email, layouts, navigations, screens) that I am not > certain is dealt with anywhere. > > Given the lack of response am I to assume that nobody is using the default > ClasspathResourceLoader that is configured in TurbineResources.properties?
TurbineVelocityService feeds configuration parameters directly to the Velocity engine. If you've gotten the Velocity configuration right, it's probably Turbine's handling of layouts/navigations/screens/etc. that you'll want to scrutinize the inner workings of. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
