Allowing users to output the proper G-code for their specific machine(s) is most definitely a part of the core PixelCNC vision, and is fast approaching as one of the remaining features left to implement. Hopefully post processor support will be in by the holiday season, at the latest.
The support for CNC posts, which will include a built-in post editor for users to create posts if they are not included for their specific machine, has been on the development roadmap since the beginning as a ‘primary feature’, of which there are several others. Once all primary features are implemented PixelCNC will enter the beta phase of its development.
As these primary features are added so increases the value of PixelCNC as a whole - which is reflected in the price increases that come with new features being implemented. Customers who buy at the earlier prices get all new added features for free, at no extra cost. New customers pay full price. This works two ways: it shows appreciation to early customers for their support while simultaneously giving potential customers an incentive to buy now, spurring sales in the near-term.
Also, I’m debating integrating an automatic post-sharing system alongside the post editor where users can submit their custom posts to a central 3rd-party post library. The library would then be browsable from within PixelCNC so that users can seek out unique posts to install without having to hunt them down on forums or create them from scratch themselves. This is an example of a ‘secondary feature’, where supporting posts at all takes precedence and this would be a sort of bonus that likely would come later, depending on the complexity of the solution that is devised to make it happen. It would definitely make it a lot easier for users to share posts.