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 === Clicking "New Publication" button from the AdminFunctionModule asks which Publication to use as a Template (defaulting to current Publication), then shows checklist of all installed Modules (from chosen Template, and Global Modules not in the Template). The new Publication is created and usable. The developer may change the XSL in the Live and Homepage Modules, which can be done using the XML Module. With this, the Sample Publication becomes the Template with all Lenya-supplied Modules. It will be fun when a Publication can handle: /Homepage/XHTML[WikiWelcomePage]/Wiki/Blog and automatically creates WebsiteMaps and RSSFeeds. I am uncertain how the Editors should be handled. Do you need to choose the editor to edit XHTML? Or should there be Types "XHTMLKupu" and "XHTMLBXE"? Does the Authoring Module retrieve the Authoring Page from the TypeModule? Or does it retrieve the Document and pass it to an EditorModule? Or both, so XHTML can be a special case where you are asked which editor to use if more than one is configured for this Publication? solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
