You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Apache Wiki <wi...@apache.org> on 2005/05/16 14:05:54 UTC
[Lenya Wiki] Trivial Update of "ProposalContentModel" by WolfgangKaltz
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by WolfgangKaltz:
http://wiki.apache.org/lenya/ProposalContentModel
The comment on the change is:
restored attachments; forced their display
------------------------------------------------------------------------------
attachment:contentModel.jpg
+
Comments:
* a document can consist of a list of several content items. That is, a document is an aggregation of 1 or more content items. The document itself thus no longer directly refers to content; it contains references to content parts.
* a {{{ContentItem}}} instance can refer to several other {{{ContentItem}}} instances, with several implications:
@@ -50, +51 @@
attachment:plugins.jpg
+
Comments:
* this model thus far only supports finding an appropriate plugin dynamically, for a content item. How exactly the plugin then interoperates with Lenya is still open. My guess: depending on the purpose of the plugin (e.g. "for editing"), a more precise contract can be defined (e.g. such a plugin must be able to receive a piece of content, and have a callback registered for saving it)
* what does a plugin implementation consist of ? Presumably each plugin will have a subdirectory, with sitemap, xsls, and configuration files. Depending on the plugin, it may also have Java classes etc. For individual XML editors, ideally no Java classes are required, as the {{{XMLEditorManagerPlugin}}} would be the service to access information about them.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org