Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Subject: Re: [cforms] refactoring questions (was Re: cvs
	commit:	cocoon-2.1/src/blocks/forms/java/org/apache/cocoon/forms/formmodel
	Struct.java Messages.java Repeater.java
	MultiValueField.java	AbstractContainerWidget.java Output.java Upload.java
	Action.java Form.java	ContainerDelegate.java AbstractWidget.java Field.java
	Union.java	BooleanField.java Widget.java)
From: Bruno Dumon <bruno@outerthought.org>
To: dev@cocoon.apache.org
In-Reply-To: <408CBF65.3040901@apache.org>
References: <20040420221928.11898.qmail@minotaur.apache.org>
	 <4085A446.5050103@outerthought.org>  <408BB8D1.4020409@apache.org>
	 <1082903053.4332.212.camel@yum.ot>  <408CBF65.3040901@apache.org>
Content-Type: text/plain
Organization: Outerthought
Message-Id: <1082969987.2642.12.camel@23.13 	yum.ot 	yum
Mime-Version: 1.0
Date: Mon, 26 Apr 2004 10:59:47 +0200
Content-Transfer-Encoding: 7bit

On Mon, 2004-04-26 at 09:51, Sylvain Wallez wrote:
> Bruno Dumon wrote:
> 
> >On Sun, 2004-04-25 at 15:10, Sylvain Wallez wrote:

> >>Note that I'd like also that <wi:styling> could be written in the definition also, as defining the styling in the widget definition can be a productivity boost with widget repositories!
> >>    
> >>
> >
> >Should be trivial to store this in the form definition.
> >  
> >
> 
> Yep. But this brings some namespace-related questions: "styling" is 
> obviously in the instance namespace ("fi"), but if we introduce some 
> "fi:" in the definition, what about "label"? The CForms machinery does 
> nothing with it except copying it in the template output, so we may 
> consider moving it also to the "fi" namespace.

+1

label has been put in the definition only because it was thought to be
convenient.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org