Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3D4830A4.4060802@apache.org>
Date: Wed, 31 Jul 2002 14:47:00 -0400
From: "Andrew C. Oliver" <acoliver@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.0) Gecko/20020530
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [Proposal] Cocoon Organization
References: <006601c238bd$6109ecd0$df74558b@vgritsenkopc>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>
>
>Yes, you may use only one or two. But think about it: right now there is
>no one, commonly shared syntax for these two (esql and transformer), and
>they have no common roots, they are not well integrated.
>
>If you to put esql and sql transformer into different subprojects, then
>situation will just get worse. They must be in the same subproject, and
>should be unified and integrated as much as possible, to reduce
>repetitive code and make maintainance / feature additions easy.
>
>
>IIRC, somebody (Andrew?) was about to integrate these two.
>  
>
Yes I plan to.  Its on the task list.

>Vadim
>
>
>
>  
>
>>So, I reckon it boils down to someone with a good overview to suggest
>>the grouping scheme and prepare a layout. I would hope that everyone
>>would move the stuff they feel responsible for to the appropriate
>>location.
>>
>>	Chris.
>>--
>>C h r i s t i a n       H a u l
>>haul@informatik.tu-darmstadt.de
>>    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08
>>    
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>  
>


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