Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 61140 invoked by uid 500); 24 Apr 2003 21:48:20 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 61043 invoked from network); 24 Apr 2003 21:48:19 -0000 Received: from unknown (HELO host.leverageweb.com) (64.91.232.157) by daedalus.apache.org with SMTP; 24 Apr 2003 21:48:19 -0000 Received: from 66-44-56-95.s95.tnt2.lnhva.md.dialup.rcn.com ([66.44.56.95] helo=geoff2k) by host.leverageweb.com with asmtp (Exim 3.36 #1) id 198oWj-0003cs-00 for cocoon-dev@xml.apache.org; Thu, 24 Apr 2003 17:45:10 -0400 From: "Geoff Howard" To: Subject: RE: Woody Date: Thu, 24 Apr 2003 18:05:06 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 In-Reply-To: <1051208637.17437.847.camel@yum.ot> Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.leverageweb.com X-AntiAbuse: Original Domain - xml.apache.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - leverageweb.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Bruno Dumon [mailto:bruno@outerthought.org] > > Hmmm... if you happen to develop complex forms, users (in my > experience) > > will eat you alive if you don't provide them with fast feedback and > > "reactive" forms :( > > Depends a lot on the use-case of course. I guess these are mostly on > intranets? If anyone knows of a good public example, I'd be interested > to see it. > > Also, when I'm saying it's not a high priority for me, it means that I > probably won't be doing any coding on it in the short-term, but I'll > keep it in mind when making design decissions. > Use-case: you have a complex form, and a user on a slow dial-up who doesn't want to have to round trip the page just to find out that they mistyped their email address. Even worse if it was a multi-part file upload of a 1meg document! Geoff