Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <4151DAAE.1040408@apache.org>
Date: Wed, 22 Sep 2004 22:03:58 +0200
From: Sylvain Wallez <sylvain@apache.org>
Organization: Anyware Technologies
User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Widget states: let's do it (was Re: CForms making widgets
 invisible)
References: <41514D5B.20709@juwimm.com> <415186AA.50601@apache.org>
 <415195F7.3010805@reverycodes.com> <4151A003.1080004@apache.org>
 <4151CA86.8040400@reverycodes.com>
In-Reply-To: <4151CA86.8040400@reverycodes.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Vadim Gritsenko wrote:

> Sylvain Wallez wrote:
>
>> And now, with "enabled"/"disabled"/"invisible"?
>
>
> I guess I'm Ok with that; can you also comment how it relates to:
>   http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108981424626685
>
>
> Your proposal seems to differ a bit by mixing presentation and 
> input/output concern - I guess there is a reason for this too :)


My proposal is only about what data comes in a out from the form model. 
The state certainly impacts how it is displayed, but this can be further 
refined in the view. For example Tim's "inline" and "disabled" proposal 
are two possible stylings of a disabled widget, in the same manner than 
an enabled widget that can have the "hidden" styling.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }