Michael Wechner wrote: [...]
so, why don't we call it components or modules?
-1 to components, because this term is already used for another concept (component oriented development), especially in the Cocoon world. Modules is fine with me. I chose "publets" because we used this term for quite a long time. What I implemented is quite along the lines of the publets proposal (http://wiki.apache.org/lenya/ProposalPublets)
I think it's very important that we get the naming/terminology right, otherwise we will have to do a lot of explaining.
Whatever term you choose, you'll have to explain what it is. But I agree, terminology is important.
It seems to me we should differentiate very clearly between "actual" publets, modules and core.
IIUC that would mean to add another concept (modules). What would be the difference between a module and a publet? Would it be possible to use the Cocoon blocks concept to implement modules?
As said before I don't think there should be something like a JCR publet.
I'm strongly against mixing all functionality in a large "core bucket". If we use another concept for modularization, fine with me.
And I think we should this now. Because once released it's hard to rename stuff. So I would suggest that we discuss/explain the naming.
OK. Do you want to make a proposal? -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
