Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <402698D4.5030703@messianic.dyndns.org>
Date: Sun, 08 Feb 2004 22:15:16 +0200
From: Johan Kok <jkok@messianic.dyndns.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: [Fwd: Re: Plugin Use cases]
References: <402487BE.6000700@messianic.dyndns.org>
 <1076173462.40251a96f3db6@secure.solidusdesign.com>
 <40266B2A.8050801@apache.org>
In-Reply-To: <40266B2A.8050801@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Ross Gardler wrote:

>
> Yes, so what I'm starting to think is that static stuff should be 
> generated by Forrest and then this is used in a Cocoon Webapp which 
> provides the dynamic stuff. But that gets a little messy. Perhaps I 
> better return to this when we have our developer on board. they will 
> be working full time on this (and other) issues so maybe they'll have 
> more time to think it through. 

I've been considering the same, and vice -versa. The biggest hurdle to 
pass immediately, would be a mix of staticly generated pages and 
dynamically generated pages. The second hurdle to pass would be to keep 
consitency on menus and menu styling between the two. The nice part if 
being able to have sub-sitemaps. If one has that in forrest, one should 
be able to use cocoon from forrest, i.e. let forrest car about the 
static parts adn static menus, and have the dynamic parts called from 
forrest. This is likely to imply that one might have a number of 
different sub-site maps to cover various uses, something like the cocoon 
blocks. Using flow between these would be great and not only there, but 
in a whole load of other areas as well.

>
>
> Ross
>
>
>
>