From 609d1a4ddb54e5c4e47f5b1415c60212024bca26 Mon Sep 17 00:00:00 2001 From: Aircoookie Date: Mon, 25 May 2020 18:27:21 +0200 Subject: [PATCH] Updated Add own functionality (markdown) --- Add-own-functionality.md | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/Add-own-functionality.md b/Add-own-functionality.md index b3d0ebb..a43f8c4 100644 --- a/Add-own-functionality.md +++ b/Add-own-functionality.md @@ -79,14 +79,7 @@ If you programmed a nice effect you want to share, submit a pull request! Changes to the embedded web user interface are not convenient. The reason is that the HTML is gzipped and added to the code as a binary array in `html_ui.h` to boost speed and lower flash usage. -If you want to test changes to the UI, it is easiest to work with the local `/wled00/data/index.htm` file. You just need to change a single line to have the local file interface to an ESP with WLED installed. Preview - -Change -`url = command ? '/json/state':'/json';` (0.9.1 line 1048, subject to change) -to -`url = command ? 'http://[Your ESP IP address]/json/state':'http://[Your ESP IP address]/json';` - -**Important:** Do not forget to change it back before gzipping the UI file! Otherwise it will not work on any other WLED installation with a different IP address. +If you want to test changes to the UI, it is easiest to work with the local `/wled00/data/index.htm` file. You just need to enter the IP address of a WLED 0.10.0 or newer instance into the popup. If you accidentally input an incorrect IP, or want to test with a different instance, clear the local storage (in Chrome: Developer Tools -> Application -> Local Storage) To serve your changes by the internal webserver, you will need to follow these or similar steps to gzip compress the `index.html` file: