https://bugs.documentfoundation.org/show_bug.cgi?id=169505
--- Comment #5 from Michael Weghorn <[email protected]> --- (In reply to Eyal Rozenberg from comment #4) > On GTK we lost RGB, HSB and CMYK; > On Qt we lost just CMYK; > On Windows and Mac - I don't know. On Windows and macOS, LO's custom color picker is currently still used, i.e. no change there. How to continue is certainly up to the UX team to decide. I personally think there is value in integrating well with the platform/desktop environment and use existing platform/UI toolkit dialogs where available, also for consistency across applications - and ideally reporting and addressing any shortcomings upstream, so that LibreOffice and all other projects using that functionality can profit from it. My tdf#167669 comment 18 has some more thoughts on that. One feature the Qt and GTK color dialogs provide that the LO one doesn't is to select a color from an arbitrary pixel on screen. I agree the GTK one is more limited at the moment, though. (RGB values can still be entered in hex form as is often used on the web, but that's not intuitive for everyone.) Potential approaches I can think of: 1) Adding an option to switch between the upstream toolkit and custom LibreOffice dialog, so people can still go back to using the custom LO dialog if they want to (as suggested by Stuart in comment 3). 2) Drop support for GTK and Qt color dialogs again. 3) Leave Qt color dialog in place (as it offers entering RGB, HSV, HTML color code and picking color from screen), but drop use of GTK one for now as it has fewer features. I'd clearly be in favour of 1). In case of 2) or 3), I think it would be good to have clear criteria of what a native color dialog would have to provide in order to be considered "suitable", i.e. it would be "dropping for now", with the possibility to re-enable in case those features are implemented in the upstream dialogs later. 2) would presumably also make it harder to implement tdf#130857 and thus fix tdf#141578 and other issues blocked by tdf#130857. At least last time I looked into it, trying to support the custom LO color dialog with custom Qt widgets resulted in issues that would need further analysis. -- You are receiving this mail because: You are on the CC list for the bug.
