cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: [RT] Mini-Cocoon
Date Sat, 15 Apr 2006 12:00:54 GMT
Bertrand Delacretaz skrev:
> Hi Don,
> 
> Le 14 avr. 06 à 21:13, Don Brown a écrit :
> 
>> ... - We only need transformers and serializers, the framework would 
>> handle the generation (implicitly a SAX parser generator would be used 
>> to process the response's outputstream)
>>  - Ideally no additional dependencies
>>  - The pipeline impl should be small, and focused
>>  - Very little to no additional configuration for the user.  A set of 
>> transformers and serializers would be defined somewhere, and stacks, 
>> or statically defined pipelines.  No selectors, matchers, or other 
>> sitemap capabilies would be needed. ..
> 
> What you suggest echoes our discussions from a last December [1], and I 
> think there's definite interest in our community to see Cocoon delivered 
> in smaller independent packages. At least at the "talking about it" 
> level...but let's hope your message prompts some people to stand up.
> 
> Maybe some of the people working on 2.2 can comment about this? How 
> could the new structure of 2.2 help using our sitemap components outside 
> of Cocoon?
> 
> Personally I'd love to help, but to be realistic I won't be able to 
> commit serious time to such a project in the next few weeks. Except 
> maybe mentoring or co-mentoring a Summer Of Code project to experiment 
> with refactoring some of our sitemap components to be usable in a 
> lighter environment.
> 
> -Bertrand
> 
> [1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113380354129554&w=2

Splitting Cocoon core is on my todo-list, I wrote something about it a 
while ago: 
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113682736011081&w=2.

An important question is of course what blocks to split core into and 
what the contracts should be for these blocks.

/Daniel

Mime
View raw message