cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Haul <h...@dvs1.informatik.tu-darmstadt.de>
Subject Re: Extending the build system for modules
Date Fri, 16 Aug 2002 13:41:39 GMT
On 16.Aug.2002 -- 03:22 PM, Nicola Ken Barozzi wrote:
> 
> Christian Haul wrote:
> >On 14.Aug.2002 -- 04:28 PM, Carsten Ziegeler wrote:
> >
> >>Hi Team,
> >>
> >>we recently had our thread about Cocoon organization etc. and
> >>it's now time to recapitulate the results.
> >>
> >>One main result is to split the core from optional things that 
> >>we from now on call modules (and not blocks!).
> >
> >
> >Objection! We have "modules" already. This is going to cause
> >confusion.
> 
> And CVS modules? ;-)
> 
> >After looking in my Oxford Thesaurus, the following alternatives might
> >be suitable:
> >
> >   portion
> >   element
> >   ingredient
> >   unit
> >   bit
> >   fragment
> >   piece
> >   item
> >   particle
> >
> >I like "particle" and "ingredient" best :-)   
> >
> >"Oh, you need to include the XMLForm ingredient for that..."
> 
> I think that they simply are Cocoon "component"s, no?

Although this is a good term, I fear the close relationship with
Avalon (-> Avalon Components) will cause confusion as well.

	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


Mime
View raw message