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: local policy)
Received-SPF: pass (ags01.agssa.net: 10.0.0.7 is whitelisted)
 receiver=ags01.agssa.net; client-ip=10.0.0.7; helo=[10.0.0.7];
 envelope-from=agallardo@agssa.net;
 x-software=spfmilter 0.97 http://www.acme.com/software/spfmilter/ with
 libspf2-1.0.0;
Message-ID: <443ADEA3.303@agssa.net>
Date: Mon, 10 Apr 2006 16:39:31 -0600
From: Antonio Gallardo <agallardo@agssa.net>
Organization: AG Software, S. A.
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Calculated fields
References: <44393403.8000403@thebug.it> <443A2F61.80200@apache.org>
 <443A51BA.6010109@thebug.it>
In-Reply-To: <443A51BA.6010109@thebug.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Simone Gianni escribi�:
>  
>>   
> -1 for client side. As i wrote, it brings A LOT of complexity, for 
> formatting, double implementation of everything (algorithm must be 
> wrote both for server side and for client side, both for us and for 
> the user), a lot of untidy stuff needed to do it, and it's relatively 
> useless with current great AJAX support. I think it was written in the 
> Jira issue because at that time Ajax was still far.
AFAIK, calculated fields main task is inform the user. In other way, if 
we don't need to inform the webapp user about the "subtotal", "taxes 
amount in a currency" and so on, then we don't need this feature. This 
is why IMHO, let's talk first about the functionality before going into 
implementation details. :-)

Best Regards,

Antonio Gallardo.