Or still use VelocityECSLayout and use iframe instead of frame. This requires some DHTML experiences. There is a browser constraint though, to my knowledge, IE 6 and NS 7 handles iframe tags but differently. NS 4 will simply blank. I guess it all depends on which browser your users use.

For example, you could use the following as a layout template, and

<script language="javascript" type="text/javascript">
function window.onload // I forget what the syntax for onload function name really is, somthing like this
{
var top = docuemnt.getElementById('HomeTop');
//position them either in CSS or in here
// and set content like
top.src='$link.setPage("somepage.vm")';
....
}
</script>

<div id="Top" class="TopNavBlock">
$navigation.setTemplate("/HomeTop.vm")
</div>
<div id="Content" class="ContentBlock">
// preset content, or use javascript to change content later.
<iframe id="ContentFrame" src="$link.setPage("Empty.vm")" class="ContentFrame">
</iframe>
// you could even use vtl like this
#if ( $data.getMessage() )
<iframe id="MessageFrame" class="MessageFrame">
</iframe>
#end
</div>
<div id="Bottom" class="BottomNavBlock">
$navigation.setTemplate("/Bottom.vm")
</div>

All in all, turbine has provided a great framework on the server side, and you will have to choose what you use to deliver business objects.
Since the pages are assembled before there are served, many of DHTML tricks can be applied.

Hope this helps.

Mitch Christensen wrote:
If you prefer to use frames, replace VelocityECSLayout as the layout manager
(in TRP) with VelocityOnlyLayout.

The problem with frames is that you need to create a <frameset/> page (w/o
the <html/> tags).  Unfortunately, the VelocityECSLayout manager generates
the <html> tags programmatically, preventing you from outputting a valid
<frameset/>.

-Mitch

-----Original Message-----
From: Engelhardt, ITS BetrWi AE2, FD
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 6:10 AM
To: 'Turbine Users List'
Subject: AW: No Index.vm screen when changing the default layout


You will always have problems if you use frames.

Scann the newsarchiv for frames and you will get several hits to that
subject.

I tried months ago to achieve the same but i had to give up und redesign my
app with no frames. But now i'll recommend to use turbine without frames und
you get everything done easy and you wont miss frames.

Good Luck
Dieter

-----Urspr�ngliche Nachricht-----
Von: Kleinhenz Thorsten [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 19. November 2002 14:54
An: '[EMAIL PROTECTED]'
Betreff: No Index.vm screen when changing the default layout


Hello,

I'm working with Turbine 2.1 (TDK) and want to create my own application.
Therefor I first created the sample app to have a Flux user management. This
works so far.
But if I change the vm files to my own (intranet) website nothing happens. I
log into the system but no "Index.vm" is shown. As long as I don't change
the default layout vm I see the normal Flux Data Manager. If I change the
layout that it only contains a $screen_placeholder for my Index.vm screen
(where I define some frames) the application doesn't work any longer.
Does anyone have a suggestion. Maybe this is only a configuration problem?
By the way I'm not sure but I think it is ok when my vm files contains
javascript code?

Regards,
Thorsten

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
Wei He, Ph.D.
Email: [EMAIL PROTECTED]
Voice: (845)359-5621
Fax:   (845)359-1631


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to