Re: Remove/ Archive Obsolete or Disabled Bugzilla Product/Components
Hi Ben, Nate suggested on matrix that we can move inactive components to a "Archived" project. This way they will not be visible under original project. Also is it possible to move the inactive projects further down the list. Regards, Shubham Sent with Proton Mail secure email. On Monday, December 18th, 2023 at 12:12 PM, Ben Cooksley wrote: > On Mon, Dec 18, 2023 at 7:21 PM Shubham Arora > wrote: > > > Hi Ben, > > > > Thanks for the response. I will move the conversation to plasma-devel for > > disabling the components. > > > > Can we archive the already disabled components? For example kinfocenter > > product has only 1 active component and around 8 inactive. These components > > are extraneous and just add to the clutter when browsing. > > > Unfortunately Bugzilla has no such "archival" functionality - so the extent > that things are disabled is as good as it gets i'm afraid. > > Cheers, > Ben > > > > > Sent with Proton Mail secure email. > > > > On Monday, December 18th, 2023 at 10:51 AM, Ben Cooksley > > wrote: > > > > > > > On Mon, Dec 18, 2023 at 8:16 AM Shubham Arora > > > wrote: > > > > > > > Hi, > > > > > > > > > HI Shubham, > > > > > > > > > > > I have compiled a list of all bugzilla components and products that > > > > need to be archived or removed to remove some clutter from the bugzilla > > > > interface. > > > > > > > > All inactive components can be archived as they are no longer in use. > > > > Following components can probably be disabled and archived. > > > > > > > > Product ID Product Name Product Description Component ID Component Name > > > > Component Description > > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 341 general > > > > all bugs not for other components > > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1131 ksysguard > > > > The ksysguard standalone windowed application > > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1130 > > > > ksysguardd The cli daemon process > > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 2438 > > > > libksysguard ksysguard library > > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1129 Plasmoid > > > > / Applet The applet -- not the windowed ksysguard. > > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1132 Process > > > > Controller - krunner part The process controller widget > > > > 359 buildsystem Report issues with the buildsystem here. 981 KDE4 > > > > (cmake) Report issues with the KDE4 buildsystem (cmake). For reporting > > > > issues with cmake itself use the cmake bugtracker: > > > > http://www.cmake.org/Bug > > > > 392 Oxygen A breath of fresh air. It includes a new icon set, sounds, a > > > > new widget style and a new window decoration. The oxygen artists also > > > > provide various artwork for applications (like backgrounds etc) 1795 > > > > gtk2-engine The GTK+-2.0 implementation of the widget style > > > > 344 systemsettings Plasma's configuration tool 2414 kcm_formats The > > > > formats module in Plasma 5.25 and earlier. Do not file bugs here if you > > > > are using Plasma 5.26 or later! > > > > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. > > > > 2425 gtk2 Bugs specific to the GTK+ 2 version. > > > > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. > > > > 2427 qt4 Bugs specific to the Qt 4 version. > > > > > > > > I used this script to generate the list. > > > > https://invent.kde.org/-/snippets/2943 > > > > > > > > Sysadmin intervention is required here as not to generate any emails > > > > for any existing bugs under the above components/products. > > > > > > > > > Components and products can be disabled/archived for new bug entry > > > without affecting existing bugs. > > > This therefore just needs someone with sufficient access (edit_components > > > rights) to do - should disabling the above be seen as appropriate by the > > > component maintainers. > > > > > > Given many of these are Plasma related, probably best to discuss this on > > > plasma-de...@kde.org. > > > > > > > > > > > Regards, > > > > > > > Shubham > > > > > > > > > Cheers, > > > Ben > > > > > > > Sent with Proton Mail secure email.
Re: Remove/ Archive Obsolete or Disabled Bugzilla Product/Components
On Mon, Dec 18, 2023 at 7:21 PM Shubham Arora wrote: > Hi Ben, > > Thanks for the response. I will move the conversation to plasma-devel for > disabling the components. > > Can we archive the already disabled components? For example kinfocenter > product has only 1 active component and around 8 inactive. These components > are extraneous and just add to the clutter when browsing. > Unfortunately Bugzilla has no such "archival" functionality - so the extent that things are disabled is as good as it gets i'm afraid. Cheers, Ben > > Sent with Proton Mail secure email. > > On Monday, December 18th, 2023 at 10:51 AM, Ben Cooksley < > bcooks...@kde.org> wrote: > > > > On Mon, Dec 18, 2023 at 8:16 AM Shubham Arora < > shubhamar...@protonmail.com> wrote: > > > > > Hi, > > > > > > HI Shubham, > > > > > > > > I have compiled a list of all bugzilla components and products that > need to be archived or removed to remove some clutter from the bugzilla > interface. > > > > > > All inactive components can be archived as they are no longer in use. > Following components can probably be disabled and archived. > > > > > > Product ID Product Name Product Description Component ID Component > Name Component Description > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 341 general > all bugs not for other components > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1131 > ksysguard The ksysguard standalone windowed application > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1130 > ksysguardd The cli daemon process > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 2438 > libksysguard ksysguard library > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1129 Plasmoid > / Applet The applet -- not the windowed ksysguard. > > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1132 Process > Controller - krunner part The process controller widget > > > 359 buildsystem Report issues with the buildsystem here. 981 KDE4 > (cmake) Report issues with the KDE4 buildsystem (cmake). For reporting > issues with cmake itself use the cmake bugtracker: > http://www.cmake.org/Bug > > > 392 Oxygen A breath of fresh air. It includes a new icon set, sounds, > a new widget style and a new window decoration. The oxygen artists also > provide various artwork for applications (like backgrounds etc) 1795 > gtk2-engine The GTK+-2.0 implementation of the widget style > > > 344 systemsettings Plasma's configuration tool 2414 kcm_formats The > formats module in Plasma 5.25 and earlier. Do not file bugs here if you are > using Plasma 5.26 or later! > > > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. > 2425 gtk2 Bugs specific to the GTK+ 2 version. > > > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. > 2427 qt4 Bugs specific to the Qt 4 version. > > > > > > I used this script to generate the list. > https://invent.kde.org/-/snippets/2943 > > > > > > Sysadmin intervention is required here as not to generate any emails > for any existing bugs under the above components/products. > > > > > > Components and products can be disabled/archived for new bug entry > without affecting existing bugs. > > This therefore just needs someone with sufficient access > (edit_components rights) to do - should disabling the above be seen as > appropriate by the component maintainers. > > > > Given many of these are Plasma related, probably best to discuss this on > plasma-de...@kde.org. > > > > > > > > Regards, > > > > > Shubham > > > > > > Cheers, > > Ben > > > > > Sent with Proton Mail secure email. >
Re: Remove/ Archive Obsolete or Disabled Bugzilla Product/Components
Hi Ben, Thanks for the response. I will move the conversation to plasma-devel for disabling the components. Can we archive the already disabled components? For example kinfocenter product has only 1 active component and around 8 inactive. These components are extraneous and just add to the clutter when browsing. Sent with Proton Mail secure email. On Monday, December 18th, 2023 at 10:51 AM, Ben Cooksley wrote: > On Mon, Dec 18, 2023 at 8:16 AM Shubham Arora > wrote: > > > Hi, > > > HI Shubham, > > > > > I have compiled a list of all bugzilla components and products that need to > > be archived or removed to remove some clutter from the bugzilla interface. > > > > All inactive components can be archived as they are no longer in use. > > Following components can probably be disabled and archived. > > > > Product ID Product Name Product Description Component ID Component Name > > Component Description > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 341 general all > > bugs not for other components > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1131 ksysguard The > > ksysguard standalone windowed application > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1130 ksysguardd > > The cli daemon process > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 2438 libksysguard > > ksysguard library > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1129 Plasmoid / > > Applet The applet -- not the windowed ksysguard. > > 189 ksysguard System monitoring tool [up to Plasma 5.21] 1132 Process > > Controller - krunner part The process controller widget > > 359 buildsystem Report issues with the buildsystem here. 981 KDE4 (cmake) > > Report issues with the KDE4 buildsystem (cmake). For reporting issues with > > cmake itself use the cmake bugtracker: http://www.cmake.org/Bug > > 392 Oxygen A breath of fresh air. It includes a new icon set, sounds, a new > > widget style and a new window decoration. The oxygen artists also provide > > various artwork for applications (like backgrounds etc) 1795 gtk2-engine > > The GTK+-2.0 implementation of the widget style > > 344 systemsettings Plasma's configuration tool 2414 kcm_formats The formats > > module in Plasma 5.25 and earlier. Do not file bugs here if you are using > > Plasma 5.26 or later! > > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. 2425 > > gtk2 Bugs specific to the GTK+ 2 version. > > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. 2427 > > qt4 Bugs specific to the Qt 4 version. > > > > I used this script to generate the list. > > https://invent.kde.org/-/snippets/2943 > > > > Sysadmin intervention is required here as not to generate any emails for > > any existing bugs under the above components/products. > > > Components and products can be disabled/archived for new bug entry without > affecting existing bugs. > This therefore just needs someone with sufficient access (edit_components > rights) to do - should disabling the above be seen as appropriate by the > component maintainers. > > Given many of these are Plasma related, probably best to discuss this on > plasma-de...@kde.org. > > > > > Regards, > > > Shubham > > > Cheers, > Ben > > > Sent with Proton Mail secure email.
Re: Remove/ Archive Obsolete or Disabled Bugzilla Product/Components
On Mon, Dec 18, 2023 at 8:16 AM Shubham Arora wrote: > Hi, > HI Shubham, > > I have compiled a list of all bugzilla components and products that need > to be archived or removed to remove some clutter from the bugzilla > interface. > > All inactive components can be archived as they are no longer in use. > Following components can probably be disabled and archived. > > Product ID Product NameProduct Description Component ID > Component Name Component Description > 189 ksysguard System monitoring tool [up to Plasma 5.21] > 341 general all bugs not for other components > 189 ksysguard System monitoring tool [up to Plasma 5.21] > 1131ksysguard The ksysguard standalone windowed application > 189 ksysguard System monitoring tool [up to Plasma 5.21] > 1130ksysguardd The cli daemon process > 189 ksysguard System monitoring tool [up to Plasma 5.21] > 2438libksysguardksysguard library > 189 ksysguard System monitoring tool [up to Plasma 5.21] > 1129Plasmoid / Applet The applet -- not the windowed ksysguard. > 189 ksysguard System monitoring tool [up to Plasma 5.21] > 1132Process Controller - krunner part The process controller > widget > 359 buildsystem Report issues with the buildsystem here. > 981 KDE4 (cmake)Report issues with the KDE4 buildsystem (cmake). > For reporting issues with cmake itself use the cmake bugtracker: > http://www.cmake.org/Bug > 392 Oxygen A breath of fresh air. It includes a new icon set, sounds, > a new widget style and a new window decoration. The oxygen artists also > provide various artwork for applications (like backgrounds etc) 1795 > gtk2-engine The GTK+-2.0 implementation of the widget style > 344 systemsettings Plasma's configuration tool 2414 > kcm_formats The formats module in Plasma 5.25 and earlier. Do not file > bugs here if you are using Plasma 5.26 or later! > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. > 2425gtk2Bugs specific to the GTK+ 2 version. > 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. > 2427qt4 Bugs specific to the Qt 4 version. > > I used this script to generate the list. > https://invent.kde.org/-/snippets/2943 > > Sysadmin intervention is required here as not to generate any emails for > any existing bugs under the above components/products. > Components and products can be disabled/archived for new bug entry without affecting existing bugs. This therefore just needs someone with sufficient access (edit_components rights) to do - should disabling the above be seen as appropriate by the component maintainers. Given many of these are Plasma related, probably best to discuss this on plasma-de...@kde.org. > > Regards, Shubham > > Cheers, Ben > Sent with Proton Mail secure email. >
Re: Kandalf: request for review
I like that. The k makes sense there. It also fits with the theme of the target uses. JV On Sun, Dec 17, 2023, 10:54 AM Martin Koller wrote: > On Freitag, 15. Dezember 2023 00:29:19 CET Justin Zobel wrote: > > I'm a fan of K when it's used well e.g. Kalendar or Kontact but not > KMyApp > > "Kamel" (german for camel) which is a kind of Lama > > -- > Best regards/Schöne Grüße > > Martin > A: Because it breaks the logical sequence of discussion > Q: Why is top posting bad? > > () ascii ribbon campaign - against html e-mail > /\- against proprietary attachments > > Frühstück, Geschenkideen, Accessoires, Kulinarisches: www.lillehus.at > > >
Remove/ Archive Obsolete or Disabled Bugzilla Product/Components
Hi, I have compiled a list of all bugzilla components and products that need to be archived or removed to remove some clutter from the bugzilla interface. All inactive components can be archived as they are no longer in use. Following components can probably be disabled and archived. Product ID Product NameProduct Description Component ID Component Name Component Description 189 ksysguard System monitoring tool [up to Plasma 5.21] 341 general all bugs not for other components 189 ksysguard System monitoring tool [up to Plasma 5.21] 1131 ksysguard The ksysguard standalone windowed application 189 ksysguard System monitoring tool [up to Plasma 5.21] 1130 ksysguardd The cli daemon process 189 ksysguard System monitoring tool [up to Plasma 5.21] 2438 libksysguardksysguard library 189 ksysguard System monitoring tool [up to Plasma 5.21] 1129 Plasmoid / Applet The applet -- not the windowed ksysguard. 189 ksysguard System monitoring tool [up to Plasma 5.21] 1132 Process Controller - krunner part The process controller widget 359 buildsystem Report issues with the buildsystem here.981 KDE4 (cmake)Report issues with the KDE4 buildsystem (cmake). For reporting issues with cmake itself use the cmake bugtracker: http://www.cmake.org/Bug 392 Oxygen A breath of fresh air. It includes a new icon set, sounds, a new widget style and a new window decoration. The oxygen artists also provide various artwork for applications (like backgrounds etc) 1795 gtk2-engine The GTK+-2.0 implementation of the widget style 344 systemsettings Plasma's configuration tool 2414kcm_formats The formats module in Plasma 5.25 and earlier. Do not file bugs here if you are using Plasma 5.26 or later! 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. 2425 gtk2Bugs specific to the GTK+ 2 version. 643 QtCurve The QtCurve style engine for Qt and other GUI toolkits. 2427 qt4 Bugs specific to the Qt 4 version. I used this script to generate the list. https://invent.kde.org/-/snippets/2943 Sysadmin intervention is required here as not to generate any emails for any existing bugs under the above components/products. Regards, Shubham Sent with Proton Mail secure email.
Re: Kandalf: request for review
On Freitag, 15. Dezember 2023 00:29:19 CET Justin Zobel wrote: > I'm a fan of K when it's used well e.g. Kalendar or Kontact but not KMyApp "Kamel" (german for camel) which is a kind of Lama -- Best regards/Schöne Grüße Martin A: Because it breaks the logical sequence of discussion Q: Why is top posting bad? () ascii ribbon campaign - against html e-mail /\- against proprietary attachments Frühstück, Geschenkideen, Accessoires, Kulinarisches: www.lillehus.at
Re: Spacing in our apps
On Sonntag, 17. Dezember 2023 13:21:32 CET Carl Schwan wrote: > a) Remove smallSpacing and largeSpacing from Kirigami, and rename > mediumSpacing to just spacing. This unified spacing value would be defined > in qqc2-desktop-style to use whatever value is defined in the current > QStyle. > > a bis) Instead of creating only a generic "spacing" property, we create a > "Kirigami.Units.margins" or "Kirigami.Units.paddings" property to use for > paddings of QtQuick Controls and mapped to the Layout*Margin pixel metrics > and a "Kirigami.Units.spacing" property mapped to the Layout*Spacing pixel > metrics. For Breeze and Oxygen, both value would map to 6 pixels anyway, > but it might make it easier to switch to other values in the future as well > as make the usage of Units value more explit. +1 for getting rid of choices because it makes my life easier if I don't have to think about which value is the correct one in some situation. I don't have an opinion on a bis), but I guess it makes sense to mirror the QWidget pixel metrics in QML. Regards, Ingo signature.asc Description: This is a digitally signed message part.
Spacing in our apps
Hi,
I'm been trying to unify a bit the usage of spacing in our apps and I'm
noticing a difference between how we do it in QWidgets apps and QML apps.
In QtWidgets apps, we use
- pixelMetric(QStyle::PM_Layout{Left,Right,Top,Bottom}Margin) for the margins
- pixelMetric(QStyle::PM_Layout{Vertical,Horizontal}Margin) for the spacing
between items in layout
In practice all these pixel metrics are equal to 6 pixels with Fusion, Oxygen
and Breeze. These means that in some cases, some apps are even hardcoding
these values in their .ui files, which is bad and we should try to avoid this.
In Kirigami apps, we use:
- Kirigami.Units.smallSpacing = 4 pixels
- Kirigami.Units.mediumSpacing = 6 pixels
- Kirigami.Units.largeSpacing = 8 pixels
In most cases, smallSpacing and largeSpacing are used as mediumSpacing was
introduced later on, so it doesn't match the values from QtWidgets apps. Worse
we don't really have clear guidelines when to use small or large spacing, so
it's mostly done arbitrarely and not consistantly :(
Also having 3 different Kirigami.Units.*Spacing values that are each only 2
pixels appart doesn't sounds like a great idea as it's hard to see a
difference between these values taken side by side.
I see three ways to move forward with this issue:
a) Remove smallSpacing and largeSpacing from Kirigami, and rename
mediumSpacing to just spacing. This unified spacing value would be defined in
qqc2-desktop-style to use whatever value is defined in the current QStyle.
a bis) Instead of creating only a generic "spacing" property, we create a
"Kirigami.Units.margins" or "Kirigami.Units.paddings" property to use for
paddings of QtQuick Controls and mapped to the Layout*Margin pixel metrics and
a "Kirigami.Units.spacing" property mapped to the Layout*Spacing pixel
metrics. For Breeze and Oxygen, both value would map to 6 pixels anyway, but
it might make it easier to switch to other values in the future as well as
make the usage of Units value more explit.
b) Use 4 pixels as standard spacing in our QtWidgets apps and add a "margins"
and "largeMargin" helper methods in KWidgetsAddons or QStyle similar to this
QMargins QStyle::largeMargins() const
{
return QMargins{
pixelMetric(QStyle::PM_LayoutLeftMargin),
pixelMetric(QStyle::PM_LayoutTopMargin),
pixelMetric(QStyle::PM_LayoutRightMargin),
pixelMetric(QStyle::PM_LayoutBottomMargin)
}
}
QMargins QStyle::largeMargins() const
{
return QMargins{
pixelMetric(QStyle::PM_LayoutLeftMargin) * 2,
pixelMetric(QStyle::PM_LayoutTopMargin) * 2,
pixelMetric(QStyle::PM_LayoutRightMargin) * 2,
pixelMetric(QStyle::PM_LayoutBottomMargin) * 2
}
}
then we can remove mediumSpacing from Kirigami and ensure that in both our
Kirigami and QtWidgets apps, we use small or large only no spacing at all. We
should still try to define some guidelines when to use large or small spacing.
c) Do nothing and accept that spacing in Kirigami apps and QtWidgets are
different. We might still want to define in our doc/hig the usecase for
largeSpacing and smallSpacing
Personally I see advantages and disadvantages for all these solutions. I had a
preference on b) but while writing this mail I'm slowly liking the a bis) idea
more and more as we might not need a small spacing and large spacing and could
get away with just one unified spacing.
Cheers,
Carl
