3 Feb
2015
3 Feb
'15
7:28 p.m.
I don't think they are gonna remove luci-lib and so on, there are many
applications which are using it. However we may ask it to the luci
developers to be sure which are the plans for it.
On 30/01/15 19:12, Gioacchino Mazzurco wrote:
On Friday, January 30, 2015 12:00:29 PM Pau wrote:
--
./p4u
Yesterday I tested the current implementation of
the web interface LUCI2
[1] (which will replace LUCI in the future). The basic administration
menu (Network, WiFi, System, Status, etc.) is already implemented and
works fine.
LUCI2 is a 100% rewritten web interface and it does not use lua anymore.
It is just a small uhttpd plug-in which communicates Javascript with
ubus via standard JSON. So it is quite more flexible and less resources
aggressive for the router (since the JS is executed in the client side).
I would recommend to start thinking in LUCI2 instead of LUCI, so we
should base the future LiMe web interface in LUCI2. Would be nice to
have some JavaScript expert into the team :)
This is related to the removing of part of the API like Hex() ip constructor
and so on?
What should we do at this point? On our code we rely on luci-lib (the one
written in lua) should we consider that openwrt folks will drop those
libraries soon or later ?
Should we repackage some lib like nixio that we are actually borrowing from
luci?
For the moment i believe we should have our how clone of luci repo with HEAD
fixed to the last point it is compatible with our code, and refer to luci2 for
future development not for the actual stable release