cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [Summary] [Vote] Moving XSP into its own block
Date Fri, 12 Mar 2004 21:29:13 GMT
Unico Hommes wrote:

> Carsten Ziegeler wrote:
> 
>> Torsten Curdt wrote:
>>  
>>
>>> Carsten Ziegeler wrote:
>>>   
>>>
>>>> Unico Hommes wrote:
>>>>
>>>>
>>>>     
>>>>
>>>>> I tend to think the dependency is from session-fw on xsp, not the 
>>>>> other way around. Unless this becomes really difficult to       
>>>
>>> accomplish   
>>>
>>>>> I'd prefer keeping it the way it is now. I will do some       
>>>
>>> research as to   
>>>
>>>>> what would be involved to change the build system to       
>>>
>>> accomodate this.
>>>   
>>>
>>>> But this then makes removing xsp more difficult :) I really think
>>>> we should keep all xsp related stuff in one place. This makes the
>>>> whole thing easier to handle but also is more transparent for
>>>> users. They have one single place to look for logicsheets.
>>>>     
>>>
>>> Hm... I think it's hard to classify...
>>>
>>> Do you also want to move the e.g. ESQL logicsheet into
>>> the XSP block? IMO that would not be a good idea.
>>>   
>>
>>
>> True...hmm...ok, then whoever does it should decide :)
>>
>>  
>>
> I see your point of placing the burden of dependencies with xsp though. 
> We could take that as a guideline whenever there isn't a clear reason to 
> do otherwise.

I'm starting to realize that XSP is an aspect not a block... maybe we 
should have two different concepts?

-- 
Stefano.


Mime
View raw message