[luci] LuCI view controller, and bmx6 luci moule

Manuel Munz freifunk at somakoma.de
Sat Apr 9 18:48:46 CEST 2011


Hi Pau

On 09.04.2011 18:11, Pau wrote:
> Hi people.
> This is my first mail to this mailing list. I'm Pau from Barcelona (
> guifi.net), last week I was in sublab, maybe some of you can remind me.
> Well,we are developing an OpenWrt based firmware for quick mesh deployments.
> The main freature is going to be the "out of the box" system. Where the user
> does not need knowlatges about networking.

this is a thing many communities need/want and therefore it may be a
good idea to join forces. I'm currently on some kind of mission, because
i think it may be a good thing to work together on one firmware to avoid
work being done twice (or more often). If you like contact me via jabber
(soma at jabber.ccc.de) or write a private mail, i'd like to hear more
about your plans.

> 
> I'm working with the LuCI interface, trying to adapt it to our requirements.
> We need one thing that seems not suporrted by LuCI system. We need control
> over the existing modules and where are them showed in the web interface.
> For instance, the OLSR module in placed here:
> luci -> admin -> status -> olsr
> 
> And we need to put it here:
> luci -> qmp -> olsr

Just out of curiosity: what does qmp mean and why do you need olsr to be
shown there?

> 
> The only way I found is editing the olsr.lua code, and modify the entry()
> function. But with a system upgrade or something like this the changes will
> be lost.
> Also we need to control if a installed module must be shown or not.
> 
> However, I am also developing a bmx6 luci module (I know jow is also working
> on it, maybe we should work togheter). And for this  module I have
> implemented the following freature:
> 
> /etc/config/bmx6
> ......
> config bmx6 luci
>     option ignore 0
>     option level1 admin
>     option level2 status
>     option level3 bmx6
>     option json http://127.0.0.1:8086/
> ......
> 
> You can find the bmx6.lua code here: http://pastebin.com/cYy2bYXN
> From line 6 to 26, you can see the code that read the parameters from bmx6
> with uci interface.
> Then, the position in the luci web site is allways dinamic, you can change
> the bmx6.luci options from uci to disable/move it.

That feels a bit too static for me, i.e. you assume there are 3
levels.If a feature to place modules at custom places should be
implemented i think this should be more flexible. But I'm not so sure
this is a good idea at all because it can make it hard to write
documentation or help users if everything can be everywhere in the menu.

[...]

Regards, soma

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : http://lists.subsignal.org/pipermail/luci/attachments/20110409/1719f55d/attachment.pgp 


More information about the luci mailing list