[EMAIL PROTECTED] wrote:
On 2/22/06, Michael Wechner <[EMAIL PROTECTED]> wrote:
I think each module should have a descriptor (similar to publication.xml
resp. publication.xconf) where the module is being described and also
"addressed"
with
- name (e.g. atom-entry)
- namespace (e.g. http://lenya.apache.org/2006/1.0)
- version (e.g. 1.0)
in order to avoid conflicts.
I have no objections to a descriptor file "module.xml", but will it be
mandatory?
yes, I think it should be required
The primary use would be to add descriptions for the
"Choose Modules for Publication" administration screen. It should be
mandatory for all modules included with Lenya, but any use of it
should survive the file not existing. I quickly create Modules for
testing features, and requiring this file would slow development
without adding any value.
well, having a readable name/description of the module and the Lenya
version cannot
be that much effort ;-)
Michi
publication.xconf should have the list of Modules used in this
Publication. Most standard Modules will not need a directory in the
Publication unless they are being customized. Almost everybody will
customize "page2xhtml.xsl" in the "live" Module, but very few will
customize the "authoring" Module, and it should be able to be included
or excluded for each Publication.
The important information is:
- name (which must match the directory name)
- (Boolean) allowed in URLs (to distinguish between Modules accessible
by visitors and internal Modules used by other Modules.)
- (optional) TemplateID if inheriting is not from the Template
specified for the Publication.
<module name="live" external="true" template="default">
The "external" Boolean flag is "true" for "live", "authoring",
"search", and other frontend Modules, but should be "false" for
"breadcrumbs", "menu", "tabs", "lucene" and other backend Modules that
should not be accessible by visitors. This flag could default to a
value from "module.xml". (We may need a Publication-level
"ignoreExternal" Boolean so all Modules are accessible on development
servers. It is very useful to check the XML output from each Module
during development.)
If external is "true", then:
http://server/pub/moduleID
http://server/pub/...?lenya.usecase=moduleID
http://server/pub/...?lenya.module=moduleID
will work. If it is "false", they all return the "Sorry" page.
Your other post was about adding a namespace to "publication.xconf".
I prefer working without namespaces when possible, but if others think
it useful, then it should wait until the elements are stable.
solprovider
---------------------------------------------------------------------
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]
