Hi, I think this is a good idea. Though, it isn't the 'break-up' I imagined when I first started reading your message. I just assumed the LuCI webif was minimal with the option of adding tabs -- much like the original webif.
I suppose the questions I still have about the LuCI webif project are: 1) will it try to only configure UCI files, or will it generally be creating application configuration files? 2) will it become the driving force in defining the UCI variables and their meanings? In my mind, there are several distinct elements: - creating application configuration files for the packages needed to implement 'features'. - defining and the logic of 'feature settings' (for lack of a better term) expressed in UCI, for example "LAN DHCP Network" being written into UCI config/dnsmasq or config/chilli based on the option "Hotspot Enabled". - and the web interface to configure it. The first element is largely the task of shell scripts for core settings, and the rest is LuCI. The more you keep the elements separate, the easier it is to switch out the pieces, which I believe is a key element in getting a broader contributor community over those interested in this specific web presentation. I would even add another element above the webif for: - configuration and status web services (API) to further decouple the features (gathering status, setting UCI) from the presentation layer. Cheers, David On Sat, 2008-07-19 at 20:13 +0200, Steven Barth wrote: > Hello Everyone, > > much work has been done this week and thanks to your feedback and opinions we > are happy to inform you about the latest project updates. > > After the recent discussions about user-friendly vs. full-featured interfaces > we decided to split up LuCI into two parts "LuCI Administration" and "LuCI > Essentials". Administration is the usual full-featured power-user interface > while Essentials serves the non-power-user's needs by just providing the most > important configuration settings in a simplified user-friendly way. > > Essentials contains configuration and status pages for basic > Network, Wifi and System settings > and can be extended with modules for > Portforwarding, QoS, DDNS, UPNP, Time-Synchronization > > Everything of course with theme and translation support. > > You will find some screenshots of Essentials here: > http://luci.freifunk-halle.net/WebUI/Screenshots/Essentials > > Build instructions - as usual - can be found here: > http://luci.freifunk-halle.net/Installation > > LuCI Essentials (as well as LuCI Administration and the additional modules) > can be found in your build configuration under "Administration" -> "LuCI - > Webinterface Components" after adding the LuCI OpenWRT feed to your > buildroot. > > > Greetings > Cyrus > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
