- User Since
- Apr 15 2015, 5:07 PM (248 w, 4 d)
Sat, Jan 18
Sat, Jan 11
Tue, Jan 7
Mon, Jan 6
The VDG channel somehow ended up liking "Yoto" a lot!
That's good with me, the rest of the patch is good and much appreciated.
Maybe there's a third option: Another precedent we already have is the circular carve-out we use for the notification number badge. Perhaps we could reuse that for the indicator.
I'm still not a big fan of the Glow for a number of reasons:
Sun, Jan 5
Sat, Jan 4
I love it.
Since we have consensus, let's expand the clipart page? :)
@chwmpfling Definitely the plan! Will appreciate your review
Fri, Jan 3
We can revisit it after some more discussion.
I don't agree with this patch. Hiding a place or section from the Places panel doesn't mean the user didn't add it and it's not to be used. We don't hide it from Folder View's config or relative title generator either. Hidden is not removed. Please revert.
It should be iconName after label.
Thu, Jan 2
Sat, Dec 28
It's definitely a discussion I'd enjoy more :)
Ah sorry, I had a reply typed into the text field but must have botched hitting Submit.
Thu, Dec 26
This is also possible in all of the other menus based on the backend, so that's sensible, yeah.
Tue, Dec 24
Mon, Dec 23
Some notes while I start working on implementation:
Sun, Dec 22
The return QString() shouldn't be necessary if we just fall through to the final return.
Dec 18 2019
Dec 17 2019
Just as a sanity check: libtm knows the pid for a window. Have you checked if there might be a faster way of doing this by checking if the stream pid is among its children?
Ah right, I didn't look at the code context and forgot we don't just load the custom pixmap in the same function body but also in Private::icon. But we also do this there:
If the concern is that QIcon::name isn't good enough but we actually have an icon inside, why don't we just change the check to QIcon::isNull?
Dec 15 2019
Dec 12 2019
Let's go for it, it's fairly in line with the TM applet refectoring we planned in Valencia at the end of the day
Good one, thanks!
Dec 10 2019
Dec 8 2019
No, Recently Used works via KActivitiesStats.
Dec 5 2019
I don't really understand why the panel being bare by default is a problem. Isn't it nicer when users don't have to opt out of clutter like this?
In the discussion you said you don't read the Planet, but when you were pointed at this post it lead you to complain about politics on the Planet, so the post seems relevant and this solution doesn't address the cause for us discussing it. That seems like a broken solution so between this and the other stuff I would say -1 as it seems like even with the solution you'd be likely to complain about community consensus again.
We currently have two proposals for how to implement your filter proposal:
I'm not calling anyone bad for having differing opinions to mine, I am calling out that it's bad to go against community consensus without respecting it and acting accordingly. Restarting a debate without bringing something new to the table was bad. My own individual opinion doesn't matter - that's in fact the point. I'm not sure why this is so hard to understand.
I think goes a bit against the code of conduct.
I'm not in favor of implementing content scanning and profiling based on keywords on the Planet.
I don't know how such a filter could work in practice. There's no consensus on when a political topic is a KDE matter or not, as we e.g. saw in the climate change debate recently. As an international community that heavily relies on free traversal of borders many political issues are in our scope, too. Then there's patents, privacy which is a community goal(!), ... And Planet KDE is explicitly not a project news feed - the description of the planet says it's for personal blogs - so a filter based on whether a post is about a project or not would seem go go along its nature. Plus the e.V. and community matters are also "projects" in some sense.
This ticket is for making the existing rules more visible, not a filter mechanism, though.
Dec 4 2019
I plan to put time into implementing the mockup this month with the above feature/change list.