Red Query UI - a NodeRED inspired low-code platform for front-end programming
Github Page: https://mdkrieg.github.io/ReQUI
Basic steps to decouple frontend from backend:
- Used "wget" to get the base HTML from the http://localhost:1880/ endpoint of a running node-RED instance --NOTE: I'd originally used the browser's "save as" to get this which was a mistake and was causing a lot of the problems I was having
- Started an iterative process of identifying any missing sources and then saving flat files in the correct places to satisfy all endpoints, sometimes this involved changing the endpoints in
red.min.js
to include the file extension - At this point the interface works but the websocket fails and the deploy button throws an error "cannot POST" - naturally...
- To null-out the websocket I added a
return;
to the very beginning of the websocket's connect, subscribe, and unscubscribe functions. Effectively make the websocket do nothing (this doesn't seem to be a problem for me "yet") - To make the deploy button save to window.localStorage like I wanted I found both the ajax functions and inserted my simplistic
window.localStorage.setItem("flows",JSON.strigify(c))
and then commented out the ajax including the .done .fail and .always functions being careful to leave the contents of the .done and .always functions (including a line to setvar e = c;
to spoof the input of this function. - Pulling the flow from localStorage was similar to above but a little simpler.