At 16:21 2001-6-26 -0400, you wrote:
>On 6/26/01 4:13 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
>
> > On 6/26/01 4:02 PM, "Xun Liu" <[EMAIL PROTECTED]> wrote:
> >
> >> So, it means I cannot have a central point to set the layout template and
> >> have to call setLayoutTemplate() after setScreenTemplate() or overwrite
> >> doPostBuildTemplate()? Right?
> >
> > I assume that you have a set of templates for the user admin1, yes?
> >
> > If so the you can put all your screen templates in a directory like:
> >
> > /templates/app/screens/admin1
> > template1.vm
> > template2.vm
> >
> > Then you can have a layout for all these screens by having
> > a directory like:
> >
> > /templates/app/layouts/admin1
> > Default.vm
> >
> > That Default.vm template is your central location for controlling
> > which layout is used for the admin1 screen templates. You
> > should need to use the setScreenTemplate/setLayoutTemplate
>
>Sorry, that should be: "You should NOT need to use the setScreenTemplate/
>setLayoutTemplate"
>
> > if this is what you're trying to accomplish.
> >
> > Do I have your scenerio right? If not please correct me and
> > we'll try to figure something else out.
> >
> > Then
Not exactly. Different users will share the same templates, but different
layout and
look/feel.
The actual requirement is that for the same system, I can customize its
look and
feel for different organizations, which can be considered as the users of
the system.
The customization should include the layout of the page and can be done
without
recompiling the system.
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
