As stated before, there appears to be several people doing preliminary work on modifying Weblet to be used as a web-based configuration tool in the LEAF community, but not limited to the LEAF developers. It would be safe to assume that at some point redundant work will be done to achive the same end result. It would seem to be logical to form a consolidated group of developers to work together on this project, so that 1) development would be faster, 2) each developer could focus on a particular piece of the code, 3) the finished product would likely be better and more portable in respect to LEAF itself.
How (and if) a group to develop a web-config package should be formed and run within the LEAF site is questionable and any idea's and advice is appreciated for a direction to take. At the moment, the work that has been done has been considered to be an extension of the weblet package and/or sh-httpd. Personally, I find a Web-configuration product to be something that is it's own entity, and be treated as such.... even though extensions will be made to the present sh-httpd code and integration with weblet will be a safe assumption. Shell/CLI environment configuration will need to be availible and the finished package should be optional as a package to the LEAF release(s) used on. I think a dedicated CVS branch, a means of communication, a schedule, and a roadmap would be general requirements to a clear and efficient development cycle for such a project. Is there an existing way to do and or all of this within the present LEAF infrastructure? Thoughts??? -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
