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=20&rev2=21 -------------------------------------------------- Here comes some headings that have to be filled down. Headings and content are proposals, so don't hesitate to modify, suppress, etc... == General 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. * Another option: Export to standard format + import (similar to JCR) = Use Cases = - {{{ + . {{{ write here you how-to use idea, like if you are a simple user }}} @@ -31, +30 @@ * process I) A --> B * process II) A --> C --> D + * Use Case 2 : Forms by clic ² + - * 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,...) + * 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 = - {{{ + . {{{ wish list of all features you would like to see will be organize / topicazed soon. }}} @@ -89, +90 @@ * New UI template processing : have a really content <-> presentation independance : 3 majors ideas * 1) All the template in one folder * 2) UI architecture/structure is just another content - * The build of this structure can be done via the "forrest template mechanism" for lenya templating : refer torsten's answer here http://www.mail-archive.com/[email protected]/msg06961.html + * The build of this structure can be done via the "forrest template mechanism" for lenya templating : refer torsten's answer here http://www.mail-archive.com/[email protected]/msg06961.html * 3) Content can be place anywhere in the structure - * For realise this point, we have to define a "block-template" interface for each module. + * For realise this point, we have to define a "block-template" interface for each module. - * This interface is just a pipeline match into the module that output an xml with sections head/body/footer + * This interface is just a pipeline match into the module that output an xml with sections head/body/footer - * Just have to write the block-template interface in the structure for having an "in place I want" result + * Just have to write the block-template interface in the structure for having an "in place I want" result - * This photo represent a first draft done during the [[MeetingBordeaux2010]] : [[attachment:template.jpg]] + * This photo represent a first draft done during the MeetingBordeaux2010 : [[attachment:template.jpg]] * Email Notification/reminder to new users * see tickets : - * https://issues.apache.org/bugzilla/show_bug.cgi?id=29273 + * https://issues.apache.org/bugzilla/show_bug.cgi?id=29273 - * https://issues.apache.org/bugzilla/show_bug.cgi?id=29279 + * https://issues.apache.org/bugzilla/show_bug.cgi?id=29279 * search improvement : * 1) use solr * 2) an idea from ticket : https://issues.apache.org/bugzilla/show_bug.cgi?id=33702 - * The lucene integration should expose more details about the search, and it should be easier to add new fields to the index via a GUI. + * The lucene integration should expose more details about the search, and it should be easier to add new fields to the index via a GUI. * http://www.getopt.org/luke/ might be helpful * use HTML5 and CSS3 * Easy to use, an excellent site administration. * Good performance in big sites (better Lenya 2 than Lenya 1.2) - * Standars compliance. + * Standars compliance. + + * Content Comments + * be abble to add comments/ reviews / evaluation function to all Lenya contents (document, photos, ...) + + * Be able to login with shared identification services (facebook, google, etc...) + + * Have routines and easy integration with integration with famous social media... twitter, facebook, youtube, issuu (http://issuu.com/) + * have a built-in easy to use there api + * note : there is a component near from that in development in the apache camel environment + + * GUI composition module : + * Be able with clic and mouse to configure position of contents, blocks, menu elements in a Lenya graphical template. + * See the Drupal way of do, it's really cool and easy. == whised == * implementation of webcalendar calendar format propose calendar service = user interface = - {{{ + . {{{ Here comes idea about the UI design (nice pictures or hand-made scan are welcome) }}} * be more user friendly, interactive, web 2.0 = Architecture = - {{{ + . {{{ main core design lines, libs and external systems that are used }}} - * Andreas' Potential Architecture Diagram : [[attachment:architectureimage.jpg]] @@ -142, +155 @@ Lenya is actually in 2.1, 2.2 was "stable" and out from a moment and C3 is actually under development in alpha stage. Which version will be use ? Let's discuss about possible scenarios and pro and cons for each. }}} * Cocoon 2.1 : - * pro, with cleaning and optimisation : http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%[email protected]%3e + * pro, with cleaning and optimisation : [[http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/<[email protected]>|http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%[email protected]%3e]] * Cocoon 2.2 : - * con : http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%[email protected]%3e + * con : [[http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/<[email protected]>|http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%[email protected]%3e]] * Cocoon 3 : - * pro : http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%3c1275640168.2879.29.ca...@mckenny%3e - * hesitate : http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%[email protected]%3e + * pro : [[http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/<1275640168.2879.29.ca...@mckenny>|http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%3c1275640168.2879.29.ca...@mckenny%3e]] + * hesitate : [[http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/<[email protected]>|http://mail-archives.apache.org/mod_mbox/lenya-dev/201006.mbox/%[email protected]%3e]] * Cocoon 2.1 with module by module migration to 3 * see : @@ -158, +171 @@ {{{ the way works the app }}} - * GUI template * separate into the actual (2.1) template idea : * template configuration : inheritance of users, workflow configuration,... @@ -168, +180 @@ {{{ api have to be simple, understandable, etc... but it's not easy ! Let's discuss about it here. }}} - = Ideas to reuses = + * this ideas are from an old 3.0 roadmap. * some of this ideas have to be reuse into this document : - * this ideas are from an old 3.0 roadmap. - * some of this ideas have to be reuse into this document : == Options == - === A: Evolution === * Preserve backwards compatibility @@ -189, +198 @@ 1. Migrate modules step by step === C: Clean Cut, Reuse Experience === - 1. Reconsider all requirements thoroughly 1. Derive architectural constraints 1. Choose architecture 1. Reuse code where it makes sense == Architectural Constraints == - * No changes to URL space and mapping between URLs and pages required * Workflow-driven content manipulation * Access control on repository level - permissions assigned to content objects rather than URLs --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
