Do any developers build luci outside of the full OpenWrt build system? Surely you’re not running a full build every time a UI change is made.
I am looking at adding a few tweaks to the UI but need a fast build/test loop.
Do any developers build luci outside of the full OpenWrt build system? Surely you’re not running a full build every time a UI change is made.
I am looking at adding a few tweaks to the UI but need a fast build/test loop.
You probably want to look at building a single package and using the SDK.
In addition, the ucode and other files can be edited live on a test device. In addition, for ucode, the ucode binary on the device can compile to bytecode (if needed, generally you don't have to use bytecode and can run using the plaintext versions) as outlined in the ucode tutorial.
HTH
If I'm just experimenting, I'll edit the file right on the device. If it's a mangled .js file, I'll first wget the proper source file from up on github, so it's easy to see what's going on.
ssh router
wget https://raw.githubusercontent.com/openwrt/luci/refs/heads/master/modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js -O /www/luci-static/resources/view/network/wireless.js
vi /www/luci-static/resources/view/network/wireless.js
If I'm actually working on something for a PR, I'll edit in my local clone and scp the file onto the device. Not that much harder, but there's that extra step that slows you down.
I test in Firefox. I always test with the debugger on and have the "don't use cache when debugger running" option enabled (not sure what it's called).