Turbine does seem somewhat similar to Tapestry. We seem to have taken
simlar approaches to some problems, but not to others. Tapestry is
specifically about avoiding scripting in the first place. Tapestry takes
care of pulling data from "the application" and putting it onto the HTML
page. It manages server side client data. It doesn't have a fixed concept
of a Module, Navigation, etc. component ... there are just components nested
together in any way appropriate to the application.
It's killing me that a network problem at Primix is keeping anyone from
actually seeing Tapestry this weekend.
Re: Tapestry -- Possible contribution to the Java Apache project
by <[EMAIL PROTECTED]>
Subject: Re: Tapestry -- Possible contribution to the Java Apache
project
From: <[EMAIL PROTECTED]>
Date: Fri, 14 Apr 2000 15:09:52 -0700 (PDT)
Sounds exactly like Turbine but only 2 years later...
<http://java.apache.org/turbine/>
;-)
Good luck with your code.
-jon
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
