techninja
commented
9 years ago 0.9.7 progress is going terribly what with FRC in full swing, #130 still having open questions keeping work from simply being head down implementation, and my day job/weekends have been unrelentingly busy. Not to mention trips to various teaching conferences are up and coming and are sure to sap any extra free time.
I've moved 0.9.7 release date to March 10th, and even that doesn't feel concrete unless we can get the implementation details for #130 wrapped ASAP, and I can get a move on on the other important pieces of this release.
The very first WaterColorBot was born 2 years ago this next week. I'd hoped to get RoboPaint v1 out by then, but that's just not in the cards. Oh well.
Happy Birthday WaterColorBot!
oskay
docprofsky
This issue is a placeholder for the work and discussion behind the next release and should act as a tracker for any release delays or important points about the build not already ticketed.
This release is intended to be the last planned release before 1.0.0. The goals of v1 are to ensure a fast, comprehensive, and mostly bug free environment to use at least two drawing robots. Everything is basically on track for this, though "comprehensive" is a bit up in the air, I'd interpret it to allow for more drawing modes by default, and especially one for raster image conversion.
For 0.9.7, we'll be focusing on:
130 - EggBot support: Over the course of dev for 0.9.5, it was found that the proper way to do this involved adding a bit too much, so while the branch was started, lots more work will be done. I certainly hope to make this one of the main focus', apart from other features/fixes as they come, this one is going to drive a lot of user experience and is therefore pretty important.
120 - Revamped quickload: This is somethign I've been wanting to do forever, especially to replace the really bad looking quickload menu I wrote myself one afternoon 2 years ago.
118 - Sub path painting: @gwygonik had originally submitted this one, and honestly it's a great idea, I just need to buckle down and find out the methodology and ensure it applies cleanly. I suspect with a few extra settings (min/max reink after/before path switch) with will perform quite well and certainly better than the existing non-path-aware algorithm.
34 - Automated updating: I'm voting this most likely to fall off the plate for this release. It would be awesome to have automated updating, but it's a whole new system to manage, for all three OS'. It's an updater, or an annoying message with a link :P.