Well I started testing .14, hopefully today I can load up .15 depends…
They moved it to deeper in the repo. Maybe give us a few days to get a more official set of files ready so no else hates it on first run. I am not seeing any of the issues with V3 but I also know how to navigate it a bot more. When we get the settings file and the right index file ready and tested, it will be as simple as moving a couple files.
Just curious for those who know how fluidic works ‘under the hood’ - is something like an mqtt addon/extension/plugin realistically possible or is the cpu load too high as is?
What did you have in mind?
A pub/sub client to post status/error messages to an mqtt broker.
Some uses off the top of my head;
Logging jobs - the file name, actual work time start to finish
Activate a ‘do not enter’ light when lasering
Control led strips on the gantry
External monitoring displays - current, feed rate
Hardware buttons / interface to control without a browser
There’s an mqtt plugin for octoprint which I used with my Rambo board so I could use physical controller for jogging and zeroing but of course thats a whole lot more processing. But mqtt runs on esp8266 at the same time as wifi and sensor readings. But of course fluidic is somewhere between that and a pi.
Hmmm… That could be handy. I must say that I do like the ability of monitoring the status of a couple of my 3d printers when I am out and about. I do that via Home Assistant with an Octoprint Integration. Like you mentioned, that has the power of a RPi behind it so it integrates video and such, but a simple MQTT client certainly has merit.
Okay, I uploaded a V3 section, GitHub - V1EngineeringInc/FluidNC_Configs: Configuration and support files for the FluidNC boards typically used and V1 Engineering
I ran these files all day yesterday on some aluminum. The preferences are not perfect but they work. There are a lot of adjustments that can be done. (for example I think the moves should be faster). More macros…
The preferences are from Mike and he understands all this far better than I ever will.
Now that the files are there we can try to agree on some universal settings and I will change them in the repo.
Do you have the Theme file? might be worth adding that there too in case someone wants it. If not, I can dig it out later
I don’t if you can link it or PR it I will add it. That is a good idea.
This will get us all working off the same files. Then we can really start progressing again.
If you unzip that, the theme-FluidNC.gz just gets placed on the storage next to the html.gz file
Added thank you!
Does 3.7.15 support the V3 UI? I didn’t get that impression from the release notes.
Yes it does.
OK, It’s been 3 hours. Does anyone have a dark theme yet? 
Seriously, this is nice work. It took me a bit to figure out where everything is, but that’s a good thing. The ability to modify the stylesheet (theme) is nice. Especially handy if you have multiple machines running on the same net. Panel ordering 
. What’s not to like?
I need a red and black theme if we are placing orders!
I should take a look and see if I can do it or not. What is the best tool for the job, vscode? Is there an easy way to preview? I really feel like I was told the answer to this before.
I wrote it up a couple times…I’ll have to find it…
My fork is here:
In the WebUI, there is a built-in simulator. It will just run and you won’t be connected to a board, but you can do lot’s of things. Just opening that index.scss file and making a change, and within a second or so, the web page will auto update.
Install current nodejs LTS (currently using v20.8.0)
Clone that repository. Switch to the “3.0-FluidNCDev” branch.
Open the folder in VSCode.
Open a terminal, and run
npm install
You should see a “NPM Scripts” area. Click play on “dev-cnc-FluidNC”
In VSCode, open \src\targets\CNC\FluidNC\style\index.scss
Any changes applied there, should auto-apply to the running browser.
so, the easiest way to create a theme (I’ve found)…
Is to find _variables.scss, edit the colors there first for primary/secondary/etc.
Then run the compile and get the index.html.gz, unzip, and extract the full built CSS from there.
I then copy that css into the index.scss of the FluidNC target for testing with the simulator. That makes it so live reloads work, etc while tuning colors.
When done and happy, I then copy all that CSS out from there into the “theme-” file to be used in the interface
Doing it that way made it much easier for me to get all of the purple color out of the controls, etc
That’s a paste of information from a few different places I’ve written before I’ve just aggregated together…
Should be a good enough start for anyone that wants to give it a shot.
I can try to help with any questions, but I am not a Web Developer…or a designer 
That was enough to get me started. Certainly something I’ll play with more when I have some time.
A couple notes:
npm run dev-cnc-FluidNCI am a bit curious on where your branch came from and the updates you made. I tried cloning other repos but they didn’t have it all.
I don’t have anything npm specific. Those targets have shown on every computer I’ve ever opened it on 
For your own personal compiled build, you can certainly do whatever you want. Anything outside the FluidNC targets is changes to the main code base, so when I was writing instructions/notes it was always from the perspective of being able to submit a PR back to the main repository.
In reality, the last part I wrote that starts “so, the easiest way to create a theme (I’ve found)…” is the easiest way to build a theme and make sure everything is consistently across all the controls.
Any of the other methods of trying to manually replace things in the scss files is a lot more tedious, and harder to make sure you catch everything
It came from me. I forked Luc’s repo and made all the changes related to getting it to work with FluidNC both in the WebUI, as well as the FluidNC side.
If you want to see what changes I had to make to get it all to work, the majority of it will be under one of the FluidNC folders, but easiest to just look in the history at the commits on that branch made by me