forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@apache.org>
Subject Re: Quick evaluation of Cocoon Portal Engine as forrest:views implementation
Date Mon, 01 Aug 2005 12:54:42 GMT
This mail was a reply from Nicola in another thread to the mail from 
Johanes that I moved here. It is unedited here, I will reply in a moment.

Nicola Ken Barozzi wrote:
 > Johannes Schaefer wrote:
 > ...
 >
 >>* The portal uses a configuration hierarchy:
 >>  1. define coplets
 >>  2. define instances
 >>     (may use coplets multiple times)
 >>  3. define the layout
 >
 >
 > How does it define layout?
 >
 >
 > One more thing that comes to mind... Cocoon portal-coplets seem like a
 > perfect way to define what /content/ is to be in a page.
 >
 > It seems to me that it starts lacking when I need to insert pieces of
 > functionality, as they may have to touch the whole page and filter it.
 >
 > IOW a portal is an excellent - user configurable - <xinclude> mechanism,
 > but views are not only about that.
 >
 > I mean, views are basically a page-templating system. Can a portal be
 > defined as a page-templating system?
 >
 > Still many questions and no good answer...
 >



Mime
View raw message