Re: Review Request: Rework layout of widget explorer and activity manager in vertical mode

are still cropped and look pretty much the same to me. And actually fixing them (e.g. by line-wrapping instead of cropping since there usually is enough space for an extra line) would be quite important. Other than that it looks fine to me and definitely like an improvement. - Thomas Pfeiffer

Re: Review Request: Humble attempt to improve the ScreenSaver KCM

> On Oct. 8, 2012, 5:31 p.m., Martin Gräßlin wrote: > > just an idea: what about hiding the whole X screen saver stuff behind > > another configure dialog. Looking at the screenshot I find the design puts > > emphasis on the wrong part: what we want to remove takes more than 50 % of > > the av

Which settings should go in the settings dialog of a Plasmoid?

Hi Plasma and KDE Usability teams, the KDE Telepathy team is currently facing a decision which I think calls for being put into a broader context: Which settings should go in a settings dialog of a Plasmoid? Of course we have the Plasmoid-specific settings Keyboard Shortcut, Share and maybe some

Re: GSOC Project Proposal Draft :: Improvement and Enhancements for Plasma Media Center

On Sunday 14 April 2013 23:33:25 Sinny Kumari wrote: If you'd like, I can co-mentor this project from the usability perspective, especially regarding use in Plasma Active. Cheers, Thomas ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.k

Re: Which settings should go in the settings dialog of a Plasmoid?

On Sunday 14 April 2013 13:58:50 Aaron J. Seigo wrote: > On Saturday, April 13, 2013 15:00:21 David Edmundson wrote: > > I think the clock example is going to be even more confusing if we > > have both your system time zone and settings for which time zone are > > shown in the plasmoid both togethe

Re: Review Request 110122: Patch to handle notifications with low timeouts masking earlier important notifications.

> On April 25, 2013, 2:02 p.m., Aaron J. Seigo wrote: > > plasma/generic/applets/notifications/contents/ui/LastNotificationPopup.qml, > > line 52 > > > > > > no minimum is set here as there was in the prior code.

Re: Review Request 110122: Patch to handle notifications with low timeouts masking earlier important notifications.

0 second maximum though, it just > means I'll never be able to use KDE and have a non-angry boss at the same > time :P > > Thomas Pfeiffer wrote: > If an information is so important that you must not miss it, it should > not be displayed as a notification (or at le

Re: Review Request 110122: Patch to handle notifications with low timeouts masking earlier important notifications.

0 second maximum though, it just > means I'll never be able to use KDE and have a non-angry boss at the same > time :P > > Thomas Pfeiffer wrote: > If an information is so important that you must not miss it, it should > not be displayed as a notification (or at le

Re: Review Request 110389: Add "Configure" button to notifications that opens KNotify settings for the app that emitted the notification

> On May 12, 2013, 2:11 p.m., Heiko Tietze wrote: > > Nice feature, if it works overall. Is there a question for usability except > > the fact that we need guidelines on notification along with its > > configuration in general? Oh, yes guidelines, we indeed need them! Would you like to help? T

Re: Review Request 110389: Add "Configure" button to notifications that opens KNotify settings for the app that emitted the notification

> On May 14, 2013, 6:46 p.m., Aaron J. Seigo wrote: > > code looks fine, the feature i think will be welcome by many. > > > > my only concern is how usable this will be on touch. (probably not very.) > > for Plasma Active 4 this is not a problem as it is using 4.10. We'll need > > to revisit t

Re: Switches around the world and broken metaphors [Was: Battery Monitor revamp]

On Sunday 26 May 2013 00:05:56 Marco Martin wrote: > On Saturday 25 May 2013 14:32:29 Martin Graesslin wrote: > > > And this is clearly the case let's work around something we don't want > > > to > > > fix. Switches are a clear improvement over checkboxes depending on the > > > context even my 60yo

Re: Switches around the world and broken metaphors [Was: Battery Monitor revamp]

On Sunday 26 May 2013 18:35:20 Martin Graesslin wrote: > > So if ambiguity is the only reason against using switches on Desktop, we > > should use them. > > At least for me there is another reason: given the way how the switch > component is designed (again no matter which one) I am inclined to dr

Re: [RFC] Moving Wishlist Items to Brainstorm

On 27.05.2013 14:03, Martin Graesslin wrote: On Monday 27 May 2013 13:25:35 Mario Fux KDE ML wrote: Do you plan as well to remove the option to send "bugs" with severity "wishlist" on bugs.kde.org (and probably just leave it for some brainstorm moderators). Would be two steps less for "wishlist

Re: [RFC] Moving Wishlist Items to Brainstorm

On 27.05.2013 23:44, Luiz Romário Santana Rios wrote: 2013/5/27 Thomas Pfeiffer : On the other hand, consistency would be very useful here. It would get quite confusing for users if they had to know for each project whether it accepts wishlist items on bugzilla or on brainstorm. If all of KDE

Re: [RFC] Moving Wishlist Items to Brainstorm

On 28.05.2013 14:17, Luiz Romário Santana Rios wrote: 2013/5/28 Thomas Pfeiffer : If developers start actively searching for very specific brainstorm topics, the whole point of moving there would be moot. The goal is that the forum does the filtering and developers only have to look at the most

Re: Battery Monitor revamp

On 28.05.2013 12:04, Àlex Fiestas wrote: For what is worth (and from the Solid side of things). Batteries have improved a lot since last time we discussed this issue, back on the days a high CPU round of 10min would drain huge percentage of the power in your battery, hence the estimation was rea

Re: [kde-artists] New start sound - Discussion.

On Saturday 11 May 2013 13:03:46 Christoph Feck wrote: > On Friday 10 May 2013 21:26:26 Ernesto Manríquez wrote: > > Greetings to all. > > > > I worked in a start sound for KDE, and I have a preliminar version > > here. > > Users can still use Login/Logout sounds, but they are disabled by > defau

Re: [kde-artists] New start sound - Discussion.

On Thursday 30 May 2013 13:10:50 Aaron J. Seigo wrote: > On Thursday, May 30, 2013 09:13:37 Thomas Pfeiffer wrote: > > I don't think it's a good idea to disable login sounds. > > Sure, they have no practical use, but they are a very important part of >

Re: [kde-artists] New start sound - Discussion.

On Thursday 30 May 2013 22:46:05 Aaron J. Seigo wrote: > On Thursday, May 30, 2013 16:00:14 Thomas Pfeiffer wrote: > > On Thursday 30 May 2013 13:10:50 Aaron J. Seigo wrote: > > > On Thursday, May 30, 2013 09:13:37 Thomas Pfeiffer wrote: > > > * It often starts at an un

Re: naming the next major release

On 20.08.2013 07:06, Martin Graesslin wrote: I do want to promote KWin for the usage in LXDE/Razor as in the next version we will hardly have any build-time dependencies from frameworks higher than tier1. I'm concerned that a generic name "Plasma" would work against that as it would be difficult

Re: naming the next major release

On 19.08.2013 21:56, Aaron J. Seigo wrote: Hi... after seeing the Nth time that we don’t know if the next release will be called Plasma Workspaces 2 or something else, i’d like to find consensus on this point so we can move forward in communication with confidence. the first point that we’ve al

Re: KDE framework 5 - a humble idea

or, best, by someone scratching their own itch. > > Reading the scenarios made me realise that I personally would prefer to have > this on our wiki at community.kde.org/Plasma. There's matching information > already there. Maybe it could be moved next to it and be refined from &

Re: Plasma Next Naming

On Saturday 18 January 2014 15:53:16 Mark Gaiser wrote: > I don't see anything wrong with naming the next plasma as just "Plasma > 2". and subsequent releases should follow the name: "Plasma > 2." so "Plasma 2.1". There is nothing wrong with that. It > works for tons of software out there includin

When should there be a screen brightness OSD?

On Saturday 18 January 2014 13:15:18 Martin Klapetek wrote: > > > Truth is you don't need to know the /exact/ brightness or volume level > > > in > > > fullscreen video, you simply fiddle with it until it suits you. In this > > > case it's maybe not as much about showing the exact percentage, but

Re: When should there be a screen brightness OSD?

On Tuesday 21 January 2014 22:45:44 Kai Uwe Broulik wrote: > Hi, > > +1 as well! > Especially it popping up on session start where the compositor isn't fully > ready. :/ > > So to summarize: > - never ever show it when the brightness changes automatically (session > start, mouse movement, screen

Re: Animation durations

On 03.02.2014 00:50, Vishesh Handa wrote: On Sunday 02 February 2014 16:59:00 Marco Martin wrote: i'm not sure if configurability is a good idea at all. Could you please elaborate on rationale behind this? Is it just technical? the only this that should be configurable is the possibility to

Re: Minutes Monday Plasma hangout

On 03.02.2014 13:47, Martin Gräßlin wrote: On Monday 03 February 2014 13:31:55 Sebastian Kügler wrote: Plasma Meeting February, 3rd, 2014 Present: David Edmundson, Marco Martin, Martin Gräßlin, Sebastian Kügler sebas: - sebas/themeswitch branch allows switching themes, almost good to merge:

Re: Date in digital-clock?

On Thursday 06 February 2014 08:16:43 Kai Uwe Broulik wrote: > Hi, > > The current way it is in plasma-desktop is broken imho, as Martin already > pointed out. But I think we should not drop that feature. +1, I don't think we should drop it. > My proposal would be a simple checkbox which gives y

Re: Date in digital-clock?

On Thursday 06 February 2014 14:30:11 John Layt wrote: > On Thursday 06 Feb 2014 01:39:33 Martin Klapetek wrote: > > Hey, > > > > what's the plan of getting the date back to the digital clock applet? Do > > we > > want that? Do we not? Should it go again under the clock (making it really > > tiny

Re: Date in digital-clock?

On Thursday 06 February 2014 15:12:28 Marco Martin wrote: > On Thursday 06 February 2014 14:56:42 Thomas Pfeiffer wrote: > > If the configuration freaks then say "It's too complicated to replace the > > default Plasmoid", we can tell them "You want flexibility

Re: plasma workspace integration for akonadi

On Saturday 08 February 2014 06:46:35 Martin Klapetek wrote: > On Sat, Feb 8, 2014 at 6:38 AM, Heena Mahour wrote: > > Re implementation of lion mail is required in any case . > > It is currently using data engine which is not the required tool as it > > should use models throughout and all is bas

Selecting wallpaper during Activity creation

Hi everyone, when Ivan posted a screenshot of the Activities sidebar on Google+ recently, I liked it a lot! The only thing I found missing was the selection of a wallpaper right in the Activity creation dialog, like we have in Plasma Active [1]. The big advantage I see in this is that it assures

Re: Letting users customize the default background on PMC homescreen (Was: Re: Ideas Critical to PMC)

On Tuesday 25 February 2014 10:48:47 Shantanu Tushar Jha wrote: > Hi Harshit, > > First of all, just a note, whenever you have a new thing to discuss, it is > a bad idea to reply to an existing thread which is not directly related > (this is popularly known as hacking others' threads :P) > > To t

Re: Selecting wallpaper during Activity creation

On 28.02.2014 13:22, David Edmundson wrote: Possible downside is it ties in the notion that activities are just about wallpapers and widgets which isn't really the case, and not something we want people to think. Good point, though in Plasma Active, from what I've learned from watching people

Re: Selecting wallpaper during Activity creation

On 28.02.2014 13:31, Marco Martin wrote: On Friday 28 February 2014 13:22:59 David Edmundson wrote: Possible downside is it ties in the notion that activities are just about wallpapers and widgets which isn't really the case, and not something we want people to think. one thing is that it woul

Re: Review Request 116648: Split into one KCM for Desktop Effects and one for Compositing

On Friday 07 March 2014 15:12:43 Jos Poortvliet wrote: > On Friday 07 March 2014 13:37:22 Martin Gräßlin wrote: > > On Friday 07 March 2014 13:07:06 Jens Reuterberg wrote: > > > Sry for perhaps breaking etiquette with review requests. > > > > No that's just fine, but it would be better if you used

Re: Review Request 116648: Split into one KCM for Desktop Effects and one for Compositing

On Friday 07 March 2014 13:37:22 Martin Gräßlin wrote: > > If they have to be split into two, I suggest renaming them into > > something more correct instead of something precise - like > > "Eye candy" and "Compositing KWM system", one being > > extremely childish and fancyful and the other uneces

Re: Review Request 116648: Split into one KCM for Desktop Effects and one for Compositing

> On March 9, 2014, 6:04 p.m., Thomas Lübking wrote: > > File Attachment: New advanced compositing KCM - kcmcompositing.png > > > > > > OOC: Is there any HIG on this? > > Is the situation on QML better than on QWidget? > > (The i

Re: Review Request 116648: Split into one KCM for Desktop Effects and one for Compositing

> On March 10, 2014, 9:20 a.m., Thomas Lübking wrote: > > File Attachment: Latest kcmcompositing screenshot - kcmcompositing.png > > > > > > Would this rather belong into the FX kcm? The "Enable Desktop Effects on Startup" option is one

Re: Review Request 116648: Split into one KCM for Desktop Effects and one for Compositing

> On March 10, 2014, 9:20 a.m., Thomas Lübking wrote: > > File Attachment: Latest kcmcompositing screenshot - kcmcompositing.png > > > > > > Scale method and vsync are backend dependent, so i'd move this below > > the two (resp. them ri

Re: Review Request 116693: Improve layout of Effect View

hugging the left border, could they get some padding, too? - The effect names were bold in the Plasma 1 version and they should be bold here as well (sorry for not noticing that before) - Thomas Pfeiffer On March 10, 2014, 9

Re: Review Request 116693: Improve layout of Effect View

hugging the left border, could they get some padding, too? - The effect names were bold in the Plasma 1 version and they should be bold here as well (sorry for not noticing that before) - Thomas Pfeiffer On March 10, 2014, 9

Re: Review Request 116693: Improve layout of Effect View

; The effect names were bold in the Plasma 1 version and they should be bold here as well (sorry for not noticing that before) - Thomas Pfeiffer On March 10, 2014, 9:48 a.m., Martin Gräßlin wrote: > > --- > This is an

Re: Review Request 116693: Improve layout of Effect View

> On March 10, 2014, 1:01 p.m., Thomas Pfeiffer wrote: > > Ah, much better now! > > Just three things: > > - The search field still says "Search Plugins" but should say "Search > > Effects" (for consistency) or better still just "Search"

Re: Bughunting Season!

On 09.03.2014 14:13, Luca Beltrame wrote: In data domenica 09 marzo 2014 14:00:25, Sebastian Kügler ha scritto: We'll also open up for feedback from the community shortly, with the Alpha release that will be tagged on Thursday (and likely be released the Tuesday thereafter, stability permitting

Re: Review Request 116703: Improve section heading

about the code itself - Thomas Pfeiffer On March 11, 2014, 8:08 a.m., Martin Gräßlin wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard

Re: Bughunting Season!

On 11.03.2014 13:37, Martin Gräßlin wrote: On Tuesday 11 March 2014 09:41:35 Jos Poortvliet wrote: On Monday 10 March 2014 20:10:48 Sebastian Kügler wrote: On Monday, March 10, 2014 18:11:28 Thomas Pfeiffer wrote: On 09.03.2014 14:13, Luca Beltrame wrote: In data domenica 09 marzo 2014 14:00

Re: Bughunting Season!

On 11.03.2014 14:49, Luca Beltrame wrote: In data martedì 11 marzo 2014 14:42:13, Thomas Pfeiffer ha scritto: Yes, maybe we could try it out in RC and if it works well, have Plasma be the test pilot from there on. So, should I postpone the forum creation to RC phase, or open it in the alpha

Re: Bughunting Season!

On 11.03.2014 15:56, Bhushan Shah wrote: On Tue, Mar 11, 2014 at 7:30 PM, Thomas Pfeiffer wrote: I think opening a forum for the alpha testers for general coordination and discussion would be useful anyway, just not for posting bugs/problems at this stage. For this we have IRC.. :P no

Re: Notifications in Next

On Thursday 20 March 2014 21:40:18 Christoph Feck wrote: > On Thursday 20 March 2014 15:11:35 Marco Martin wrote: > > On Thursday 20 March 2014 13:37:12 Martin Klapetek wrote: > > > Hey all, > > > > > > so I think I've nailed all the showstoppers for the new > > > notifications, the code is all in

Re: Notifications in Next

On 24.03.2014 15:19, Martin Klapetek wrote: On Sat, Mar 22, 2014 at 5:10 PM, Thomas Pfeiffer mailto:colo...@autistici.org>> wrote: We're on a Desktop system, so everything that scrolls has to have a scrollbar. Is there anything that strongly speaks against

Re: Notifications in Next

On 24.03.2014 16:21, Martin Klapetek wrote: On Mon, Mar 24, 2014 at 4:17 PM, Kai Uwe Broulik mailto:k...@privat.broulik.de>> wrote: Hi, Concerning the long notifications, I think when KMail lists subject and sender of all (or like 5-10) new mails that's a valid usecase imho. We

Re: Visual design for logout/login/lockscreen

On Saturday 05 April 2014 18:54:03 Andrew Lake wrote: > On Fri, Apr 4, 2014 at 4:37 PM, David Edmundson wrote: > > Awesome! > > That login theme in nice, and I like the idea of the visual > > consistency throughout. I'll have a go at implementing the login stuff > > on Monday, maybe the lock screen

Re: Visual design for logout/login/lockscreen

On 08.04.2014 11:58, Jens Reuterberg wrote: Well the issue is that we have to start being careful what gets crammed in and if too much is crammed in how to hide it away. The point is that too many options visible would be problematic since the main point of a login is to have a place to pick user

Re: Visual design for logout/login/lockscreen

On 07.04.2014 17:20, David Edmundson wrote: On Mon, Apr 7, 2014 at 2:12 PM, Kai Uwe Broulik wrote: Hi, What about QtGraphicalEffects ColorOverlay? I've been using it extensively for some time already to colorize white svg icons in my apps as needed. For the breeze theme that will work fine.

Re: Review Request 117450: Add Milou to the default panel layout

On Saturday 12 April 2014 21:29:17 Marco Martin wrote: > On Saturday 12 April 2014, Vishesh Handa wrote: > > a.) Most of the users won't discover the search in KickOff because there > > is > > no search bar. I could be wrong, but I don't think people think "if I type > > here, it will start searchi

Re: Continued: milou/kickoff/whatever menu

On 17.04.2014 11:53, Marco Martin wrote: Hi all, I know the discussion was already pretty long :/ but we have to continue it. To recap the issue, is to not have too many ways to search stuff, to give a good unified design direction and to decrease what's called the "gulf of execution" i.e. decid

Re: Defaults: panel on each screen?

On Friday 18 April 2014 14:10:05 Marco Martin wrote: > On Friday 18 April 2014, Martin Klapetek wrote: > > Hey, > > > > if there's no plasma config existing, plasma is run for the first time in > > a > > multi-screen env, should plasma create a (default) panel on each screen? > > no, i don't thin

Re: Defaults: panel on each screen?

On Sunday 20 April 2014 02:21:05 David Edmundson wrote: > If we do only default to one panel, then the taskmanager should not > default to "only show applications from the current screen", which it > currently seems to. David, David, are you not paying attention? :-p Your good buddy Martin alread

Re: Cursorsors: where?

On Wednesday 23 April 2014 13:58:02 Martin Gräßlin wrote: > On Wednesday 23 April 2014 13:53:56 David Edmundson wrote: > > Right now we have an oxygen repo full of all different things (icons, > > window decoration, qstyle) > > > > We can make a Breeze repo full of all these new different things.

Re: Cursorsors: where?

On 24.04.2014 12:17, Aleix Pol wrote: Should we maybe start a new thread about that? I think this has little to do with where the cursors should be, and it's a topic that people not interested in cursors can be interested in. Aleix You're absolutely right, I'll start a new one. Sorry for hij

Widget and windeco themes for Plasma Next

Hi everyone, I admittedly injected the topic of widget and windeco themes for Plasma Next into a thread about cursor themes, so now I'm starting this thread to properly separate the two topics. Bear with me, it's gonna be rather long... === What's the current situation? === We now have a wor

Re: Widget and windeco themes for Plasma Next

On 24.04.2014 14:27, David Edmundson wrote: I don't think we want this. So if we want to at least be visually on par with current Plasma, additional work would have to go into the Oxygen QtQuickControls style (and according to David, a bug in Qt would have to be fixed) That particular bug in Qt

Re: Widget and windeco themes for Plasma Next

On 24.04.2014 15:48, Ivan Čukić wrote: (I guess this should be communicated better than we did with 4.o) That's the most important part. Distros were told not to ship 4.0 as default as well, so they created special versions with 4.0 as the default, but apparently enough people were eager eno

Re: Review Request 117450: Add Milou to the default panel layout

On Thursday 24 April 2014 11:53:49 Sebastian Kügler wrote: > One has to take history into account here. While cleaning up the Kickoff UI, > I've removed the "branding" button. This small text is a useful replacement > for that: > > - Distros want to have the distro name somewhere in the UI > - Us

Re: Plasma 5?

On 06.05.2014 17:27, Mario Fux wrote: Aren't the version number mostly important for bug reporting and there they are extracted automatically? Not only for bug reporting but whenever there is a problem. I don't care what version of a piece of software I run, until the moment when something do

Re: Review Request 118038: Bring back a KCM for the screen locker

st user action" or "After the screen was locked". I'd write "Require password after locking:". This is still not 100% clear, but should be more clear than it is now. - Is "Logout automatically after" really useful? do we know of realistic

Re: Review Request 118038: Bring back a KCM for the screen locker

> On May 7, 2014, 7:31 p.m., Thomas Pfeiffer wrote: > > Okay, usability review. Some recommendations, some questions: > > - This right now only has these options because adding wallpapers or > > Plasmoids simply wasn't implemented yet and will get more settings once

Re: Where we are now... (VDG)

On Tuesday 13 May 2014 09:37:20 Marco Martin wrote: > > Not in the Breeze project repo: > > * plasma theme - ready to ship (probably a few minor fixes before artwork > > freeze) > > is in the plasma-framework repo, shipped () Shouldn't the plasma theme go into the breeze repo at some point, too,

Re: Where we are now... (VDG)

On Tuesday 13 May 2014 12:31:11 Marco Martin wrote: > no, the framework repo needs at least one theme, the one with pluginname > "default" since needs it in order to work and can't depend from an artwork > repo for sure. Okay, now I got it, it's about the framework which can be used outside the w

Re: Where we are now... (VDG)

On Tuesday 13 May 2014 13:16:18 Marco Martin wrote: > On Tuesday 13 May 2014, Thomas Pfeiffer wrote: > > Which part of the 4.x release exactly do you mean? > > Applications don't decide for themselves which widget theme they use, do > > they? So people who use 4.14 with

Re: Where we are now... (VDG)

On Tuesday 13 May 2014 13:44:12 Sebastian Kügler wrote: > On Tuesday, May 13, 2014 12:25:57 Thomas Pfeiffer wrote: > > As far as I know, the idea was to apply the Breeze color scheme and remove > > the gradient from the next release of Oxygen > > I tried that last week,

Re: Plasma Next release schedule changes

On 14.05.2014 12:58, Sebastian Kügler wrote: Hey all, We had to delay the Plasma Next release, because Frameworks will only be released July 1st. Jonathan has adjusted the online schedule, the short version of the relevant part is: * Beta 2: Thu June 5 tagging, Tue 8 June release * Release Cand

Re: Ship with Aurorae and Qtcurve or not...

On 15.05.2014 12:16, David Edmundson wrote: On Thu, May 15, 2014 at 11:39 AM, Jens Reuterberg wrote: Ok so after the feedback from the Beta Release an issue that we knew was coming have happened. Visuals being the most easily accessible bit of anything technical, people have reacted negatively

Re: Ship with Aurorae and Qtcurve or not...

On 15.05.2014 14:10, Martin Gräßlin wrote: On Thursday 15 May 2014 14:08:29 Sebastian Kügler wrote: On Thursday, May 15, 2014 13:58:04 Marco Martin wrote: On Thursday 15 May 2014 13:35:21 Thomas Pfeiffer wrote: On 15.05.2014 12:16, David Edmundson wrote: On Thu, May 15, 2014 at 11:39 AM

Re: Ship with Aurorae and Qtcurve or not...

On Thursday 15 May 2014 12:49:31 Martin Gräßlin wrote: > I really don't want to have an Aurorae theme as default. It would undermine > the fact that I told distros to not do that. We cannot bend ourselves like > that :-) Plan B: Use a QtCurve-based windeco together with the QtCurve widget style?

Re: Ship with Aurorae and Qtcurve or not...

On Friday 16 May 2014 13:37:34 Marco Martin wrote: > On Thursday 15 May 2014, Marco Martin wrote: > > btw, i added a small kde4 application in the breeze repo in the branch > > mart/kde4breeze > > that tries to set qtcurve, apply colors etc in the kde4 session. > > Do we go in this direction? > >

Re: Icons for Paste Bin and Paste

On Tuesday 20 May 2014 19:00:08 Marco Martin wrote: > > 2. All applet icons are coloured. > > if the vdg thinks that the share applet should be monochrome in the UI, this > can be done: > * do an icon for it in the png icon theme, colored and all > * same name, monochrome and svg version in the pl

Re: Icons for Paste Bin and Paste

On Thursday 22 May 2014 18:47:15 Jens wrote: > Ok remade it since... well since a clipboard doesn't make sense > really. It's either this with the image, or perhaps a paperclip or an > arrow? Since what you intend to do is share something or atleast > move it into "the cloud" as it where > > http:

Re: Icons for Paste Bin and Paste

On Thursday 22 May 2014 19:17:22 Jens wrote: > Ah the issue that there are TWO pastebin, one good for images (of > all kinds, including the link above btw) as well as text and one not > so good that is just for text > > Perhaps a paperclip instead of the image then? Oh, sorry, I was spewing nonse

Re: Notification bloat (4.xx)

On Friday 23 May 2014 10:16:03 Martin Klapetek wrote: > Thomas - what's your opinion here? Should notifications about file > operations be persistent or not? I just invited Celeste to this discussion. Given that she wrote her PhD thesis about desktop notifications, she's the expert here ;)

Re: Plasma Addons

On Saturday 24 May 2014 16:51:49 David Edmundson wrote: > KDE 3.x had a clock with 5 pages of config tabs. It was not a great system. > > I don't think there's much wrong with doing one thing and doing it > well. Swappable small parts iis what plasma does well. Exactly! That's why I suggested (an

Re: Notification bloat (4.xx)

On 24.05.2014 02:54, Celeste Lyn Paul wrote: There definitely needs to be better logic when it comes to showing certain types of notifications. One of KDE's strengths is that all notifications are channeled through the same system, and so KDE can control the behavior of all notification interrupt

Re: Plasma Addons

On Monday 26 May 2014 11:00:32 Martin Gräßlin wrote: > that was also not my intention. Still we need to rethink how to handle the > addons. We accepted that the addons became a dumping ground for 3rd party > plasmoids which then went into unmaintained state. That is something we need > to address.

Re: Review Request 118337: Adjust to deprecated PM_DefaultLayoutSpacing:

patch applied so we could see whether all layout glitches have been fixed and add Andrew Lake to the review request? That would be great, thanks! - Thomas Pfeiffer On May 26, 2014, 11:19 p.m., David Edmundson wrote: > > --- > T

Re: Review Request 118390: Powerdevil KCM Updates

fraid. - For grouping controls (as in the case of Battery Levels and Events) the HIG recommends using group boxes (see http://techbase.kde.org/Projects/Usability/HIG/GroupBox ) instead of simply spacing Apart from those two things, the changes look fine to me! - Thomas Pfeiffer On May 28, 2014,

Re: Review Request 118390: Powerdevil KCM Updates

On Friday 30 May 2014 15:34:27 Sebastian Kügler wrote: > I'll not change to groupboxes in this review, but anticipate the HIG > catching up. :) Yes, that's okay. We'll discuss the grouping HIG on our list. If we come out with a different solution to what you implemented in the end, we'll notify y

Re: Review Request 118390: Powerdevil KCM Updates

there. Can you fix them as well? - Thomas Pfeiffer On May 30, 2014, 2:19 p.m., Sebastian Kügler wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.

Re: Review Request 118390: Powerdevil KCM Updates

fixed in the diffs are those in the "Battery Levels" group of the Advanced Settings: Low Level, Critical Level, At Critical Level. All others seem fixed now from what I can tell from the diffs. - Thomas Pfeiffer On June 2, 2014, 1:35 p.m., Sebasti

Re: Review Request 118390: Powerdevil KCM Updates

ne from my side now! - Thomas Pfeiffer On June 2, 2014, 4:04 p.m., Sebastian Kügler wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.review

Re: Review Request 118406: Notify the user if the location containing the media is inaccessible.

a tooltip on mouseover on a pointer device or on tap on a touch device. If it's already done in a similar way, then it's fine for me ;) - Thomas Pfeiffer On June 3, 2014, 5:05 p.m., R.Harish Navnit wrote: > >

Re: Review Request 118406: Notify the user if the location containing the media is inaccessible.

> On June 5, 2014, 8:36 a.m., Thomas Pfeiffer wrote: > > Usability review: > > Since I lack the skills to picture it from the diff: When exactly is the > > notification shown? Is it shown as soon as the media is supposed to be > > played? If so, I think it could b

Re: Review Request 118406: Notify the user if the location containing the media is inaccessible.

> On June 5, 2014, 8:36 a.m., Thomas Pfeiffer wrote: > > Usability review: > > Since I lack the skills to picture it from the diff: When exactly is the > > notification shown? Is it shown as soon as the media is supposed to be > > played? If so, I think it could b

Re: Ideas around Highlight

On Sunday 15 June 2014 18:12:43 Sinny Kumari wrote: > On Sun, Jun 15, 2014 at 4:48 PM, Akshay Ratan wrote: > > Hello, > > > > In my opinion, second highlight looks more crisp and sharp and hence > > preferable. :) > > > > + 1 > > But I am not usability expert I'd say they're both okay from a u

Re: Ideas around Highlight

On Sunday 15 June 2014 19:23:35 Bhushan Shah wrote: > On Sun, Jun 15, 2014 at 6:50 PM, Bhushan Shah wrote: > > This is KDE4 version and yes I have tried my port to Plasma Next with > > breeze theme but due to dark background it does not look very well on > > breeze theme.. Though breeze dark theme

Re: Review Request 124675: Fix Bug 311991 - Taskbar buttons for minimized apps should not use disabled state

> On Oct. 25, 2015, 10:05 p.m., Thomas Pfeiffer wrote: > > As always: If you want design or usability input, please provide a > > screenshot. We cannot read the code. Thanks. > > Eike Hein wrote: > Thomas, all this does is not grey out the text in Task Manager

Re: Review Request 124675: Fix Bug 311991 - Taskbar buttons for minimized apps should not use disabled state

> On Oct. 25, 2015, 10:05 p.m., Thomas Pfeiffer wrote: > > As always: If you want design or usability input, please provide a > > screenshot. We cannot read the code. Thanks. > > Eike Hein wrote: > Thomas, all this does is not grey out the text in Task Manager

Re: Review Request 125898: [Clipboard plasmoid] Fade out text where buttons are

! - Thomas Pfeiffer On Oct. 31, 2015, 5:21 p.m., Kai Uwe Broulik wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.

Re: Review Request 125891: calendar: Allow to scroll navigate in the entire DaysCalendar component

header area should be scrollable instead of just the label. One thing to make sure (if that is even affected by this change at all) is that when we have events in the poup, scrolling over the even description won't change the month. Other than that, +1 for the change! - Thomas Pfeiffer O

Re: Review Request 125897: [Clipboard plasmoid] Fix line breaks

much sense to me, as that would bring back the original problem fixed by the highlighting (that what gets pasted in is not the same as what you saw in the preview). Therefore it should show the whitespaces for all lines. - Thomas Pfeiffer On Oct. 31, 2015, 4:47 p.m., Kai Uwe Broulik wrote

  1   2   3   4   5   6   >