OT in this thread, but i wanted to say i very much like the
categorization of modules by functionality that solprovider suggests
below. i found it very confusing at the beginning how so very different
things as document type handlers and sitetree could be both called
"modules". so votes++ to include this overview in a prominent place in
the 1.4 modules docs.
[EMAIL PROTECTED] wrote:
On 2/9/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
Michael Wechner wrote:
Andreas Hartmann wrote:
Michael Wechner wrote:
The concept is as follows:
IMO it should be
- module
- containing resource types
- containing usecases
- containing static resources, ...
- using other modules
so, the "blog publication" could be a module itself (but without content)
Yes, IMO that would be nice. I once tried to implement this,
but it is apparently harder than it looks :)
publication
- having content
- using modules
- containing resource types
- containing usecases
- containing static resources, ...
the blog publication would basically just consist out of the blog
module, right?
It will be much easier once all functionality is moved to Modules. A
Publication just has a config file with the list of Modules and
location of the Content Repository. Everything else is handled by the
Modules.
Here is my current list of Modules:
== AdministrationModules (Affects entire Publication)
Users
Groups
IPRanges
AdminFunctions (ServerStatus, DeleteTrash)
Sitetree (for maintaining Resource relations in hierarchies)
Registration (handles Register, Maintain User Infomation, Login, and Logout).
== FunctionModules (backend processes, maybe categorized as Admin?)
Notification
Newsletter
== NavigationModules (Uses multiple Resources to return Document)
Search
- Lucene
- (other Search)
WebsiteMap
Menu
TabbedMenu
(other menus)
Breadcrumb
RSS (directly accessible by visitors)
== TypeModules (Uses single Resources to return Document. Most
configure which editor to use.)
XHTML (or XHTMLKupu, XHTMLBXE. See below.)
Blog
Wiki
XML (for XMAP, XSP)
CSS
ProductSample (for use in creating Fields-based Documents.)
Asset (Returns binary file or Document with META information)
- Image (Like Asset, but adds Height and Width)
Section (for retrieving portions of a Document)
== PageModules (return HTML Pages)
Live
Homepage
Authoring
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
