Release planning

[xblax]

Starting a general thread about release planning.

I think many of the first public beta issues were fixed, another beta release is due. Does anyone see any issues/improvements that are already solved but did not make it into the master branch?

@consp and other GitHub collaborators:
I did already create a draft Release for the v00.04-beta version. Do you see anything that's missing?
If nobody disagrees I also think that KlipperScreen can be promoted from alpha to beta.

[KaruroChori]

I think the list for 0.04 is fine, but I have not been able myself updated over the last week, so I might be missing something. Finally I am back printing.

[consp]

Starting a general thread about release planning.

I think many of the first public beta issues were fixed, another beta release is due. Does anyone see any issues/improvements that are already solved but did not make it into the master branch?

@consp and other GitHub collaborators: I did already create a draft Release for the v00.04-beta version. Do you see anything that's missing? If nobody disagrees I also think that KlipperScreen can be promoted from alpha to beta.

I'll have a look tonight and test it as well, currently only a few commits behind so shouldn't be too much of an issue.

KS works good enough. Still a bit slow, I'm considering looking into the lvgl idea with guppyscreen if it's more responsive since klipperscreen works and i'm not sure it can be more performant, should also use less memory. Biggest problem there is WiFi support. Lot easier to do in python than c++, but there are ways around it. That's something for another day though, for now the way to go is KlipperScreen as its easily modifiable and not too hard to run (and mostly stable except some quirks).

[consp]

Biggest issue I'm having so far is lack of prompt support, don;t know if that's simply not done yet or is broken.

Well, my hacked together c contraption wrapped around some c++ code seems to work so that might not be an issue anymore. I can shut down at least (options are VERY limited, colors do not work and that's because lvgl cannot do different button colors in a msgbox).

This fixes the "I cannot shut down when I'm at the printer" "problem" I was having.

Are there any other commands with prompts?

[KaruroChori]

What do you mean with "commands with prompts"?

[consp]

commands with prompts

Anything which uses action:prompt_begin

I was under the idea the save_config also had this but that is not the case.

[ballaswag]

Take a look at this build configuration I use for the CM1 on a btt pad 7 https://github.com/ballaswag/guppyscreen/blob/bcfa539b941f616da25d4958f9eb15525901138b/.github/workflows/build.yml#L35

It sets up a few things for make to build for ARM, like cc and cxx, and some guppy specific flags like evcalibration, rotation, and target small size screens.

[consp]

ARM, like cc and cxx,

Pretty much the way I went. Strange thing is the libhv cmake ignored the cross_compile but maybe that's an error on my side. Adding a CMAKE_CXX_COMPILER define and it works like a charm.

evcalibration

Fortunately it's not needed, the touchscreen is calibrated stock via tslib and with ts_uinput you can make a calibrated evdev.

[consp]

Do you see anything that's missing?

Added #68 to the "servo issue" since the images are there. You made a pretty good coverage of all the fixed issues. Nothing jumps out as missing.

[KaruroChori]

For reference: #57 (reply in thread)
If I recall correctly, consp was able to integrate the patched file at some point, but it was not carried over for the latest release.
Should we get it back for the next one?

[xblax]

Yes, I'm planning to do that. Probably for the next release. I'd like to make Klipper, Moonraker and Mainsail Buildroot packages even if there is not much to compile, then we can use the automatic patch handling etc.