Re : Re: KF6 meeting notes 2021-12-07
Le mercredi 8 décembre 2021 à 11:26 AM, David Redondo a écrit : > Am Dienstag, 7. Dezember 2021, 18:04:19 CET schrieb Volker Krause: > > > https://phabricator.kde.org/T11587 > > > > - there are bigger plans to rework color scheming, this needs more > > coordination with the effort to down-tier this for KF6 > > - would likely mean only storing the color scheme name in kdeglobals > > rather > > than actual colors > > I actually started a branch to use QSettings instead of KConfig for > KColorScheme with some changes to the public API that does this. > https://invent.kde.org/frameworks/kconfigwidgets/-/commits/work/davidre/ > qsettings/ > > > - do we need per color cascading or is that rather a bug? compare e.g. > > to > > Kate's syntax highlighting themes. > > This does away with per color cascading, and imo there's not much use > case for > it. When introducing the Header color set extra effort was taken to NOT > have > > cascading for those. Also Plasma will only allow creating full color > schemes > from the gui iirc. Cascading of color scheme doesn't really make sense and is actually causing problems with the Header when an application allows to overwrite the theme (e.g. neochat, elisa, ...) but the app theme used doesn't have a Header role defined, then you get a mix of two themes and it's a bit broken. There was an attempt to fix this here: https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/52
Re: KF6 meeting notes 2021-12-07
Am Dienstag, 7. Dezember 2021, 18:04:19 CET schrieb Volker Krause: https://phabricator.kde.org/T11587 - there are bigger plans to rework color scheming, this needs more coordination with the effort to down-tier this for KF6 - would likely mean only storing the color scheme name in kdeglobals rather than actual colors I actually started a branch to use QSettings instead of KConfig for KColorScheme with some changes to the public API that does this. https://invent.kde.org/frameworks/kconfigwidgets/-/commits/work/davidre/ qsettings/ - do we need per color cascading or is that rather a bug? compare e.g. to Kate's syntax highlighting themes. This does away with per color cascading, and imo there's not much use case for it. When introducing the Header color set extra effort was taken to NOT have cascading for those. Also Plasma will only allow creating full color schemes from the gui iirc. - should we just put this into KF::Config itself? The reason I did not finish this because I hit a stumbling block, that QSettings cannot deal with nested groups (see the latest few commits in the branch), so our current format '[Colors:Button][Inactive]' does not work which we should keep imo and we had to copy the group parsing from KConfig. So that might indeed make sense.
KF6 meeting notes 2021-12-07
https://mail.kde.org/pipermail/kde-frameworks-devel/2021-December/119935.html - tricky to find a mentor so far - good tasks become available after branching, but that might not happen in time https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/157 - merged - apply the same approach to all other frameworks where this is feasible https://phabricator.kde.org/T12166 - more research from Ahmad in the comments there https://phabricator.kde.org/T13806 - needs input from David F https://phabricator.kde.org/T11587 - there are bigger plans to rework color scheming, this needs more coordination with the effort to down-tier this for KF6 - would likely mean only storing the color scheme name in kdeglobals rather than actual colors - should we just put this into KF::Config itself? - do we need per color cascading or is that rather a bug? compare e.g. to Kate's syntax highlighting themes. - coordinate with Noah Davis, Nico will bring this up in the Plasma meeting https://phabricator.kde.org/T12208 - looks like a development tool mainly, is this even a blocker for KF6 given it's not exported and could be moved at any time? https://phabricator.kde.org/T12174 - KUrlRequester is often used for local file location and thus pulls in full KIO. - see e.g. KNotifyConfig - can probably be done later, unless there's a framework that depends on KIOWidgets just for this in its public link interface (seems unlikely) signature.asc Description: This is a digitally signed message part.
