portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject Re: [M2 build design] Refactoring
Date Tue, 04 Sep 2007 22:58:34 GMT

On Aug 28, 2007, at 7:17 AM, Weaver, Scott wrote:

> I think a side by side would be the way to go.  The reason I yanked
> portlet-based layouts is that, at the time, they were some clunky and
> auto-deployment wasn't working consistently, at least for me.  I went
> with the simplest approach using just Velocity running is a valve and
> directly interacting with the aggregation engine.  This eliminates the
> need to for theme designers to pack each, new layout/theme as a  
> portlet.
> There is also no need for a specific, deployment mechanism for  
> themes as
> they just sit in a /theme directory right off the root of the
> application.  This approach also allows me to easily proxy static
> content through Apache for performance's sake.
> The theme system provides for localized and device/content-type  
> specific
> (which I am pretty sure was in the previous layout mechanism) themes.
> /themes/html/page.html
> /themes/html/de/page.html
> /themes/xml/page.xml
> It also supports fall back.

Yes the previous approach supported language and media type fallback  
for templates.
In retrospect, although this feature is useful, it should be optional  
as its often not used at all

> /themes/html/en/ <--page.html not found here so move up one level.
> /themes/html/page.html <-- found here, so use it.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message