acheronuk | @VikingRedwolf there is some active development on qtcurve now it's officially a kde project | 09:22 |
---|---|---|
acheronuk | with a 1.9 RC https://cgit.kde.org/qtcurve.git/ | 09:22 |
lubot1 | <VikingRedwolf> ahh that's good news | 09:22 |
lubot1 | <VikingRedwolf> I really need help on that. theming lxqt is a pain in the arsse | 09:22 |
acheronuk | so maybe a pretty please to KDE devs on some way to set theming for lxqt? | 09:23 |
lubot1 | <VikingRedwolf> I downloaded tonez! of documentation with no luck | 09:24 |
lubot1 | <VikingRedwolf> maybe cooperating with KDE team will be nice for Lubuntu Next | 09:24 |
acheronuk | imposing a per user pre-done config via /etc/skel would work, but it is an ugly way. and hard to restore if a user decides to delete the config | 09:24 |
acheronuk | yes, worth asking | 09:24 |
lubot1 | <VikingRedwolf> yup | 09:25 |
lubot1 | <VikingRedwolf> the problem is, without some kde packages, LXQt is unable to install new themes. or use them. that's a problem. for me, at least | 09:25 |
acheronuk | yes. I have on a couple of occasions look to see if you could run the qtcurve config dialogue without systemsettings (or the kcmshell backend it uses), but seems it is tied in to being a KDE thing | 09:27 |
lubot1 | <VikingRedwolf> aye. you can't. also, the theme selector only reads the pre-installed widget themes. and now I have no bloody idea where to add LX widgets themes or QTCurve ones | 09:28 |
acheronuk | decoupling that could be trivial, or could be very hard. my coding is not good enough to tell | 09:28 |
lubot1 | <VikingRedwolf> but I'd include qtcurve in Lubuntu if that let users to change the theme or add one, the same way gtk does (/.themes) | 09:29 |
acheronuk | kde-style-breeze: /usr/share/QtCurve/Breeze.qtcurve | 09:31 |
acheronuk | so in that folder ? | 09:31 |
lubot1 | <VikingRedwolf> so I drop mytheme.qtcurve there? | 09:32 |
acheronuk | I use qtcurve in KDE and my config sees breeze qtcurve theme installed by kde-style-breeze package | 09:32 |
acheronuk | I assume so. | 09:33 |
lubot1 | <VikingRedwolf> the problem will be the selector then | 09:33 |
acheronuk | if there is extra magic required to make qtcureve see it, I'm not sure what | 09:33 |
lubot1 | <VikingRedwolf> and LXQt is like an "eroded" KDE desktop | 09:34 |
lubot1 | <VikingRedwolf> it lacks some things it might need | 09:34 |
acheronuk | indeed. | 09:34 |
lubot1 | <VikingRedwolf> :( | 09:34 |
acheronuk | I had a look, but could not work out if there was a way of specifying a global default theme for qtcurve | 09:35 |
acheronuk | i.e. something you could install with a lubuntu-settings package in a system dir | 09:35 |
acheronuk | adding *that* may be an eaier ask of KDE devs? | 09:36 |
lubot1 | <VikingRedwolf> I tried lots of things. I'd like to use my customised colour scheme (lubuntu.qtcurve) and make it active on first boot / ubiquity | 09:36 |
acheronuk | so you set a default? then if users change it, then up to them? | 09:36 |
acheronuk | sure something can be worked out. just not obvious right this sec | 09:37 |
lubot1 | <VikingRedwolf> I know :( | 09:37 |
lubot1 | <VikingRedwolf> I'll read MO documentation on Git. thanks for the link anyways :) | 09:38 |
redwolf | tsimonq2, Tiberio! | 18:26 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!