on 2/7/01 10:21 AM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
> 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.
This has been discussed quite a bit on this list in the past (I think before
you came here jvz)...
I would be strongly +1 for seeing this happen. Just note that it needs to be
done in such a way that it is backwards compatible though.
thanks,
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
