Yes, it can.
No, I don't think that is a good idea & it should not be necessary.
However, it is open source so you are free to clone it and create your own version.
Thank you @TotallyInformation for your response.
If settings.js is enough to hide the Node-RED palette, I’ve been trying for a couple of days but it doesn’t work. Could you please help me with what changes I need to make in settings.js?
Thank you @lgrkvst for your response.
I think that to modify the source code like you did, it’s necessary to understand the objects and architecture of Node-RED. Do you have any information, PDF, or link that explains how Node-RED works — its architecture, folder/file structure, and the role of each file?
Can I ask why you don't use the un-minified version of the js file? It seems like a giant maintainability headache using the minified version. Also are you that interested in upgrading with each new release of NR? I tend to stick to one version of NR and extend out from there.
When I created dead red - the head less node red - I moved to using RED.max.js so that I could better make changes and locked on the version 3.1.3. If I do want to update that code base, what I have is a retrieve script that obtains everything needed to run the NR frontend - including nodes and plugins frontend code.
I extended that script for Erlang-Red (which implements NR in Erlang) to work for NR version 4.x. I regularly update the NR codebase when I update the nodes installed - i.e., I have a source NodeJS Node-RED installation where I install and update nodes and plugins. When I have done a node update, I subsequently copy the codebases of that installation to Erlang-Red using my retrieve script. Finally I implement any backend functionality in Erlang. Rinse and repeat.
The point here is that it's a structured methodology in copying the NR frontend. Admittedly an upgrade of the NR version would be difficult but I have no ambition to do that. If I were to start a new project, for example Rust-Red - NR in Rust - then I would take the latest version of NR and extend from there.
Hi @gregorius,
It seems you have very deep knowledge of Node-RED.
Could you please guide me step by step on how to hide the default Node-RED palette and replace it with my own custom palette?
This is the first task I need to complete. After that, I plan to add a low-code GUI that will allow developers to add new custom components.
I'm currently stuck at this point and not sure where to begin.
Thank you in advance for your help!
