I saw somewhere that there were plans to develop an API to enable plugins. I was wondering if that’s still on the roadmap.
It’s something I’d be willing to explore and help develop if it’s just a matter of people power.
I have some ideas around CNC tooling I’m keen to develop. They’re safely out of the scope of most sender projects, including this one, but I’d like to avoid reinventing the foundations that have been laid with gSender (and CNCjs).
@kitizz a shame I just saw this now, but yes there is a part of our roadmap that includes trying to build in support to run community-created plugins so that people can expand the abilities of gSender without having to re-create their own all new g-code sender. Now that 1.5.# is released and we have a new ‘Tools’ section, this is the area where we were planning to implement this, and we’ve also already put in some work to make these tools more standardized so that they can leverage templating to make more.
At this point, it really is just a matter of people power if you’d like to go check out the code and start to make some tweaks. Right now the team is split between trying to bring on and train up a new QA role, building in support for ATC which had continue to be the largest ask from our users, and trying to get on top of clearing as many prior reported issues as possible to get gSender nice and stable now that we completed a large re-write to bring 1.5.0 into existence