Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <43ED1689.2090204@apache.org>
Date: Fri, 10 Feb 2006 23:41:13 +0100
From: Sylvain Wallez <sylvain@apache.org>
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Fine Tuning Ajax Handling in CForms
References: <c84c391f0602101119g7ce1b9dei6b4a6112e8f6efa8@mail.gmail.com>
In-Reply-To: <c84c391f0602101119g7ce1b9dei6b4a6112e8f6efa8@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Quoin Developers wrote:
> Currently, it's all or nothing when it comes to using AJAX on a form.
> With this enhancement, form widgets can be marked with <fi:styling
> ajax='false' />, and they will trigger a non-ajax form submission.
>
> I believe it is useful to give the developer control over which
> widgets use AJAX and which do not.
>   

Why do you need such flexibility?

> Note that the patch files also include a fix to a separate AJAX issue.
>
> forms_onsubmitHandlers = null
>
> Causes problems when in AJAX mode - submit handlers are only called
> the first time an ajax submit is called. Thereafter, the array of
> handlers is null, and none are called.
>   

Yeah, that's a problem. But we cannot keep it either, as some of the 
handlers are registered by widgets that are replaced by the update.

The move to Dojo which I'm currently working on should solve this issue.

Sylvain

-- 
Sylvain Wallez                        Anyware Technologies
http://bluxte.net                     http://www.anyware-tech.com
Apache Software Foundation Member     Research & Technology Director