[Powerdevil] [Bug 340063] New: Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

Bug ID: 340063
   Summary: Please make KDE fade to black before turning screen
off
   Product: Powerdevil
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: sb56...@gmail.com

Hello,

I sometimes am watching something on the screen or simply reading something for
a long time without moving the mouse. I have my screen set to automatically
turn off after a certain time. However, when that time is reached, it just
abruptly turns the screen off. It would be a much nicer exeperience if it would
fade to black and allow the user to interrupt the process before the screen
turns off. For me this is actually such an important feature that it currently
prevents me from using Plasma, although I would like to use it.

Here are several related bugs, but not exactly the same, given that Plasma 5 is
now out and there is no longer a screensaver mechanism.
Bug #183119
Bug #86683

Thanks!

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

S  changed:

   What|Removed |Added

Product|Powerdevil  |plasmashell
  Component|general |general
   Target Milestone|--- |1.0
 CC||bhus...@gmail.com
Version|5.0.1   |5.1.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

--- Comment #13 from S  ---
OK, it looks like I'm seeing the fade, but it definitely seems too fast. The
idea in my opinion is not just to make it aesthetic, but to give the user an
alert that it's about to turn off so it can be interrupted. I'd like to see an
interval of about 5 seconds.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

--- Comment #15 from S  ---
Hi, I have to take back my last comment, I'm not seeing any fading. The screen
goes from full-on straight to black with no fading transition (I assume this is
the lockscreen activating) and then the energy module kicks in and turns off
the screen.

Where is the fade supposed to occur? Before the lockscreen or before the energy
module turns off the screen?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

--- Comment #17 from S  ---
(In reply to Kai Uwe Broulik from comment #16)
> A couple of seconds before the screen turns off, no matter what is currently
> shown (desktop or lock screen)

OK, thanks for the explanation. So I can confirm that I am definitely not
seeing any fading. About 5 seconds before the energy saver turns off the
screen, my screen goes straight to a black screen with the backlight and mouse
pointer still on. Then the screen turns off. Could you please help me diagnose
why this isn't working?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

--- Comment #19 from S  ---
Hmm I see. So I guess what I was requesting with this bug report is what
mate-screensaver does, ~5 second fade to black which gives the user a chance to
interrupt it before the screen goes completely black.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Powerdevil] [Bug 304696] Display is dimmed in half the time you configure to dim

[S]

https://bugs.kde.org/show_bug.cgi?id=304696

S  changed:

   What|Removed |Added

 CC||sb56...@gmail.com

--- Comment #13 from S  ---
Created attachment 115877
  --> https://bugs.kde.org/attachment.cgi?id=115877&action=edit
Power settings not obeyed

Hi, this bug still exists in Plasma 5.14.1 (on openSUSE Tumbleweed).

With the settings in this screenshot, it appears to dim to about 50% brightness
after 2.5 minutes (half of my configured 5 minutes). But what is more strange
is that it goes into yet another dimmed state of about 10% brightness at the 5
minute mark, and finally powers off the screen entirely at 6 minutes.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

--- Comment #21 from S  ---
(In reply to Christoph Feck from comment #20)
> The entire discussion in this bug report looks like there is a
> misunderstanding between "black" and "off".

That seems to be the issue. :-)  I should also clarify that I am referring to a
fade of the screen color to black, not a change to the backlight brightness.

I personally think it should just gradually fade to black (and be interruptible
by user input) during about 5 seconds.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S]

https://bugs.kde.org/show_bug.cgi?id=340063

--- Comment #24 from S  ---
@Alexander thanks for the clear explanation. In that case, could I please
request that the #1 stage of fade to black be increased to about 5 seconds, or
even make it user configurable in traditional KDE fashion? Thanks a lot.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: plasmate:questions about coding

[Sam S.]

Hi,

I hope it's okay if I drop in on the discussion.

Being a KDE enthusiast but not much of a C++ programmer, I'm quite
interested in using QML for creating KDE plasmoids. So apart from
reading up on QML documentation, I also downloaded plasmate from git
and gave it a try (and am actually using it now for creating my first
QML plasmoid).

Here are my thoughts:

On Thu, Apr 21, 2011 at 1:54 PM, Aaron J. Seigo  wrote:
> i really would like to keep that first screen's UI clean. is it really
> necessary to be able to clear projects if there are only four or less? maybe
> not.

I actually do think that having an easy way to delete a project from
that list (and from disk) would be nice.

For example, just because you open an existing plasmoid from
GetHotNewStuff _once_ (to look at it's code), doesn't mean you always
want it to "stick in your face" from now on every time you start
plasmate... ;-)

What's wrong with the context-menu solution you mentioned above?
Or a hovering "delete" tool button on each list entry (maybe only
visible while the mouse is over the respective list item)?

Oh and while I'm at it, the other function I felt was missing was a
way to close the current project and get back to the start page,
without quitting plasmate and re-starting it. (Maybe a simple "File >
Close" menu entry?)
And of course support for data engines, which doesn't seem implemented
yet (when I try to create on, plasmate crashes).

All in all, however, plasmate is a pretty useful tool already, even if
it's not yet finished. Thanks for creating it, it really makes it much
easier for someone like me to get started with plasmoid development!

>> Also,in the near future we must decide if we want plasmate to support only
>> QML or other bindings as well.A lot of the TODOs and FIXMEs are related
>> with the bindings.
>
> yes, this is something i want to discuss wiht people at Tokamak 5 next week
> and come to a decision on. do you (or others :) have any opinions on this?

You're just talking about plasmoids, right? Not also about data engines?

While QML+JavaScript seems to be an awesome combination, I can still
see reasons why one might sometimes use Python or Ruby - either
directly for the plasmoid code, or at least in the form of a data
engine:

 - plasmoids that want to make use of external libraries which are
only available in Python (in fact the plasmoid I'm trying to create is
of this type, although I'm using QML and plan to create a Python data
engine for communicating with the external library)

 - plasmoids that require complex non-UI logic for which JavaScript is
either not well suited, or not preferred by the developer (JavaScript
just doesn't make it easy to keep large chunks of code clean and
reusable, and provides less convenience features than e.g. Python)

Cheers,

  Sam
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

5.5 video

[Lucas S]

Hi
Thanks for all comments. I think that I fixed most (all?) remaining issues.

- Improved  visibility of the text by adding black transparent
background and by moving to the beginning of the sequences
- Fixed a typo
- Added 2 more activities so filtering looks more natural now. (With
more than 5 activities there is a scrollbar visible, which looks kinda
out of place)
- Removed a window with activities settings
- Improved muon part (cropped "freedom")
- Added simple fade in/fade out effect for the first and last title
(but still think that 3d dissolving animation looked the best ;))

Link:
https://youtu.be/DsSyPpHS6HI

Cheers
Lucas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: 5.5 video

[Lucas S]

Hi

>The appearance of the overlays texts and the some scene cuts at roughly the
>same time should be more synchronous.

This is intentional, but I will try to play with some fade out effect
to make cuts more subtle.

Cheers
Lucas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: 5.5 video

[Lucas S]

Hi,

- Added simple cross fade effect between the end of the sequences and the titles

Link
https://youtu.be/WZWmtAohp7s

Cheers
Lucas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: [plasma-devel] Re: 5.5 video

[Lucas S]

Hi,

-Fixed a typo "managment" => "management".

Thanks for spotting this

Link
https://youtu.be/3wFTo34mCj0
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Plasma 5.6 video

[Lucas S]

Hi all

Since Plasma 5.5 video (https://www.youtube.com/watch?v=3wFTo34mCj0)
was rather successful I would like to continue with Plasma 5.6 video.
So here is my grand plan for this release:

1. I would like to use voice recording for the video instead of the
simple text. We need native English speaker for this task (preferably
woman). Unfortunately I do not know such a person in the KDE
community, so I am hoping for help of the plasma team in that matter.
2. We need to write a script/text for our brave volunteer. I may take
care of this, but my English skills are well... quite low so I need an
assistance.
3. A list of the features in the upcoming Plasma 5.6 release. Useful
also for a release announcement.
4. Plasma/KDE  YouTube channel.  There is an official KDE community
https://plus.google.com/105126786256705328374/posts  on g+ so maybe it
is a good idea to add youtube channel.
5. I may need some official graphics/logos/backgrounds for the video.

Plan B
As they say "No battle plan survives contact with the enemy" so we
need a plan B/minimum. Basically I am going to make something similar
to Plasma 5.5 video, maybe with better compositing and animations.
That's all for now.

Greetings!
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

5.6 features

[Lucas S]

Dear developers

Please add your feature to the list asap, otherwise it will not be
mentioned in the 5.6 video. Two short sentences per feature should be
enough ;)

Cheers,
Lucas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Plasma 5.6 video

[Lucas S]

Hi

It is time for a quick update so here is the first version of the
Plasma 5.6 video https://youtu.be/q-nACSvivGU
After initial feedback on the plasma IRC channel, this is the list of
planned changes for the next video.

1.  Rework the end of the video, because now it ends rather unexpectedly.
2.  Update the "widget explorer" part
3.  Ivan are you ok with the "Activity Manager" part?
4.???
Feel free to post other suggestion/improvements, but please be quick :)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Plasma 5.6 video

[Lucas S]

Hi

"One thing that I found little bit off is the animation transition at 1:20.
It's kinda hasty/fast zoom-out-zoom-in. Maybe zoom directly to the
next scene without the zooming out?"

This is the tricky one, because here I change the view from "monitor
template" to full screen, hence this fast zoom-out-zoom-in. It also
makes the video more dynamic and the change between scenes is less
visible.  Basically I use the two effects when I switch between
scenes, the first one is fast zoom out and zoom in, the other is
something I call "white flash". This is how it looks like in this
scene https://youtu.be/uKO0RwuDMzU. Fast zoom-out-zoom-in looks much
better in my opinion. And yes I tried with a simple zoom, but the
result is disappointing.


"Also sometimes it shows things within a screen and sometimes
not (it's most notable at 1:46 when it suddenly zooms out for no
apparent reason). This is really a minor issue, just for the sake
of consistency."

Ah yes.  As I mentioned earlier I use two modes for the video scenes a
"monitor template" and full screen. When I switch to monitor template
the video is downscaled and makes things blurry. This is not a problem
for the video sequences when I show only parts of the screen like
download progress or media controls on the panel, but is quite
problematic for a full screen sequences like breeze theme part. As for
1:46, well at first I just wanted to do a simple zoom in but weather
widget is still using old oxygen icons and the buttons on the media
frame plasmoid are misaligned and the effect is not something we want
to show, hence zoom out  ;)
https://youtu.be/ywtINeDKBLo


Cheers
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Plasma 5.6 video

[Lucas S]

Hi

Plasma 5.6 video RC ;)

https://youtu.be/hhNNe6i9I9o

If there will be no major issues this is going to be the final Plasma 5.6 video.

Changes:
1. Revamped the end of the video
2. Included most of the suggestions from from Martin Klapetek
3. Corrected  the widget explorer part.
4. A couple of other small fixes

I can still adjust a few things if there will be such a need, so
comments welcome.

Cheers
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Plasma 5.6 video

[Lucas S]

Quick update, just to fix two small glitches
https://youtu.be/LYpK8k-5Rcs

2016-03-20 22:38 GMT+00:00 Lucas S :
> Hi
>
> Plasma 5.6 video RC ;)
>
> https://youtu.be/hhNNe6i9I9o
>
> If there will be no major issues this is going to be the final Plasma 5.6 
> video.
>
> Changes:
> 1. Revamped the end of the video
> 2. Included most of the suggestions from from Martin Klapetek
> 3. Corrected  the widget explorer part.
> 4. A couple of other small fixes
>
> I can still adjust a few things if there will be such a need, so
> comments welcome.
>
> Cheers
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Plasma 5.6 video

[Lucas S]

2016-03-21 8:23 GMT+00:00 Martin Steigerwald :
> On Montag, 21. März 2016 00:44:24 CET Lucas S wrote:
>> Quick update, just to fix two small glitches
>> https://youtu.be/LYpK8k-5Rcs
>>
>> 2016-03-20 22:38 GMT+00:00 Lucas S :
>> > Hi
>> >
>> > Plasma 5.6 video RC ;)
>> >
>> > https://youtu.be/hhNNe6i9I9o
>> >
>> > If there will be no major issues this is going to be the final Plasma 5.6
>> > video.
>
> Great video, Lucas! Thanks for doing it.
>
> Two notes:
>
> 1) I was a little irritated that voice starts immediately after pressing play,
> but then found that its still part of the intro and there is a short title.
>
> 2) I do not see any task manager progress thing when the woman who speaks
> talks about it. Only a short "copy completed" note in Dolphin. I think it
> would be nice to actually see the task manager progress display at work. Am I
> missing something? I really watched it three times or so.
>
> Thanks,
> --
> Martin
> ___
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel

Hi

2. Look closely. There is a green bar moving slowly in the task
manager (distro - Dolphin) on the panel

Cheers
Lucas
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 350434] New: SDDM theme does not use Breeze user icons

[Markus S .]

https://bugs.kde.org/show_bug.cgi?id=350434

Bug ID: 350434
   Summary: SDDM theme does not use Breeze user icons
   Product: Breeze
   Version: 5.3.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: kamika...@web.de

Compare
http://static.davidedmundson.co.uk/blog/display_managers_finale/breeze_login_screen.png
to
http://i1-news.softpedia-static.com/images/news2/KDE-Plasma-5-1-0-Brings-Back-Some-Old-Features-462226-6.jpg

The user image in the first screenshot is not the Breeze one.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 350434] SDDM theme does not use Breeze user icons

[Markus S .]

https://bugs.kde.org/show_bug.cgi?id=350434

Markus S.  changed:

   What|Removed |Added

 CC||kamika...@web.de,
   ||k...@davidedmundson.co.uk

--- Comment #1 from Markus S.  ---
CC'ing David as he's listed as the author.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 350434] SDDM theme does not use Breeze user icons

[Markus S .]

https://bugs.kde.org/show_bug.cgi?id=350434

--- Comment #3 from Markus S.  ---
(In reply to David Edmundson from comment #2)

> This path overridable in sddm.conf

Why not then make the KCM change the path on theme change?
Would this also fix displaying custom per-user icons set in System Settings?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[kwrited] [Bug 491272] New: Write Daemon/Local System Message Service does not show notifications sent using wall(1) or write(1)

[Colin S]

https://bugs.kde.org/show_bug.cgi?id=491272

Bug ID: 491272
   Summary: Write Daemon/Local System Message Service does not
show notifications sent using wall(1) or write(1)
Classification: Frameworks and Libraries
   Product: kwrited
   Version: 5.27.11
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: bugs.kde@zetafleet.com
  Target Milestone: ---

SUMMARY
Messages sent with wall(1) or write(1) never appear in the desktop environment
(nor in Konsole sessions, for that matter, so this may not just be a Write
Daemon issue).

STEPS TO REPRODUCE
1. Open Konsole
2. Type `echo 'Hello' |wall`

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
A desktop notification should appear that says 'Hello'. Otherwise, if Write
Daemon cannot initialise successfully for some reason, it should probably
detect that and report it.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.9.10-amd64 (64-bit)

ADDITIONAL INFORMATION
I have confirmed that the Write Daemon service is enabled and running in
Background Services, and that the Local System Message Service in Notifications
is configured to “Show a message in a popup” for “The daemon received a new
message sent with wall(1) or write(1)” event.

Messages sent with wall/write *do* appear as expected in a plain tty (e.g.
Ctrl+Alt+F5). Additionally, when the system shuts down, the wall/write messages
are also visible in that tty.

kwrited is built and packaged as a module rather than as an executable in
Debian. I saw a comment in the CMakeLists.txt file that suggests that
libutempter needs to be available; that package (libutempter0) was not
installed on my system, so I installed it and restarted the Write Daemon
service, and still did not receive notifications.

There are no errors or warnings that I can see in logs that might suggest why
this is not working.

Running `w` shows one login with tty1 for `/usr/bin/startplasma-wayland`, and
one login with no tty for `/usr/lib/systemd/systemd --user`. There are never
additional logins for Konsole terminals and nothing about kwrited, but I do not
know if this is expected or not.

I am running KWin using Wayland.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[ksysguard] [Bug 421902] New: Package ksysguard5 cannot be installed on the current openSUSE Leap

[S. Bryant]

https://bugs.kde.org/show_bug.cgi?id=421902

Bug ID: 421902
   Summary: Package ksysguard5 cannot be installed on the current
openSUSE Leap
   Product: ksysguard
   Version: 5.18.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: libksysguard
  Assignee: plasma-devel@kde.org
  Reporter: st...@bawue.de
  Target Milestone: ---

SUMMARY
Package ksysguard5 (and some others) cannot be installed on the current
openSUSE Leap.

STEPS TO REPRODUCE
1. On Leap 15.1, add the KDE repos; see:
https://en.opensuse.org/SDB:KDE_repositories
2. zypper in ksysguard5-5.18.90
3. 

OBSERVED RESULT
Problem: ksysguard5-5.18.90-lp151.264.1.x86_64 requires
libprocesscore.so.9()(64bit), but this requirement cannot be provided
  not installable providers:
libksysguard5-5.18.90-lp151.257.1.x86_64[KDE_Frameworks5]
...

EXPECTED RESULT
The installation succeeds.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:  upgrading 5.18.5 -> 5.18.90
KDE Frameworks Version: 
Qt Version: 5.14.1

ADDITIONAL INFORMATION
The previous package libksysguard5-5.18.5 includes
/usr/lib64/libprocesscore.so.7.  It appears that the 5.18.90 package does not
include the required libprocesscore.so.9, and it's not available in any other
package that I can find.  This in turn means a number of other packages won't
install either; in my case I'm left with a version mix and some broken
functionality.  I'm hoping this is just a minor error in the packaging process.

What is the correct severity for uninstallable packages?  Please adjust
accordingly!

-- 
You are receiving this mail because:
You are the assignee for the bug.

Air theme active task SVG improvement

[S. Christian Collins]

Hi Developers,

I noticed that the Air theme's graphic for the active task (on the task 
manager) was a pixmap, whereas the other button states were true SVG 
vector shapes.  As a result, the active task (appears as depressed 
button) didn't perfectly match the other button states, and there were 
alignment issues, such as the infamous 1px gap at the right edge of the 
active task button.


So, I recreated the active task button using vector shapes instead, and 
have attached the file here (./widgets/tasks.svgz).  This is based on 
the air theme version included with KDE 4.8.0.  FYI, after replacing the 
tasks.svgz file, you might not able to see the change in the air theme 
until after deleting the plasma theme cache file in 
~/.kde/cache-/hostname//.


I've also included this fix in the Frosty Air Theme on kde-look.org 
 if you want to 
give it a test.  You may also want to consider the changes made to the 
Frosty Air theme for inclusion in the default air theme, since they 
improve text readability when the desktop effect "blur" is active (see 
KDE bug #278861 ).


-~Chris

<>___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Not able to install on my Nexus 5

[Arya S Jr]

Hi devs,
I'm trying to install KDE Plasma-mobile on my Nexus 5, and I want the
latest stable image.

I'm experiencing a few errors,
1. It says, "unknown flag 'developer-mode' ".
2. And " unknown flag 'password' ".
3. After removing these flags (I'm not sure if removing these two flags is
right, but does nothing until removed), starts downloading, but after a few
percentage gets out and says, " unexpected EOF".

Now, what can I do?
Is there any way to download the files manually (where?) and install on the
phone manually (how)?

I appreciate your help in advance.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Not able to install on my Nexus 5

[Arya S Jr]

Hi devs,
I'm trying to install KDE Plasma-mobile on my Nexus 5, and I want the
latest stable image.

I'm experiencing a few errors,
1. It says, "unknown flag 'developer-mode' ".
2. And " unknown flag 'password' ".
3. After removing these flags (I'm not sure if removing these two flags is
right, but does nothing until removed), starts downloading, but after a few
percentage gets out and says, " unexpected EOF".

Now, what can I do?
Is there any way to download the files manually (where?) and install on the
phone manually (how)?

I appreciate your help in advance.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 374311] New: it is too easy to activate context menu item if mouse moves during right-click

[S . Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=374311

Bug ID: 374311
   Summary: it is too easy to activate context menu item if mouse
moves during right-click
   Product: Breeze
   Version: 5.8.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: s_chriscoll...@hotmail.com
  Target Milestone: ---

Please see the following video:
https://youtu.be/5U9XQgf3NXI

When using applications in KDE, it is very easy to accidentally activate a
context menu item if the mouse cursor is not perfectly steady during the right
mouse click that brings up the menu. As you can see in the video, in some cases
the cursor only needs to travel 2 pixels between mouse press and release to
activate the menu item.

Steps to reproduce:
1. Open Dolphin and move it to the bottom right-hand corner of the screen.
2. Right-click (and keep the mouse button down) in the white space near the
bottom right-hand corner of Dolphin. The context menu should open just above
the mouse cursor.
3. Move the mouse up 2 pixels and release the mouse button.

Result: The bottom entry of the context menu is activated. The problem is that
this all too often happens very quickly if my mouse is not steady, or my
trackpad's accuracy sucks (which it does). For example, I can't tell you how
many times I've accidentally disabled a clip in this manner when editing videos
in Kdenlive.

Some possible solutions include:
1. If a right mouse click is very short (very little time between mouse press
and release), a context menu item shouldn't be activated on mouse button
release.
2. Set a minimum number of pixels the mouse cursor must move between launching
the menu (mouse right button press) and activating the menu item (mouse right
button release).
3. Add a few pixels of padding region around the context menu where the cursor
can exist without a menu item being selected. This solution already exists in
the Oxygen widget style, as seen at the end of the video.
4. Have the context menu appear a few pixels away from the mouse cursor instead
of right at the tip of the pointer. This solution would function similar to
solution #3, but without causing potential changes to the appearance of the
widget style.

I didn't know exactly which component to report this bug against, since as far
as I know it could be a KDE, Qt, or Breeze issue. Please reassign as necessary.

** My System **
OS: KDE Neon 5.8.90 64-bit (Plasma Desktop 5.8.5+git20161227.1802-0, KDE
Frameworks 5.30.0, Qt 5.7.0)
Linux Kernel: 4.4.0.57-generic

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 374311] it is too easy to activate context menu item if mouse moves during right-click

[S . Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=374311

--- Comment #3 from S. Christian Collins  ---
I have reported this bug for Qt here:
https://bugreports.qt.io/browse/QTBUG-57849

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Breeze] [Bug 374311] it is too easy to activate context menu item if mouse moves during right-click

[S . Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=374311

S. Christian Collins  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

D14869: [RFC] Increase default font sizes by 1 pt

[Øystein S . -Alværvik]

oysteins added a comment.


  In D14869#309949 , @rkflx wrote:
  
  > F6198464: kubuntu10-kubunbtu11-win10-macos.png 

  
  
  I feel that Windows' font rendering produces significantly sharper fonts than 
anything else. FWIW I think it's both their choice of font (Segoe UI) and their 
ClearType technology that makes text in Windows easy to read even at 9pt. 
Increasing Noto Sans' size doesn't make it sharper in my eyes; perhaps AA and 
general font rendering is worth looking at.

REPOSITORY
  R119 Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D14869

To: ngraham, #plasma, #kde_applications, valorie, #vdg
Cc: oysteins, rooty, filipf, safaalfulaij, rikmills, harmathy, rkflx, abetts, 
davidedmundson, rizzitello, plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, 
ali-mohamed, jensreuterberg, sebas, apol, mart

D15011: [Kickoff] Make the search field always look like a search field

[Øystein S . -Alværvik]

oysteins added a comment.


  In D15011#313872 , @filipf wrote:
  
  > although if I think of my parents for example I do see how they might miss 
it
  
  
  This was the rationale behind my bug report about this; that some users might 
be puzzled about the apparent lack of a search field.
  
  In D15011#313872 , @filipf wrote:
  
  > is it possible to somehow make a toggle to keep the status quo ie. have no 
search box?
  
  
  +1 for this, if it is doable. Perhaps the search field could be toggled only 
for new installs, so upgraders can stick to the status quo?
  
  In D15011#313874 , @anthonyfieroni 
wrote:
  
  > I'm -1 for this, it's not needed to click in just start typing witch is 
more intuitive. Adding this optional by config?
  
  
  The patch seems to retain this functionality. Maybe the patch could keep the 
text 'Type to search…', or does it become redundant?

REPOSITORY
  R119 Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D15011

To: ngraham, #plasma, #vdg, davidedmundson
Cc: oysteins, anthonyfieroni, filipf, abetts, davidedmundson, michaeltunnell, 
plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, 
sebas, apol, mart

D26338: Ensure WM initializes before session starts

[Eon S. Jeon]

esjeon created this revision.
Herald added a project: Plasma.
Herald added a subscriber: plasma-devel.
esjeon requested review of this revision.

REVISION SUMMARY
  This is an attempt to resolve bug 362857. A number of users have complained 
about restored application not supporting desktop effects, like transparency 
and blurring. This is caused by a race condition where restored applications 
start before KWin (and its compositor) finishes its initialization. Under this 
condition, applications fail to detect compositor and disable desktop effect on 
themselves.
  
  This patch tries to avoid this race condition by inserting delay b/w 
initialization of KSM server, which starts KWin (or user-designated WM), and 
start-up phase 0. At the same time, the patch also tries to minimize the actual 
delay by detecting KWin and compositors using D-Bus and KWindowSystem 
repectively.

TEST PLAN
  The nature of this bug (graphics!) forces the use of physical machines for 
testing, but not every machine can reproduce this. Old hardware w/ proprietary 
graphics driver is recommended.
  
  - Pre-requisite:
1. "Restore previous session" option enabled under "Desktop Session".
2. Konsole set up w/ transparent window
3. Verify that the bug is reproducible on your machine (Reboot might be 
required)
  
  - Test 1: session restores normally
1. Login, open Konsole, logout, and re-login
2. Konsole should be restored.
  
  - Test 2: KWin w/ compositor, restore w/ desktop effect.
1. Login, open Konsole, reboot, and login.
2. Konsole should be restored w/ transparent background.
  
  - Test 3: Other WM w/ compositor, restore w/ desktop effect.
1. Put  the following into `~/.xinitrc` (edit it to fit your env.): `export 
KDEWM=/usr/bin/dwm; picom & exec startplasma-x11`
2. From Linux console, run `xinit`.
3. Konsole should be restored w/ transparent background.

REPOSITORY
  R120 Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D26338

AFFECTED FILES
  startkde/plasma-session/CMakeLists.txt
  startkde/plasma-session/main.cpp
  startkde/plasma-session/startup.cpp
  startkde/plasma-session/startup.h

To: esjeon
Cc: plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fbampaloukas, 
GB_2, ragreen, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, ahiemstra, mart

D26338: Ensure WM initializes before session starts

[Eon S. Jeon]

esjeon added a comment.


  Note that this is an RFC at the current state. This can be solved elsewhere 
(e.g. ksmserver), and is **tested only on X11** (I don't have machine that runs 
wayland w/o problems). I also don't like that plasma-session is calling 
QGuiApplication, which is required to use KWindowSystem.
  
  Also, I think it's safe to remove `m_enabled` here, for Qt terminates the 
object after calling emitResult, but I'm not really fluent in Qt to be sure 
about it.
  
  Anyways, there's lots of room for discussion.

REPOSITORY
  R120 Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D26338

To: esjeon
Cc: plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fbampaloukas, 
GB_2, ragreen, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, ahiemstra, mart

D26338: Ensure WM initializes before session starts

[Eon S. Jeon]

esjeon added a comment.


  In D26338#588960 , @davidedmundson 
wrote:
  
  > On the conceptual level, does it make more sense for the relevant client 
(konsole) to monitor for compositing changed itself. It's something that could 
change at runtime regardless, so it needs to react to it anyway?
  >  If it does need that code anyway, there's no point doing fixes in startkde
  
  
  Technically, yes, apps can do that. But this will force changes to any apps 
that embed Konsole (i.e. dolphin, kate) or depend on desktop effects. Also, 
this issue will arise whenever an app implements such features. We can just 
solve this here and forget about it forever.
  
  Also, the problem only occurs during session restoration, so it's clear that 
one change here can fix for all applications.
  
  > Code wise, this gives a timeout for anyone who doesn't run kwin composited, 
which would be a problem as is.
  
  Welp, I agree, but there's just no way to figure out if user wants compositor 
or just WM. A possible solution is to make this toggleable through 
configuration or env, which isn't exactly beautiful.
  
  Still, the impact can be minimized by moving `wmjob` to right before session 
restoration instead of stage0.
  
  > also I don't like the split that ksmserver is waiting for kwin to register 
on ICE, and startkde is waiting on kwin through a combo of both DBus and X 
atoms in KWindowSystem::compositingActive(). That's 3 different paths all used 
at once.
  > 
  > I've been wanting to move the kwin startup from ksmserver into startkde 
anyway, doing those things together would make the most sense.
  
  I agree. Things will be much cleaner if WM is handled in startkde. WM isn't 
really a part of session, and ksmserver already treats WM as a special case 
anyway.

REPOSITORY
  R120 Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D26338

To: esjeon, #plasma, davidedmundson
Cc: asturmlechner, plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, 
fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, 
ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart

Re: Review Request: Use Plasma::ScrollWidget in the widget explorer

[Anselmo L. S. Melo]

> On 2010-10-01 17:21:28, Aaron Seigo wrote:
> > update to current trunk if needed, and let's get this in as well.

@agateau: I've updated this patch to current trunk [1] - I updated it when I 
wrote another patch [2], to check if both patches were ok together.
Now it is an updated version on top of today's trunk =)

[1] - 
http://anselmolsm.org/public/kde/plasma-addwidget-scrollwidget-r1181856.diff
[2] - http://reviewboard.kde.org/r/5446/


- Anselmo


---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/4676/#review7930
---


On 2010-08-04 21:02:11, Aurélien Gâteau wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/4676/
> ---
> 
> (Updated 2010-08-04 21:02:11)
> 
> 
> Review request for Plasma.
> 
> 
> Summary
> ---
> 
> Make AbstractIconList inherit from Plasma::ScrollWidget, has discussed on 
> plasma-devel.
> 
> The horizontal orientation behaved a bit strangely: AbstractIconList was 
> becoming much larger than the screen width. I had to change the layout code 
> to include the "Close" button inside FilteringWidget layout instead of 
> creating another layout.
> 
> Note: you need http://reviewboard.kde.org/r/4675/ to get proper scrollbar 
> slider sizes.
> 
> 
> Diffs
> -
> 
>   trunk/KDE/kdebase/workspace/libs/plasmagenericshell/abstracticonlist.h 
> 1147944 
>   trunk/KDE/kdebase/workspace/libs/plasmagenericshell/abstracticonlist.cpp 
> 1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.h
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.cpp
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletslist.h
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletslist.cpp
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/widgetexplorer.cpp
>  1147944 
> 
> Diff: http://svn.reviewboard.kde.org/r/4676/diff
> 
> 
> Testing
> ---
> 
> Tested in both horizontal and vertical modes, with lists larger and smaller 
> than the view.
> 
> 
> Thanks,
> 
> Aurélien
> 
>

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: Do not use tree view for categories in the vertical widgets explorer

[Anselmo L. S. Melo]

> On 2010-10-01 17:20:56, Aaron Seigo wrote:
> > much nicer.

Commited in r1181683. Thanks.


- Anselmo


---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/5446/#review7929
---


On 2010-09-27 10:57:33, Anselmo L. S. Melo wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/5446/
> ---
> 
> (Updated 2010-09-27 10:57:33)
> 
> 
> Review request for Plasma.
> 
> 
> Summary
> ---
> 
> The propose here is to remove the Tree View used in the widgets explorer in 
> vertical orientation. In its place, use the same button of the horizontal 
> orientation, what simplifies the code (removes a class and some checks) and 
> improves the use of space as the widgets list can grow vertically.
> 
> Better if combined with http://reviewboard.kde.org/r/4676/ as we also gain 
> the space currently occupied by the arrow buttons and the close button in the 
> bottom left corner.
> 
> The screenshots attached show the current widget explorer with the categories 
> tree view and the proposed one, using the categories button.
> 
> 
> Diffs
> -
> 
>   
> /trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.h
>  1179288 
>   
> /trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.cpp
>  1179288 
> 
> Diff: http://svn.reviewboard.kde.org/r/5446/diff
> 
> 
> Testing
> ---
> 
> Tested in both horizontal and vertical orientations.
> 
> 
> Screenshots
> ---
> 
> current widgets explorer
>   http://svn.reviewboard.kde.org/r/5446/s/511/
> proposed, not using the tree view
>   http://svn.reviewboard.kde.org/r/5446/s/512/
> 
> 
> Thanks,
> 
> Anselmo
> 
>

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: Use Plasma::ScrollWidget in the widget explorer

[Anselmo L. S. Melo]

> On 2010-10-01 17:21:28, Aaron Seigo wrote:
> > update to current trunk if needed, and let's get this in as well.
> 
> Anselmo L. S. Melo wrote:
> @agateau: I've updated this patch to current trunk [1] - I updated it 
> when I wrote another patch [2], to check if both patches were ok together.
> Now it is an updated version on top of today's trunk =)
> 
> [1] - 
> http://anselmolsm.org/public/kde/plasma-addwidget-scrollwidget-r1181856.diff
> [2] - http://reviewboard.kde.org/r/5446/
> 
> Aurélien Gâteau wrote:
> Sounds good, please commit your updated version if it's not already in 
> (/me needs to update his trunk checkout)

Ok, I'll commit tomorrow morning here (UTC-3) =)


- Anselmo


---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/4676/#review7930
---


On 2010-08-04 21:02:11, Aurélien Gâteau wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/4676/
> ---
> 
> (Updated 2010-08-04 21:02:11)
> 
> 
> Review request for Plasma.
> 
> 
> Summary
> ---
> 
> Make AbstractIconList inherit from Plasma::ScrollWidget, has discussed on 
> plasma-devel.
> 
> The horizontal orientation behaved a bit strangely: AbstractIconList was 
> becoming much larger than the screen width. I had to change the layout code 
> to include the "Close" button inside FilteringWidget layout instead of 
> creating another layout.
> 
> Note: you need http://reviewboard.kde.org/r/4675/ to get proper scrollbar 
> slider sizes.
> 
> 
> Diffs
> -
> 
>   trunk/KDE/kdebase/workspace/libs/plasmagenericshell/abstracticonlist.h 
> 1147944 
>   trunk/KDE/kdebase/workspace/libs/plasmagenericshell/abstracticonlist.cpp 
> 1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.h
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.cpp
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletslist.h
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletslist.cpp
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/widgetexplorer.cpp
>  1147944 
> 
> Diff: http://svn.reviewboard.kde.org/r/4676/diff
> 
> 
> Testing
> ---
> 
> Tested in both horizontal and vertical modes, with lists larger and smaller 
> than the view.
> 
> 
> Thanks,
> 
> Aurélien
> 
>

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: Use Plasma::ScrollWidget in the widget explorer

[Anselmo L. S. Melo]

> On 2010-10-01 17:21:28, Aaron Seigo wrote:
> > update to current trunk if needed, and let's get this in as well.
> 
> Anselmo L. S. Melo wrote:
> @agateau: I've updated this patch to current trunk [1] - I updated it 
> when I wrote another patch [2], to check if both patches were ok together.
> Now it is an updated version on top of today's trunk =)
> 
> [1] - 
> http://anselmolsm.org/public/kde/plasma-addwidget-scrollwidget-r1181856.diff
> [2] - http://reviewboard.kde.org/r/5446/
> 
> Aurélien Gâteau wrote:
> Sounds good, please commit your updated version if it's not already in 
> (/me needs to update his trunk checkout)
> 
> Anselmo L. S. Melo wrote:
> Ok, I'll commit tomorrow morning here (UTC-3) =)

Don't consider the previous comment, it was saved but not published in 
reviewboard.

Commited in r1183238.


- Anselmo


---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/4676/#review7930
---


On 2010-08-04 21:02:11, Aurélien Gâteau wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/4676/
> ---
> 
> (Updated 2010-08-04 21:02:11)
> 
> 
> Review request for Plasma.
> 
> 
> Summary
> ---
> 
> Make AbstractIconList inherit from Plasma::ScrollWidget, has discussed on 
> plasma-devel.
> 
> The horizontal orientation behaved a bit strangely: AbstractIconList was 
> becoming much larger than the screen width. I had to change the layout code 
> to include the "Close" button inside FilteringWidget layout instead of 
> creating another layout.
> 
> Note: you need http://reviewboard.kde.org/r/4675/ to get proper scrollbar 
> slider sizes.
> 
> 
> Diffs
> -
> 
>   trunk/KDE/kdebase/workspace/libs/plasmagenericshell/abstracticonlist.h 
> 1147944 
>   trunk/KDE/kdebase/workspace/libs/plasmagenericshell/abstracticonlist.cpp 
> 1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.h
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletsfiltering.cpp
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletslist.h
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/appletslist.cpp
>  1147944 
>   
> trunk/KDE/kdebase/workspace/libs/plasmagenericshell/widgetsexplorer/widgetexplorer.cpp
>  1147944 
> 
> Diff: http://svn.reviewboard.kde.org/r/4676/diff
> 
> 
> Testing
> ---
> 
> Tested in both horizontal and vertical modes, with lists larger and smaller 
> than the view.
> 
> 
> Thanks,
> 
> Aurélien
> 
>

___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340063

S  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #9 from S  ---
Hi, was this fix actually implemented in a Plasma release? On 5.6 in openSUSE
I'm seeing a very quick fade, probably under 500ms, which looks slick but
doesn't accomplish the purpose of this bug report, namely, to give the user
time to cancel the screen turning off.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[plasmashell] [Bug 340063] Please make KDE fade to black before turning screen off

[S via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340063

--- Comment #11 from S  ---
Thanks for the reply. Does something need to be done to enable this?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: Draft: Widgets Explorer "Add Widgets"

[Anselmo Lacerda S. de Melo]

On Mon, Nov 23, 2009 at 10:26 AM, Petri Damstén  wrote:
> Modified the diff so it puts the Get New Widgets to the filter row:
> http://kotisivu.lumonetti.fi/damu0/misc/we.diff
>
> It also adds close button but It's not working yet:
> http://kotisivu.lumonetti.fi/damu0/images/add-widgets1.png

Great =)

I made a small modification in you patch and uploaded to
http://www.anselmolsm.org/public/we2.diff

WIP to make the close button work. A question: Should this button
close only the widgets explorer (and show the panel settings again) or
should it close both?



Anselmo
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Review Request: Draft: Widgets Explorer "Add Widgets"

[Anselmo Lacerda S. de Melo]

On Wed, Nov 25, 2009 at 11:10, Petri Damstén  wrote:
> On Wednesday 25 November 2009 07:30:03 Anselmo Melo wrote:
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> http://reviewboard.kde.org/r/2191/
>> ---
>>
>> (Updated 2009-11-25 05:30:03.553432)
>>
>>
>> Review request for Plasma.
>>
>>
>> Changes
>> ---
>>
>> Diff updated. Includes:
>> * "Get New Widgets" button+submenu
>> * Changes by Petri Damstén ("get new widgets" button between the input
>>  field and tabbar + close button) * close button working
>
> Message freeze is today, so is this ready to be committed?

Regarding code it's ready.

I'm not certain about the button text "Get New Widgets". Opinions?


Anselmo

>
> Petri
>





-- 
Anselmo Lacerda Silveira de Melo
http://www.anselmolsm.org
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel