Skip to main content

Planning update

Β· 2 min read
David Zwart
Founder / Lead Developer

πŸ“† 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)

April 2024 Updates

Β· One min read
David Zwart
Founder / Lead Developer

πŸš€ 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

Β· 2 min read
David Zwart
Founder / Lead Developer

πŸ€— 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. πŸ’‘

Connectivity to OctoPrint

Β· One min read
David Zwart
Founder / Lead Developer

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ℒ️

MongoDB to SQLite

Β· One min read
David Zwart
Founder / Lead Developer

An easier setup without external database​

Time for an update from my end. In the previous months I've announced a shift from MongoDB to SQLite. The SQLite database code is nearing completion, and Im testing the server + web client together now. So far things seem to work beautifully! The migration process is not an easy one, and I want the transition from MongoDB to SQLite to be as smooth as possible for all existing users! Please hold tight for those reasons. Users starting afresh would not have this complex route, so if anyone is interested I can already look at releasing a test docker container with SQLite - thumbs up below to show interest!