You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by keith <ke...@kjsdesigns.com> on 2003/06/19 20:01:55 UTC
giving view to the graphic designer - HOW?
I love the idea of MVC, but I can't figure out how to put the choice of
navigation/layout into the hands of the vm screen builder. In other
words, if my vm designer had the page:
screens/x.vm:
------------------
<b>HelloWorld</b>
------------------
Is there any way he could specify inside the screen what
navigation/layout files to use? We have a number of both navigations
and layouts we want to use; the only way I can see this happening right
now is by storing each screen in the database, creating an online
editing tool, and forcing our screen developer to toggle the desired
areas using htmlforms... this sounds like extra work - is there a better
way?
Thanks
Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: giving view to the graphic designer - HOW?
Posted by keith <ke...@kjsdesigns.com>.
Many thanks!
keith
On Thursday, June 19, 2003, at 02:17 PM, Henning P. Schmiedehausen
wrote:
> keith <ke...@kjsdesigns.com> writes:
>
>> I love the idea of MVC, but I can't figure out how to put the choice of
>> navigation/layout into the hands of the vm screen builder. In other
>> words, if my vm designer had the page:
>
>> screens/x.vm:
>> ------------------
>> <b>HelloWorld</b>
>> ------------------
>
>> Is there any way he could specify inside the screen what
>> navigation/layout files to use? We have a number of both navigations
>> and layouts we want to use; the only way I can see this happening right
>> now is by storing each screen in the database, creating an online
>> editing tool, and forcing our screen developer to toggle the desired
>> areas using htmlforms... this sounds like extra work - is there a
>> better
>> way?
>
> $data.setLayoutTemplate("MyFancyLayout.vm") on your screen template.
>
> Navigation is then references from the layout template.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
___________________________________
Keith Seim • http://kjsdesigns.com
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: giving view to the graphic designer - HOW?
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
keith <ke...@kjsdesigns.com> writes:
>I love the idea of MVC, but I can't figure out how to put the choice of
>navigation/layout into the hands of the vm screen builder. In other
>words, if my vm designer had the page:
>screens/x.vm:
>------------------
><b>HelloWorld</b>
>------------------
>Is there any way he could specify inside the screen what
>navigation/layout files to use? We have a number of both navigations
>and layouts we want to use; the only way I can see this happening right
>now is by storing each screen in the database, creating an online
>editing tool, and forcing our screen developer to toggle the desired
>areas using htmlforms... this sounds like extra work - is there a better
>way?
$data.setLayoutTemplate("MyFancyLayout.vm") on your screen template.
Navigation is then references from the layout template.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org