Andreas Hartmann wrote:
I wouldn't pay too much attention to the question "what is a publet",
but I think this is a very important question. From my point of view
publets had the goal to provide the necessary resource types and usecases
for a specific part of a publication, e.g. a blog publet, just as you
actually describe it above.
but rather on the possibilites that are provided by the publet
concept:
- publet menu items are inserted automatically if a publet is declared
by a publication, so you can use it for functionality which is
used by multiple publications
- you can see a publet as a resource package which is used by
multiple publications
- ... (no idea what else will be possible)
or is it rather like a component (e.g. sitetree, etc.)?
Yes.
so, why don't we call it components or modules?
I think it's very important that we get the naming/terminology right,
otherwise we will have to do a lot of explaining.
It seems to me we should differentiate very clearly between "actual"
publets, modules and core. As said before I don't think there should be
something like a JCR
publet. 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.
Michi
How does the inclusion of a publet work on compile-level?
It's exactly the same as for publications.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
