Yes, that's one of the possible applications (gradient fill from lines or points too).

Done !

Nope, not yet, but I do it right now.

Maybe, instead of changing the unit name, it would be better to add tooltips. Since the unit lists are implemented using Qt models/views it should be easy.

We discussed two things with Boud:

Correct the patch:

Reopen after phabricator autoclosed because of a reference in a commit :S

Ok, from the previous café, a few notes:

Thanks for the test !

Yes, but I did not found any example of how thoses abreviation are translated,

Do you have any reference about internationalized units abrevations, I found nothing on google (not sure I search correctly). Anyway, are you sure it's needed to internationalized that ? It may makes the doc overcomplicated no ?

I ran into some nasty problem today. Basically I want to add support for image relative units directly into the KisSpinBoxUnitManager.

Ok, for time I think we should say frames are the reference (since time is managed in frame in KisImageAnimationInterface). seconds should be a relative unit, configured from the framerate.

For the next merge windows I will try to have the second part of the project ready, meaning unit management. Here are some idea about it:

Sure for the object model. If we need to do a refactoring we can do it at the same time. It may also be usefull to collect potential usecases.

Ok, so as we discuss before I think python is the best choice of language because:

The procedure I use to test is to open an image then go to image size. To test the functions you need a doublespinbox (intspinboxes just do arithmetic) so just select percent as a unit. Then I write my formulas for example:

Cool, thank you.