Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <44D06783.7050409@apache.org>
Date: Wed, 02 Aug 2006 10:51:15 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [CForms] Streaming out widget attributes?
References: <44CF760C.1010408@apache.org> <44CF781C.3000506@apache.org>
 <44CF92CD.1020004@apache.org> <44CFC595.6050605@apache.org>
 <44D047A2.2000408@apache.org> <44D05FF0.9000903@apache.org>
In-Reply-To: <44D05FF0.9000903@apache.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Sylvain Wallez wrote:
> 
> Yeah, but the point is about the "somewhere". Each element in a Cocoon 
> pipeline is supposed to address a particular concern.
> 
> Now over time, reasons emerge for everything to be useful everywhere, 
> and we end up with a giant mix, where having different stages in a 
> pipeline no more really make sense, and where each stage produces as 
> much information as possible for the next one, for the occasional case 
> where it may be useful, thus impacting the general performance just to 
> handle these edge cases.
> 
Ok, in general you're right; but I'm wondering why for example we added
a special handling for suggestion lists which is rarely needed and seem
to refuse to add a more general approach which helps others as well.
Streaming out the attributes of the field definition should in no way
change the performance as the attributes are empty in most cases anyway.

> 
> Well, that looks like business logic to me, and can be handled by 
> on-change events with Ajax.
I don't want to use ajax for this; i don't need a server request; I can
generate javascript which completly runs in the browser - which is much
faster and user friendly.

Carstem
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/