https://bugs.documentfoundation.org/show_bug.cgi?id=164656
--- Comment #6 from Michael Weghorn <[email protected]> --- (In reply to Eyal Rozenberg from comment #5) > (In reply to Michael Weghorn from comment #1) > > In case of MS Windows, I can generally think of 2 potential options: > > > > 1) work on Qt welding on Windows > > 2) work on welding using native Windows widgets > > Speaking as a non-GUI-developer and non-LO-developer... Why is option (1.) > relevant? Don't we already have a Qt backend? Which uses the same widgets > that would be used here? The Qt VCL plugins on Linux currently mostly use VCL widgets (i.e. widgets from LO's own UI toolkit), just draw them to look mostly like "real" Qt widgets. Using actual Qt widgets is still work in progress, see tdf#130857. That work could in theory be done on any platform if Qt was used by LO on that platform. So it is true that if this gets implemented on Linux, implementing the use of native widgets wouldn't have to be done again for each widget type on Windows. However, LO on Windows currently doesn't use Qt, so adding support for using Qt on Windows inside LO would still be a prerequisite *if* going/evaluating that route (s. WIP branch from jmux mentioned in my comment 1). -- You are receiving this mail because: You are the assignee for the bug.
