Nathan
Nathan Angelacos wrote:
Thanks for all the positive feedback on webconf so far. There is a
suggestion that webconf.lrp (core) be just a weblet replacement, and the
current "expert" menu set be moved into webconf.lwp.
The reason is situations where an admin wants to give a customer "read-only"
rights to web pages for monitoring; but the customer shouldn't have access to
"fix" [pronounced: break] the installed router.
This makes sense to me; it means webconf.lrp is the replacement for weblet;
webconf.lwp is the value-add for most "do-it-yourself" SOHO users; and
extra .lwp's add further functionality.
Here's a proposed breakup of the existing webconf.lrp (beta 2)
keyboard.lwp -> keyboard.cgi (basic menu set)
dropbear.lwp -> dropbear.cgi (basic menu set)
webconf.lwp -> lrcfg.cgi (expert configuration pages)
-> lrcfg.pkgdisks.cgi ("Destinations")
-> leafcfg.cgi (Edit leaf.cfg )
webconf.lrp -> (all the framework, lib, css, etc)
-> connection-info.cgi ( Active Connections)
-> general-info.cgi (General Health)
-> logfiles.cgi (Log Files)
-> lrcfg.back.cgi (Backup Packages)
-> wc-passwd.cgi (Webconf password)
Wouldn't you think dropbear.cgi and keyboard.cgi belong to dropbear.lwp
and keyboard.lwp, especially for keyboard-less boxes.
Erich
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
