Return-Path: 
 <cocoon-dev-return-36005-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 91692 invoked by uid 500); 31 Jan 2003 20:37:33 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 91651 invoked from network); 31 Jan 2003 20:37:31 -0000
Subject: default attribute to transformer, reader, SitemapModelComponent,
	...
From: Andrew Timberlake <andrew@timberlake.co.za>
To: cocoon-dev@xml.apache.org
Content-Type: text/plain
Organization: 
Message-Id: <1044045447.12662.84.camel@guru.ddd.co.za>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 31 Jan 2003 22:37:28 +0200
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I am using Cocoon to create an application which uses stylesheets and
resources to present the content to users. The content is managed by a
database and the content to be returned is determined by part of the
request uri.

The application has a default set of stylesheets and resources (images)
to display content initially. I would like to be able to change the
style for different content based on different stylesheets but to use
the default stylesheets when another stylesheet is not available.

I am finding this very difficult to explain so I will try to go into
detail in this email with examples of the syntax I'd like to use. I need
to know if Cocoon is able to do the following in some other way or if
some changes need to be made?

To simplify the application I'll use the following example. 
This example is trivial and is purely to try to explain the concept, my
application currently has many matchers with many transformations in
which only some may be customised.

The application displays the results of database tables. The application
will generate an xml file of the database table in the same manner for
each table.

<table>
    <row>
        <column_name>value</column_name>
    </row>
</table>

The default set of stylesheets will display the table data in an HTML
table with a default set of colours, images etc.

The pipeline would be as follows

<map:match pattern="/db/*/x.html">
    <map:generate type="serverpages" src="content/tables.xsp">
        <map:parameter name="table" value="{1}"/>
    </map:generate>
    <map:transform src="stylesheets/default/table.xsl"/>
    <map:serialize type="html"/>
</map:match>

I would like to create table specific stylesheets when needed, this
would then become

<map:match pattern="/db/*/x.html">
    <map:generate type="serverpages" src="content/tables.xsp">
        <map:parameter name="table" value="{1}"/>
    </map:generate>
    <map:transform src="stylesheets/{1}/table.xsl"/>
    <map:serialize type="html"/>
</map:match>

But, I would like to fall back on the default stylesheet when a specific
stylesheet does not exist. For this the syntax might be as follows

<map:match pattern="/db/*/x.html">
    <map:generate type="serverpages" src="content/tables.xsp">
        <map:parameter name="table" value="{1}"/>
    </map:generate>
    <map:transform src="stylesheets/{1}/table.xsl"
default="stylesheets/default/table.xsl"/>
    <map:serialize type="html"/>
</map:match>

where default="" would be a fall-back stylesheet that is used should the
src file not be available.

I would also need this for resources such as images such as

<map:read src="images/{1}/header.gif"
default="images/default/header.gif" mime-type="image/gif"/>

I can see uses of this in generators as well.

To repeat the question at the beginning, is there a way to do this with
Cocoon as it currently stands or is this something that would need to be
added?
Does anyone else see this as a useful addition to Cocoon?
Which would be the best way to get this functionality into Cocoon?
	is the default attribute right or should it be something else?
I would be more than prepared to implement such functionality if others
would like it as well.

-- 
Andrew Timberlake <andrew@timberlake.co.za>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org