Yep, no problem! Yeah I'll do what I can, but if I get stumped, I'll definitely let everyone know how far I've gotten. It'll at least let anyone else who tries know what may or may not have worked. Still yeah, I won't do everything at once. I'll focus on each bullet one at a time. For now I'm focusing on exchanging the title bar. And yeah, those two sounded like the most complicated since they would involve larger changes than UI or interaction, but a fundamental change.

I'll do my best to implement as many of these as possible.

• Bigger Toggles = Should be a matter of adjusting the pixel size for the UI. I'll definitely make sure of that as UI is my specialty
• Alt + Click to only show that one = I'll have to try it myself, but I agree, I can add that ability and make it toggle the single select.
• Curves as Vectors = I'll have to see how the vectors and curves are drawn and manipulated, but I do agree it'd be a lot easier if they used the same editing mechanism.
• Numerical input = Agree and should be easy to do.
• Curve Presets = Similar as the Curves as vectors, I'll have to look at how the code handles those, but once I figure it out, I can try to copy that over
• Rotation circle based = I presume you mean it always rotates from the 0 = up point rather than from its current position? I should be able to add a toggle that determines if the rotation is relative to its position and add a step mode and a 0 button, but I'll need to figure out what's best here. I'll have to look at how it works.
• Rotations as Radians = I heavily agree it should be degrees. Radians is useful for calculation, but degrees is VASTLY more intuitive for UI. We can translate these values in the code so the display is easy to understand and remains flexible.
• Normalize View = I agree as well. With graphs I always like to normalize so the data is as clear as possible. Shouldn't be too hard. Get the max value and min value of the curves and add a little buffer to determine the view size. Just gotta see how it's done in the code.
• Scalar keyframes support frame labels = That would be ideal. Hopefully it's just a matter of making the frame base universal so the labels are part of it by default. If I'm understanding that correctly.

Ah excellent! Thanks for the mockup! It gives me an idea of what changes to aim for. Yeah, reducing the size of the UI icons definitely helps for smaller screens so the icons don't take too much space. I'll play with it to see if I can get it out of the way enough, but still visible for high res monitors that are physically small.

Sounds good! Yes I will review that area to see how the working example works and apply it to the Curves Docker. Thanks for the tip! I'll start pulling the code soon and get to it!

I will take a look at this and try to get started on it. If I can get in a good position for this development, I'll claim it and take the mantle. Just need time to get set up, review the Curves docker and break down the task into steps for improvement.