That is the purpose of the getLayout method in Screen. So use the first
method.
----- Original Message -----
From: Neeme Praks <[EMAIL PROTECTED]>
To: Turbine (E-mail) <[EMAIL PROTECTED]>
Sent: Tuesday, May 09, 2000 6:54 AM
Subject: publicLayout and secureLayout
> Hi all!
>
> I'm trying to implement a system with Turbine where some screens are
> available without requiring the user to log in and some require the user
> to log in.
> What would be the best way to achieve this?
>
> Right now I'm implementing the following solution:
> I have to Layouts, publicLayout and secureLayout: public shows the
> screen and the secure shows the login screen when not logged on.
>
> I have a question regarding this implementation:
> How do I nicely define that some screens use secure and others use
> public? Should I subclass the Screen.java with two separate screens:
> publicScreen.java and secureScreen.java that would have the
> getLayout(Rundata data) returning appropriate layout? Then I would
> subclass these screens for the actual screens...
> Or should I just write the getLayout(Rundata data) method for my actual
> pages to return the appropriate layout...
>
> I tend to like more the first approach because to is more abstract...
> But I would like to hear other comments...
>
> Neeme
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
