[Lenya Wiki] Update of "Lenya 3.0" by FlorentAndre
Apache Wiki <[email protected]>
| Newsgroups | gmane.comp.cms.lenya.devel |
|---|---|
| Message-ID | <[email protected]> |
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification. The "Lenya 3.0" page has been changed by FlorentAndre. http://wiki.apache.org/lenya/Lenya%203.0?action=diff&rev1=3&rev2=4 -------------------------------------------------- - This document is a first draft for design the future Lenya major version. + This document is a first draft for design the future Lenya major version. - Useful reading and information have to be picked up from this documents : + Useful reading and information have to be picked up from this documents : + - * [[RoadmapLenya3.0]](Need to be reviewed and copy into another section, not really a roadmap IMO) + * [[RoadmapLenya3.0]](Need to be reviewed and copy into another section, not really a roadmap IMO) - * [[WishlistLenya2.0]] + * [[WishlistLenya2.0]] Here comes some headings that have to be filled down. Headings and content are proposals, so don't hesitate to modify, suppress, etc... = Firsts requirements = + * Automatic content migration from old version to the new one + * LenyaDocTransformer can be a begin of a solution with his capability to create documents from xml with api usage. - * Automatic content migration from old version to the new one - * LenyaDocTransformer can be a begin of a solution with his capability to create documents from xml with api usage. + = Uses-cases = + * write here you how-to use idea, like if you are a simple user - = uses-cases = + * Use Case 1 : Chain modules + * be able to easily (via user interface) to chain modules in order to create a new process in my publication. + * For example, I have in my module stack : + * A - upload module (build interface for the end user) + * B - Write to file system module + * C - To html parser (ie Tika) + * D - Lenya document creator module + * so I can define via administrative interface : + * process I) A --> B + * process II) A --> C --> D - * write here you how-to use idea, like if you are a simple user + * Use Case 2 : Forms by clic ² * Be able to define forms with clic and decide what I want to do with this after validation (write in a resource, write on FS, put in database, send by mail,...) + = Features needed = + == Needed == + * wish list of all features you want to see + * will be organize / topicazed soon. - * Use Case 1 : Chain modules - * be able to easily (via user interface) to chain modules in order to create a new process in my publication. - * For example, I have in my module stack : - * A - upload module (build interface for the end user) - * B - Write to file system module - * C - To html parser (ie Tika) - * D - Lenya document creator module - * so I can define via administrative interface : - * process I) A --> B - * process II) A --> C --> D + * all is module, core is restrict to his more simple expression - * Use Case 2 : Forms by clic - ² * Be able to define forms with clic and decide what I want to do with this after validation (write in a resource, write on FS, put in database, send by mail,...) + * easy way to integrate webservices + * GUI module configuration + * more "2.0": + * user can create his account + * possible to comment each document + * hook feature : each module can define pre or post hook for predefined function, with this, module don't be intrusive into existing process, easily add features on it - = features needed = - * wish list of all features you want to see - * will be organize / topicazed soon. - * all is module, core is restrict to his more simple expression + * user interface + * workflow more closed to the article + * suppress "site" tab and put all functionnalities into "authoring" mode + * molecular sharing system : + * each user can define one or more "friends group" and share with it read, write, comment access. 4 bases levels : individual, personnal groups, site groups, world - * easy way to integrate webservices - * GUI module configuration - * more "2.0": - * user can create his account - * possible to comment each document - * hook feature : each module can define pre or post hook for predefined function, with this, module don't be intrusive into existing process, easily add features on it + * easy way to create forms + * forums + * blog + * synchronisation between different instances (via svn for example) + * possibility to edit site when not connected - * user interface - * workflow more closed to the article - * suppress "site" tab and put all functionnalities into "authoring" mode + * links with mail-box + * import Ooo 3.0 + * be able to edit imported Ooo 3.0 + * presentation / slide module - * molecular sharing system : - * each user can define one or more "friends group" and share with it read, write, comment access. 4 bases levels : individual, personnal groups, site groups, world + * metaData Navigator : be able to navigate trow documents by date, autor, key-words, ... + * fine grained workflow + * be able to define particular workflow for a path in the site structure (so a part of the site can become wiki, and the other verified area) - * easy way to create forms - * forums - * blog + * Unit-testing on sitemap's results. - * synchronisation between different instances (via svn for example) - * possibility to edit site when not connected + == whised == + * implementation of webcalendar calendar format propose calendar service - * links with mail-box - * import Ooo 3.0 - * be able to edit imported Ooo 3.0 - - * presentation / slide module - - * metaData Navigator : be able to navigate trow documents by date, autor, key-words, ... - - * fine grained workflow - * be able to define particular workflow for a path in the site structure (so a part of the site can become wiki, and the other verified area) - - * Unit-testing on sitemap's results. = user interface = - - * Here comes idea about the UI design (nice pictures or hand-made scan are welcome) + * Here comes idea about the UI design (nice pictures or hand-made scan are welcome) = Architecture = + * main core design lines, libs and external systems that are used - * main core design lines, libs and external systems that are used + * maven + * clean jcr implementation + * Built on Cocoon 3? + = process = + * the way works the app - * maven - * clean jcr implementation - * Built on Cocoon 3? - = process = - - * the way works the app - - * GUI template + * GUI template - * separate into the actual (2.1) template idea : + * separate into the actual (2.1) template idea : - * template configuration : inheritance of users, workflow configuration,... + * template configuration : inheritance of users, workflow configuration,... - * template GUI : independent, more flexible mechanism that allow to easily share template into community + * template GUI : independent, more flexible mechanism that allow to easily share template into community = api = + * api have to be simple, understandable, etc... but it's not easy ! Let's discuss about it here. - * api have to be simple, understandable, etc... but it's not easy ! Let's discuss about it here. -