Hi,
I ran into this problem while trying to integrate Flux
into Tambora. The modules for Flux and Tambora could be
separated into different packages which made adding the
Flux modules to a Turbine application nice. But having
to keep the Flux templates in the main Tambora templates
hierarchy is not really that nice.
I like the idea of jetspeed portlets: it would be nice
to have small mini-applications like flux that were
easily embedded withing a parent turbine application.
Just drop in a portlet/mini-app (whatever you want to
call it), which would consist of some modules and
some templates. It would be nice to keep them separated.
I like the idea of having separate template paths
if desired, or even different template sources
which velocity supports: say pulling a set of
templates from a JAR file. I would definitely
help you work on this as it would make Flux
integration a lot cleaner. It would make the
integration of many small applications much easier.
Having all the templates separated into their
own hierarchies according to portlet/mini-app
is definitely more desirable then having a big
jumble of templates.
jvz.
On Wed, 7 Feb 2001, Mike Haberman wrote:
> hey!
>
> I would like to set up the new jyve system such that each
> project (e.g. to lists, faqs, receipe collections, etc) can
> have it's own L&F.
>
> I've come up with 2 solutions:
> 1. give each project it's own template hierarchy. So for exaple,
> the faq templates would be under templates/faq/{nav,layouts, screens}
> and the todo list might be under templates/todo/{nav, layouts, screens}
>
> So, I need to change the following two properties on every request
> depending what project is being accessed:
> services.TurbineTemplateService.template.path
> services.TurbineVelocityService.templates
>
> the default would be
> services.TurbineTemplateService.template.path=/templates/gjyve
> services.TurbineVelocityService.templates=/templates/gjyve
>
> To implement this I will need a way to change the vTemplates
> property in TurbineVelocityService and templateRoot in
> the TurbineTemplateService.
>
> Assuming I add the methods to do the above, At what point can
> can I set the properites before any processing is done? That is
> where do I place the code to do the switching such that it gets
> called first on each request?
>
>
> 2. An easier but less flexible way would be to have a single template
> hierarchy but allow only the main screen Template to change. So you
> are stuck with one layout for all your projects.
>
>
> Any other ideas or suggestions?
>
>
> thanks
>
> mike
>
>
> -------------------------------------------------
> I am Vinz, Vinz Clortho. Keymaster of Gozer,
> Volguus Zildrohar, Lord of the Sebouillia.
> Are you the Gatekeeper?
> -------------------------------------------------
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
