btw with the migration to QtKeyChain and KWallet having org.freedesktop.secret support added, we should probably deprecate the KWallet API or at least make it a porting aid for KF6, since maintaining it for KF6 doesn't seem very viable

beat to me to it, haha

Done with https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/466

going back to this task, it probably makes sense to have native context in Kirigami, since it won't get plasma styling anyway *and* it's something that we want for desktop apps anyway. we could even have a Kirigami.Actions based API :V

quick note regarding inset: -1 was chosen for compatibility, but obv that won't matter for kf6 :)

Recently we migrated Koko away from hamburger menu, opting instead for a custom page.
This is an example of an advanced use case where we can't fit all actions in a nav bar.

Either that or simple statement (Maybe a quote from one our users?)

Recently there was a media outrage regarding win11 hardware requirement and how they leave many people in the dust, including 7th gen of intel processor which isn't that different from 8th gen and even leaves out some of Microsoft's hardware such as Surface Studio 2 (which they're still selling!)

ahh, alright thanks for explaining

tbh not a fan of that idea especially considering that we wanna minimize the amount of chrome at any given time

I thought the whole point of this is to use QPallete with above comment being more about that than the syntax

am I correct to assume that with this approach we would go from:

Good point, although we already have BasicPlasmoidHeading, which adds upon PlasmoidHeading

this has just landed 🎉

started work at https://invent.kde.org/graphics/koko/-/merge_requests/69 (nice)

bad example haha, I might actually work on this today, since it should be pretty simple (famous last words)

tbf feature wise koko already has most of the gwenview's features excluding some niche stuff like video support, so it's not like it can really get more complicated than it already is :P

reading over convo: I think we should use Twemoji, they are clearly more accurate
also imo round corners look on flags look really nice

I suppose that's an option too and probably good to do anyway, but then we have to wait until we can use Qt 6.3. We can have something similar and stable in PlasmaExtras now. If we want to make a list of Platform MenuItems for Kicker's actionLists, we'll have to write embedded QML in C++, which is annoying and sub-optimal even if doable.

Couldn't we potentially just mirror Platform Menu, so we'd still have stable API even if qt killed it? I know it's suboptimal but imo still better than creating another implementation altogether

added some applets that depend on this (wasn't really thorough) but it's pretty clear that this is a pretty important task