Henning P. Schmiedehausen wrote:
I would also add that the UIService in cvs under proposals is a much more flexible implementation - see: http://cvs.apache.org/viewcvs.cgi/jakarta-turbine-2/proposals/seade/UIService/readme.txt?rev=1.1&view=markup"Doug Brower" <[EMAIL PROTECTED]> writes:
There is a tantalizing article in the Turbine 2 User Guide regarding Turbine's skinning feature: http://wiki.apache.org/jakarta/JakartaTurbine2UsersGuide/TurbineSkins
The article is fairly recent, but the folder layout described in the article is created through the TDK only, not by META (at least, not through the simple turbine:setup goal). So I'm wondering if the skinning feature itself, accessed in Velocity templates with $ui, is on the way out; does anyone recommend using it to build skinned applications with Turbine?
well, the /resources folder is set up, but you should be able to create the sub directory by yourself.
The $ui tool must be activated and I don't think that it is by default. So you must uncomment the tool.ui. line in the TurbineResources.properties
I haven't used this tool in any of my applications yet. Code examples wanted.
I would actually like to get this in as a replacement for the existing service for 2.4. Unless anyone has any objections I will replace the existing code with that in the proposal and add the missing documentation (I was sure there was xdoc documentation for the UIService, but it appears there is not).
Scott
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
