cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conal Tuohy" <con...@paradise.net.nz>
Subject RE: New "module" terminology: WAS: Extending the build system for modules
Date Mon, 19 Aug 2002 21:07:16 GMT
I realise that "blocks" are still vapour-ware, whereas "optional modules"
are at least imminent vapour-ware ;-) but I'm still not entirely clear on
how the relationship between these "optional build modules" and the planned
"blocks" is supposed to develop. Can someone comment on how they see these 2
related concepts developing?

It seemed to me that the CONTENT of each one of these things (i.e. the
components, sitemaps, scripts, docs, etc within a module, or block) would be
essentially the same, i.e. they should have the same granularity. This is
what I meant by "essentially the same", NOT that they use the same
mechanism, because obviously they are different. Is this right?

When pluggable "blocks" are finally developed, will they be able to entirely
replace the mechanism for optional modules? Or will there be some optional
modules which will never become blocks? Is the optional build going to be a
temporary measure before blocks arrive? Or is it a step towards a component
architecture of blocks? i.e. a block = a module + some metadata? This is
what I'm still unclear about.

Cheers

Con


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


Mime
View raw message