David Zwart

Klipper support​

After the work on 1.6.2 I have started work on Klipper for FDM Monster 1.7.0 🥳

📆 Planning​

The past two weeks have been mostly about planning and refining the work for FDM Monster. It has become clearer to me and others that the project needs a cleaner roadmap.

Together with @Dyrant we've been able to formalize the roadmap and shape the work into Github Milestones The result is a development cycle which slightly looks different than what was before:

• a set of specific features are selected for a release (version 1.6.0)
• in a follow-up cycle, bugs are collected, prioritized and fixed (for example 1.6.1, 1.6.2 and so on)
• and then the next cycle: work towards a new release starts (for example 1.7.0 with Klipper support), but also work on documentation, site and overall code quality (administration)

🚀 Updates​

This week I have started the upgrade of the frontend UI of FDM Monster. I've allocated quite some time to upgrade from Vue 2 to Vue 3. Luckily, this is not the first time I'm doing this so it will be a feasible but impactful task. I do want to emphasize that this gives mental space for Mobile Design of FDM Monster, something I've been putting off quite a while now.

🤗 Bit of a break​

The last few weeks I've given myself a bit of a break. This was necessary after a lot of work was done recently. It is important to take rest every now and then! This was also a source of inspiration around this project. 💡

This week I updated the connectivity to OctoPrint. I added more robust state updates, to make sure FDM Monster reports the right state in the UI. There are more tweaks to be done, but this is already great! I tested it on OctoPrint 1.9.3 and I plan to test 1.8.x soon, to make sure you all will have a smooth ride.

Released in: 1.6.0

When: soon™️