<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - KDE5 VCL may require a little more cooking for wide consumption (at least on impress)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124044#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - KDE5 VCL may require a little more cooking for wide consumption (at least on impress)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124044">bug 124044</a> from <a class="email" href="mailto:m.weghorn@posteo.de" title="Michael Weghorn <m.weghorn@posteo.de>"> Michael Weghorn</a> <pre>Thank you for your reply. (In reply to sergio.callegari from <a href="show_bug.cgi?id=124044#c5">comment #5</a>) > In the meantime, there is something that is still not 100% clear to me. Is > the building of the gtk3_kde5 vcl plugin incompatible with that of the kde5 > vcl plugin in the LibO deb packages? No; it's possible to build (and package) all VCL plugins at the same time; it's just that the packages provided by TDF don't do so. > Would it be possible (and sensible) to ship both the gtk3_kde5 plugin and > the kde5 for the time being, so letting people on KDE plasma play with both > gtk3_kde5 and kde5 in view of the decision that might be taken at 6.2.5? It's possible, but currently not done for the TDF packages. I'd currently not add another VCL plugin for TDF's 6.2 builds. Since gtk3_kde5 is basically gtk3, with the difference that native kde5 file dialogs are used, using gtk3 would give you quite a good impression of gtk3_kde5 as well. > "In case it's decided to "disable" kde5 for 6.2, the easiest thing would > probably be to revert commit [3], resulting in kde5 not to be chosen > automatically any more, but the order on KDE Plasma and LXQt then becoming: > gtk3_kde5, kde4, gtk3, gtk, gen" > > from which it seems like either you have gtk3_kde5 or kde5 on the plugin > list. The list is used to decide which VCL plugin is used by default. The first one available will be used. In case the decision should be to switch back defaults, I'd personally go back to the state it was in before (which position should kde5 take otherwise?). kde5 could still be used by setting the environment variable.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>