Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of peter.neu@gmx.net designates
 213.165.64.21 as permitted sender)
From: "Peter Neu" <peter.neu@gmx.net>
To: <dev@cocoon.apache.org>
Subject: Future Use of Form.js Version 2/Best Practice Web Apps
Date: Mon, 23 Jan 2006 08:40:12 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcYf8D5GuRReqzZITXWFvu2eamo87A==
Message-Id: <20060123074021.3DEEB10FB00F@asf.osuosl.org>

Hello,

I have a two-part question. I already placed it in the dev mailinglist. But
I realize that this was maybe not the place to post them. 

Question I 
Reading through the cocoon documentation and browsing for examples I did not
find much reference on how to build the classic web app. Meaning: how to
divide all content header, footer, etc into serate parts. I worked with
Tiles beforehand so I really missing this feature badly. What are you
suggestions to do this? Is an approach like in the example advisable?  

http://www.cocooncenter.org/articles/navigation.html

How about doing some kind of best practice example? I know brick cms but it
does not really deal with this, does it? 


Question II
I like the concept of event handlers you introduced in version 2 of the
Form.js. I realized though that the examples working with the version 1 of
Form.js are not working with version 2 and vice versa. So is version 2 meant
to be used for good or is it a toy which will disappear in future releases? 


Cheers,
Pete