Hey, Martin! Thank you for all your efforts to make Inkscape better! You are doing really well! Hope you continue. Thank you so so much!

Super interesting presentation, it really manages to show the depth and complexity of your work. I for one would love some even deeper dive on the actual code

Making history! Martin Owens 🎉

I understand your work with color, and I think the order you are putting in everything related to color is very important. The truth is that with so much chaos and duplicity, it makes future jobs difficult for programmers. We thank you for all the work you are doing.

1: I think introducing change is OK @ 7:02 as long as it makes the software better. 2: Separating code is essential even for smaller software. 3: otherwise I totally agree with you. I hope it workout.

It sounds good. And it sounds necessary.

Cool, great presentation

18:15 I'm not sure if this would be relevant to the actual intended audience, but I feel a quick explanation of what an icc color profile is could be beneficial. Thanks! I'll keep sharing. Great work!

Finger crossed for good reception, FOSS can be very bumpy in terms of changes, because of personal ego, worse knowledge, different type of knowledge. In my opinion you are doing great work, Inkscape need CMYK to grow in popularity.

good!

A couple of spelling errors: In the Utilities slide “consistently” is spelled thus, and in the Signals slide “implemented”.

27:03 The signaling seems very interesting and kind of hard. Specially in regards to handling multiple selected objects. I also like the idea of being able to change a single thing in one action for multiple objects. I feel the most common use case would be the saturation and opacity. One of the hard things to sort out when dealing with batch editing I think is deciding between setting or changing properties. While the first is easier because you set new property despite current value, on the later you would need to check all current values and only allow those identical to be changed. Or, a third option is to allow for proportionally changing like increase/decrease saturation/opacity instead of setting all selected to the same value, or allowing the user to change the opacity only it all selected objects currently have the same value for that. In top of all that there's all the UI/UX decisions.

A few comments: * color conversions between different ICC profiles can either use relative colorimetry or best match perceptual. Which approach will be used? Last time I messed with this, I got super confused and stuck. * 15:30: What is SPObject (what is SP)? * Will Color objects be immutable or will they be modifiable? I think this would be a very important decision that would need to be justified. * How is Drag & Drop related to colors? Is this about clipboard serialization?

Martin, seria possível qualquer dia desses vc postar um video de você implementando algo no código do Inkscape, acho que seria bem interessante, apesar de entender muito pouco ou quase nada de programação.

Tackling the color space is only for grown-ups. Might have to watch this again. Could this be re-made into a video game?

Thank you so so much for your good work! As touching compatibility, should we expect PSD or XCF file compatibility in the near future? I believe this alone can encourage a good number of potential users. Should we also expect TIFF export in CMYK as this is what most Large format Machines use?

25:07 it's not clear if do future programmers should add new stuff to the utilities or in the color API itself. I feel that maybe some utilities might be a standalone code while others an interface for some specific API code. Perhaps clarify or explore that distinction a bit could be useful.

Just as a matter of presentation style Martin, is there some way you can slow down your presentation a little? Your fast paced delivery is a little hard to follow in places.

20:43 it's ok to say you don't like something but I'd recommend not startin stating that it's not a good design. Maybe it's better to acknowledge that there are different programming paradigms but that for the sake of global consistency it's probably better to stick with object oriented because this and that...