Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3EA0520C.3090506@dotech.com>
Date: Fri, 18 Apr 2003 15:29:16 -0400
From: David Kavanagh <dak@dotech.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.2) Gecko/20030208 Netscape/7.02
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: GroupingTransformer
References: <3EA03B41.4040706@dotech.com> <3EA045BC.1070600@verizon.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Yes, I can see how FilterTransformer could be modified to return the 
entire dataset like the GroupingTransformer. I've seen other examples of 
similar components, so it seems like there may be room for two separate, 
but similar transformers that each do their respective jobs well.

I just looked at the code for the FilterTransformer and it seems a 
little easier to follow than mine. I think it would be easy to modify to 
output all pages. I don't really have the time to do that now, but maybe 
someone does.

David

Vadim Gritsenko wrote:

> David Kavanagh wrote:
>
>> I've been on the cocoon-user list for a while, but had this 
>> transformer I wanted to submit.
>>
>> I'm not sure if anyone has written something like the before, but 
>> here goes...
>>
>> This tranformer will group sets of elements in an XML stream. 
>
>
>
> Your transformer reminds me of FilterTransformer and Paginator 
> transformer. They also divide incoming stream into blocks/pages, but 
> output only one block/page at a time. I think FilterTransformer can be 
> extended to include capabilities of your GroupingTransformer 
> transformer, this way we will have just one transformer instead of two 
> somewhat similar transformers.
>
> Vadim
>