On 4/10/08, Richard Frovarp <[EMAIL PROTECTED]> wrote: > kanth nalluri wrote: > > sir, > > in the enhancement of lenya i want to add the following > feature > > all configuration files should be editable through the GUI > > i want to know the solution and the way to do it? > > There are no more details than that. For those not following: > https://issues.apache.org/bugzilla/show_bug.cgi?id=35176 > > You need to develop a basic understanding of how Lenya works, before diving > into such a project. Looking at the bug, it was filed in 2005 against 1.2. > Not to say that it still isn't desirable. By using and configuring Lenya you > can see which configuration files there are, what effect they have, and what > you can configure from the GUI. Several of the configuration files are now > editable from the GUI: proxy settings, usecase settings, security settings. > > It is up to the person doing the work to offer up ways of solving the > problem. You may want to use the system some and then choose a simpler > problem to start with.
Wow. My old suggestion is still open? That bugzilla predates my becoming a Committer. Does anyone developing Lenya-2.x care about making design files editable through the Web GUI? From my limited knowledge of Lenya-2.x, this functionality may not be easy to integrate with the Lenya-2.x Module system. I am actively working on this feature for Lenya-1.3. My current work (saving sitemaps/structures/relations) has been delayed from being committed because it needed the infrastructure for editing configuration files. The code included a rather complicated infinite loop: - The Content object requires initialization information from Modules: Resource types, Revision names, Structure names, Index configurations. - Moving Module configuration files into Content means the Content object is required to initialize Modules. The problem derived from creating Design Resources by adding functions to the FlatContent class. Creating a FlatDesign class should separate the concerns and solve the technical problems. Once the non-XML text editing Module is completed, every file in any Module will be editable through the Web GUI. (Note: Lenya-1.3's Modules cannot include compiled Java. They are very similar to Lenya-1.2's Usecases with XMAPs, XSLTs, CSS, JS Flow, etc..) Answering the main topic: Lenya 1.2: Editing design files using the Web GUI might be difficult. Design files are dispersed throughout the Publication's directory, may call global files without warning, and have no method for being overridden for a specific Publication or function. Lenya 1.3: This function is a prime specification and will be available soon. Modules separate files by functionality. Module Inheritance allows easy overriding. The ability to store Design Resources as Content should be in my next commit. The remaining tasks are the text editor and listing all files for a specific Module; both are easy and may appear at any time, but the priority is reproducing Lenya-1.2 functionality (and this feature is not in Lenya-1.2.) Lenya 2.x: Others can answer better. I have seen no discussion planning this feature or analyzing its feasibility.. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
