Return-Path: 
 <dev-return-47134-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 89373 invoked from network); 31 Aug 2003 11:41:25 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 31 Aug 2003 11:41:25 -0000
Received: (qmail 67631 invoked by uid 500); 31 Aug 2003 11:41:15 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 67514 invoked by uid 500); 31 Aug 2003 11:41:14 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 67477 invoked from network); 31 Aug 2003 11:41:13 -0000
Received: from unknown (HELO mwinf0402.wanadoo.fr) (193.252.22.27)
  by daedalus.apache.org with SMTP; 31 Aug 2003 11:41:13 -0000
Received: from anyware-tech.com (AToulouse-206-1-3-142.w81-50.abo.wanadoo.fr
 [81.50.192.142])
	by mwinf0402.wanadoo.fr (SMTP Server) with ESMTP id 02CCC800085
	for <dev@cocoon.apache.org>; Sun, 31 Aug 2003 13:41:09 +0200 (CEST)
Message-ID: <3F51DED4.1060804@anyware-tech.com>
Date: Sun, 31 Aug 2003 13:41:08 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: fr, en, en-us
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: cvs commit:
 cocoon-2.1/src/blocks/woody/samples/xsl/html	woody-default.xsl
References: <20030817210342.12815.qmail@minotaur.apache.org>
 <1062149729.14367.31.camel@yum.ot> <3F51B424.1010704@anyware-tech.com>
 <3F51C8E8.8070403@outerthought.org>
In-Reply-To: <3F51C8E8.8070403@outerthought.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Steven Noels wrote:

> Sylvain Wallez wrote:
>
>> Example :
>> <wt:widget id="foo">
>>  <wi:styling type="textarea" rows="10"/>
>> </wt:widget>
>>
>> The "type" attribute defines the "style type" and all other 
>> attributes are dependent on this type (and here, copied as is).
>>
>> What do you think ?
>
>
> Including the style element directly rather than referring to it with 
> a type attribute leaves for more future expansion room and won't mess 
> up namespaces if you include direct output elements in the 
> <wi:styling/> element, IMHO.


I think I wasn't clear : this applies well to _flat_ styling 
configurations (i.e. a simple list of name/value pairs) as it doesn't 
require an additional nested element (reduced verbosity). But this does 
not prevent the use of nested elements in wi:styling when needed 
(although I haven't encountered this need up to now).

Furthermore, use of attributes ensures uniqueness of styling type, which 
is not guaranteed with nested elements.

E.g. what happens if we write :
<wt:widget id="foo">
  <wi:styling>
    <textarea rows="10"/>
    <password size="20"/>
  </wi:styling>
</wt:widget>

Will this widget be rendered as a textarea or as a password ? With 
"textarea" or "password" being defined by the unique "type" attribute, 
this problem cannot happen.

Or do we want <wi:styling> to be able to hold different styling 
directives and let the layout stylesheet decide which one is best ? 
Mmmh... too much magic...

Sylvain

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