Cameron Riley wrote
> I added a small howto in velocity-site.xml in the xdocs;
>
>
>
> Frames are easily achieved with Velocity, the frameset tag
> being implemented
> at the screen level. The default setting for the
> layout.default directive in
> the TurbineResources.properties is the VelocityECSLayout class. The
> VelocityECSLayout wraps the Screen in Body tags. For frames
> this needs to be
> removed. The layout.default needs to be changed to;
>
> layout.default=VelocityOnlyLayout
>
> The layout Velocity template needs to point to the
> screen_placeholder. As an
> example modify the Default.vm in the /WEB-INF/templates/layouts/;
>
> $screen_placeholder
>
>
> The screen_placeholder marker will load and process the
> template marked as
> the template.homepage in the TurbineResources.properties. To
> create frames
> this is the template which will need to contain the frameset tag. Edit
> /WEB-INF/templates/screens/Index.vm;
>
> $page.setTitle("Frames example");
>
> <frameset>
> <frame src="$link.getPage(FrameTop.vm)" />
> <frame src="http://www.something.com/" />
> </frameset>
>
> Create a FrameTop.vm template in the
> /WEB-INF/templates/screens directory.
> The top frame will load this template. The reference to something.com
> requires an internet connection and is shown as an example,
> anything can be
> linked to the lower frame, another Velocity Screen for instance.
>
> ## Example FrameTop.vm
> <p><b>The FrameTop Velocity Template</b>
Great, Thanks!
Now with this and Jon's 'OO 101' lesson, I've tried lots of different
scenarios, with pretty good success, even if I'm not Java programmer.
I can't wait for the next TDK. Keep up the excellent work!
Don
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
