This will most likely no be a very popular position. I think that I can safely say that I have cut the most metal of anyone using the Plasmac branch. At the present time it works very well and only lacks one feature I need and I have hacked that in myself. Most job shops or engineering type users will never use this feature. Now the fact of the matter is most hobby or small shop users don't need a 100s of entries tool (or cut parameter) table for everyday work. The scale of the present Plasmac ones and the ease of entering new parameters makes me question the need for the all singing all dancing tool handling methods. Most people use a single tool for an entire sheet with the possible exception of smallish holes which are usually covered with special codes. So I will go so far as to say Phill has produced a really wonderful product that has taken LinuxCNC plasma cutting to a whole new level. May I be so bold as to suggest that now is the time to take a good look look around and consider what the future of LinuxCNC may look like and find collaborators from different areas to move forward with modern screen builders (the various QT stuff I know nothing about) and maybe an as yet undefined universal tool handling method. I bet Phill might like to finish his machine some day instead of chasing new features in Plasmac. I seem to recall that Python 2.7 is rapidly nearing the end of life and we are still stuck using Glade 2 for GUIs here.
Well if you guy's want to hear my 2 cents it is a topic that doesn't even belong here. Will someone please take the Gcodetools foundation (open source) in Inkscape and make a really good CAM with nesting application out of it. This will make a complete open source tool chain for plasma and milling. While pretty crude the underlying code in Gcodetools does produce nice Gcode for cutting if you can get past the UI.
Well lets just run with what Phill has got now, tidy up anything left unfinished and push the powers that be to get it into master branch ASAP.
We can all follow John's hack to enable/disable the THC.
BigJohn has done some work on nesting already.
A sheetcam post processor would be a nice inclusion before its pushed. Maybe one of us can contribute that. How clean is yours John? Mine still has a lot of CandCNC stuff in it but it still retains the centre punch option. All of the CandCNC fields need deleting and a toolId added.
rodw wrote: Thats actually a separate userspace module written in Python. You should be able to control it from sheetcam settings from your post processor.
