[EMAIL PROTECTED] wrote:
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.
A Usecase is currently defined as an XMAP that can be called using a
complicated URL.
[OFF-TOPIC: My recommendation is to specify the XMAP in the path
rather than the querystring.]
A Publet is a Usecase (or several) plus whatever else is required to
make it work?
Basically yes, whereas I'd see it the other way round:
A typical publet offers resource types and usecases which operate on them.
[OFF-TOPIC: My opinion is only one XMAP should be in the pub directory
as the hook for the new function. Additional XMAPs should be in the
Publet's directory with all other required files. The top-level XMAP
can specify the path structure to keep it clean:
/myXMAP/subXMAP/AdditionalInformation/pathToDocument]
I have a Usecase which requires other files (XSLT, XSP, Flow) which I
keep in one directory (to keep them organized as part of this
function, rather than spread them among the many standard directories.
Separating by filetypes just adds confusion.) Should call I this
functionality a "Publet"? Or can I keep calling it a "Usecase" even
though the XMAP is not sufficient by itself?
IMO that's up to you. If you see it as a standalone reusable unit,
you could implement it as a publet.
-- The "Search" Example --
It would be good if the various files for Search were in a single
directory. My revision put files into 7 directories, and the index is
built in #8.
1. /tools/bin (ant files: batch/shell and log4j config)
2. build\lenya\webapp\WEB-INF\classes\org\apache\lenya\lucene\index (bug fix)
3. {pub} (for the Usecase XMAP)
4. {pub}/config/search
5. {pub}/lenya/content/search
6. {pub}/lenya/xslt/navigation
7. {pub}/lenya/xslt/search
8. {pub}\work\search\lucene\index\live\index
Have you looked at the trunk (1.4)?
All search related files are in a single directory.
The files in 4, 5, and 7 include almost all publication configuration,
and should be in one directory. #8 can be placed under that directory
so if Search is removed from the Publication, so is the working
directory. #3 is the hook from the publication. #7 is part of the
navigation system, and requires manual deletion if the rest of the
function is uninstalled.
Should this collection of files be called the "Search Publet" or the
"Search Usecase"?
IMO that's a publet.
---
It sounds like calling something a "Publet" means changing from the
current filetype directory structure to functional organization of
files.
Yes - modularization is one purpose of publets.
Does that really require a new term?
A new term is maybe not required, but it's fun, isn't it? :)
BTW - no idea who coined it, but it's quite old.
My opinion is the new term may keep people happy while the
reorganization happens, but it will haunt you for a long time. It is
easier to call XMAPs/Usecases simply XMAPs, and call functions
"Usecases", which is close to how "usecase" is defined outside the
Lenya community. This would be easier if the "usecase-" was removed
from the names of the XMAP files.
IMO a publet is different from an XMap and is also different from
a usecase. It's rather a module which can contain a couple of both
of them.
[OFF-TOPIC: I dislike referring to XMAP files as "Sitemaps" because
"sitemap" has a specific definition for websites, and Lenya creates
websites. I wrote an XMAP as part of a Usecase to display the
document organization ("map") of the website. Documenting that
without using the word "sitemap" was difficult.]
OK, but "sitemap" is an established term in the Cocoon world.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
