Re: Review Request 125817: Add plugin system for Calendar events

2015-10-30 Thread Martin Klapetek


> On Oct. 31, 2015, 2:08 a.m., David Edmundson wrote:
> > src/declarativeimports/calendar/daysmodel.h, line 44
> > 
> >
> > I think we need some sort of
> > 
> > QStringList availablePlugins()
> > 
> > setPlugins( QStringList plugins);

What for?


> On Oct. 31, 2015, 2:08 a.m., David Edmundson wrote:
> > src/declarativeimports/calendar/daysmodel.cpp, line 63
> > 
> >
> > who deletes it?

Right, needs a qDeleteAll in ~


> On Oct. 31, 2015, 2:08 a.m., David Edmundson wrote:
> > src/declarativeimports/calendar/daysmodel.cpp, line 167
> > 
> >
> > Are you sure this works?
> > 
> > From what I see you're copying the event, then replacing the copy.
> > 
> > (though the autos make it confusing, so I may be wrong)

Yes, it does work. This looks through the stored events and replaces the stored 
one with the one that is passed as the method argument.


> On Oct. 31, 2015, 2:08 a.m., David Edmundson wrote:
> > src/declarativeimports/calendar/daysmodel.cpp, line 179
> > 
> >
> > this can be an invalid index, best to check it
> > 
> > (in each case we do this)

But then all it does is emit dataChanged() with invalid signal...but I'll add a 
check anyway.


> On Oct. 31, 2015, 2:08 a.m., David Edmundson wrote:
> > src/declarativeimports/calendar/daysmodel.cpp, line 209
> > 
> >
> > who owns this?
> > 
> > Q_INVOKABLE tries to be clever, which basically means I never know.
> > 
> > If QML owns it (which I think it does) you're potentially returning 
> > null values if this is called twice
> > 
> > if you own it, you're leaking this if you have m_qmlData when the model 
> > is deleted

Ah, good spot. Should be owned by the model, ideally. All problems solved.


> On Oct. 31, 2015, 2:08 a.m., David Edmundson wrote:
> > src/declarativeimports/calendar/plasmacalendarintegration/calendareventsplugin.h,
> >  line 173
> > 
> >
> > Unless needed otherwise, I'd put the UID in the constructor.
> > 
> > If a plugin uses this, you screw everything up

> If a plugin uses this, you screw everything up

I don't follow. Note that uid is not a mandatory property. You can have events 
without uid. As the comment above it says, it's useful only if you want to 
implement eventModified/eventRemoved (so that it can locate the events in the 
model), which in case of eg. holidays is not needed, cause they are not going 
to be modified/removed. So there's no need to make those plugins more complex 
for no reason.


> On Oct. 31, 2015, 2:08 a.m., David Edmundson wrote:
> > src/declarativeimports/calendar/plasmacalendarintegration/calendareventsplugin.h,
> >  line 202
> > 
> >
> > rather than this much docs, would it make sense to have a protected 
> > method that takes a list, then in this class you turn that into the hash?

Well if the only reason to do that is because "there's too much to read", then 
no :P


- Martin


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125817/#review87768
---


On Oct. 28, 2015, 6:18 p.m., Martin Klapetek wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125817/
> ---
> 
> (Updated Oct. 28, 2015, 6:18 p.m.)
> 
> 
> Review request for Plasma and Daniel Vrátil.
> 
> 
> Repository: plasma-framework
> 
> 
> Description
> ---
> 
> This adds a simple plugin interface that can be subclassed
> and provide events integration with Plasma Calendar applet.
> 
> It's asynchronous and I've kept it deliberately simple.
> For now the Calendar tells the plugins which date range
> is being displayed, the plugins load the data and then
> emit the dataReady() signal containing the events.
> 
> The events are stored in a multihash for quick access
> by the Calendar's agenda part but also for overall
> easy-to-use (eg. in teh model data()).
> 
> The event data is stored in EventData class, which has
> a pretty self-explanatory members, except perhaps the
> "isMinor" one. The intention with this is to support
> namedays, where in some countries the calendars have
> different name every day. This is just a minor holiday
> and as such should not mark t

Re: Review Request 125817: Add plugin system for Calendar events

2015-10-30 Thread David Edmundson

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125817/#review87768
---



src/declarativeimports/calendar/calendarplugin.cpp (line 36)


RegisterUncreatableType?



src/declarativeimports/calendar/daysmodel.h (line 44)


I think we need some sort of

QStringList availablePlugins()

setPlugins( QStringList plugins);



src/declarativeimports/calendar/daysmodel.cpp (line 33)


const



src/declarativeimports/calendar/daysmodel.cpp (line 35)


const



src/declarativeimports/calendar/daysmodel.cpp (line 63)


who deletes it?



src/declarativeimports/calendar/daysmodel.cpp (line 157)


Are you sure this works?

From what I see you're copying the event, then replacing the copy.

(though the autos make it confusing, so I may be wrong)



src/declarativeimports/calendar/daysmodel.cpp (line 169)


this can be an invalid index, best to check it

(in each case we do this)



src/declarativeimports/calendar/daysmodel.cpp (line 199)


who owns this?

Q_INVOKABLE tries to be clever, which basically means I never know.

If QML owns it (which I think it does) you're potentially returning null 
values if this is called twice

if you own it, you're leaking this if you have m_qmlData when the model is 
deleted



src/declarativeimports/calendar/plasmacalendarintegration/calendareventsplugin.h
 (line 173)


Unless needed otherwise, I'd put the UID in the constructor.

If a plugin uses this, you screw everything up



src/declarativeimports/calendar/plasmacalendarintegration/calendareventsplugin.h
 (line 180)


I'd add a dpointer here, even though you don't use it yet.



src/declarativeimports/calendar/plasmacalendarintegration/calendareventsplugin.h
 (line 202)


rather than this much docs, would it make sense to have a protected method 
that takes a list, then in this class you turn that into the hash?


- David Edmundson


On Oct. 28, 2015, 5:18 p.m., Martin Klapetek wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125817/
> ---
> 
> (Updated Oct. 28, 2015, 5:18 p.m.)
> 
> 
> Review request for Plasma and Daniel Vrátil.
> 
> 
> Repository: plasma-framework
> 
> 
> Description
> ---
> 
> This adds a simple plugin interface that can be subclassed
> and provide events integration with Plasma Calendar applet.
> 
> It's asynchronous and I've kept it deliberately simple.
> For now the Calendar tells the plugins which date range
> is being displayed, the plugins load the data and then
> emit the dataReady() signal containing the events.
> 
> The events are stored in a multihash for quick access
> by the Calendar's agenda part but also for overall
> easy-to-use (eg. in teh model data()).
> 
> The event data is stored in EventData class, which has
> a pretty self-explanatory members, except perhaps the
> "isMinor" one. The intention with this is to support
> namedays, where in some countries the calendars have
> different name every day. This is just a minor holiday
> and as such should not mark the calendar grid, otherwise
> the whole grid would be in a different color.
> 
> Putting the interface here might raise the question of
> depending on plasma-framework, but plugins provided by
> KDE can go to plasma-workspace and other 3rd party ones
> would just have to live with it. I don't think it will
> be a problem but if it turns out it is, we can rethink
> the placement.
> 
> 
> Diffs
> -
> 
>   src/declarativeimports/calendar/CMakeLists.txt 40ead91 
>   src/declarativeimports/calendar/calendarplugin.cpp bafe80c 
>   src/declarativeimports/calendar/daysmodel.h a5bdac9 
>   src/declarativeimports/calendar/daysmodel.cpp 2d059a8 
>   src/declarativeimports/calendar/eventdatadecorator.h PRE-CREATION 
>   src/declarativeimports/calendar/eventdatadecorator.cpp PRE-CREATION 
>   src/declarativeimports/calendar/plasmacalendarintegration/CMakeLists.txt 
> PRE-CREATION 
>   
> src/declarativeimports/calendar/plasmacalendarintegration/PlasmaCalendarIntegrationConfig.cmake.in
>  PR

[Powerdevil] [Bug 354623] New: Full charge not trigger notification

2015-10-30 Thread Anthony via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354623

Bug ID: 354623
   Summary: Full charge not trigger notification
   Product: Powerdevil
   Version: 5.4.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: bvb...@abv.bg

When battery is full charged, notification is not shown.

Reproducible: Always

Steps to Reproduce:
1. Systemsettings
2. Notification
3. Power Management System
4. Charge complete
5. notification or task bar entry

Actual Results:  
Notification is not triggered on full charge

Expected Results:  
Notification on battery is full charge

-- 
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 125878: fix lost QuickViewSharedEngine initialSize on initializing

2015-10-30 Thread Takahiro Hashimoto

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125878/
---

(Updated Oct. 30, 2015, 9:06 p.m.)


Status
--

This change has been marked as submitted.


Review request for Plasma, David Edmundson and David Faure.


Changes
---

Submitted with commit 4ca3237c2e07ac035104af5730bd209c18f61fe2 by Takahiro 
Hashimoto to branch master.


Repository: kdeclarative


Description
---

After my commit 1c3f42afe17cc090372eaf45647d71495de12c19, view's initialiSize 
value is lost (remaining 0,0 in spite of item's size). It should be set by 
item's size for some reusing purpose (with initialSize() getter) 

Sorry again my bad commit :(


Diffs
-

  src/quickaddons/quickviewsharedengine.cpp 323cf92 

Diff: https://git.reviewboard.kde.org/r/125878/diff/


Testing
---

build and run test

kenya888@xps13 ~/devel/kf5/build/frameworks/kdeclarative $ ninja test
[1/1] Running tests...
Test project /home/kenya888/devel/kf5/build/frameworks/kdeclarative
Start 1: fullmodelaccesstest
1/2 Test #1: fullmodelaccesstest ..   Passed0.05 sec
Start 2: quickviewsharedengine
2/2 Test #2: quickviewsharedengine    Passed0.39 sec

100% tests passed, 0 tests failed out of 2

Total Test time (real) =   0.44 sec

--

confirmed ksplashqml works well which use QuickViewSharedEngine.


Thanks,

Takahiro Hashimoto

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


Re: Review Request 125864: Add back the Agenda part of the Calendar

2015-10-30 Thread Martin Klapetek

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125864/
---

(Updated Oct. 30, 2015, 8:11 p.m.)


Review request for Plasma.


Changes
---

+ fix issues
+ add time label to the events, see new screenshot

I'm not entirely sure about the offset of the label when there is just one time 
(the todo in the screenshot)
but it makes all things with time aligned properly, so I dunno. Thoughts?


Repository: plasma-workspace


Description
---

Adds back the Agenda that was there pre-5.0 with some changes.

It now shows an overview of the given day events/holidays. I'd
like to add a second view at some point that would show you the
selected day by hours but that is much more work and the freeze
is getting closer, so maybe that will have to wait till 5.6.


Diffs (updated)
-

  applets/digital-clock/package/contents/ui/CalendarView.qml b52eb10 

Diff: https://git.reviewboard.kde.org/r/125864/diff/


Testing
---

Selecting a day correctly changes the date in the agenda and correctly displays 
the events of the day.

Event removal/modification also removes/modifies it from the agenda.


File Attachments (updated)


Current look in Breeze
  
https://git.reviewboard.kde.org/media/uploaded/files/2015/10/29/5485250c-8d20-409e-8a5b-0eda7a9d7b8d__snapshot29.png
Multiple same-day events
  
https://git.reviewboard.kde.org/media/uploaded/files/2015/10/29/d453a01e-f9cf-4da3-8f6a-fac5aa6aadf5__snapshot18.png
New screenshot
  
https://git.reviewboard.kde.org/media/uploaded/files/2015/10/30/c75fed5e-02fd-4906-8bd9-726f0fc54ce8__snapshot30.png


Thanks,

Martin Klapetek

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


Re: Review Request 125864: Add back the Agenda part of the Calendar

2015-10-30 Thread Martin Klapetek


> On Oct. 29, 2015, 5:55 p.m., Sebastian Kügler wrote:
> > applets/digital-clock/package/contents/ui/CalendarView.qml, line 46
> > 
> >
> > Could you clean this out before committing as well? (I know, nothing to 
> > do with your patch, just noticed it.)

I plan to do a bigger cleanup altogether, I'll make as part of that.


- Martin


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125864/#review87678
---


On Oct. 29, 2015, 5:24 p.m., Martin Klapetek wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125864/
> ---
> 
> (Updated Oct. 29, 2015, 5:24 p.m.)
> 
> 
> Review request for Plasma.
> 
> 
> Repository: plasma-workspace
> 
> 
> Description
> ---
> 
> Adds back the Agenda that was there pre-5.0 with some changes.
> 
> It now shows an overview of the given day events/holidays. I'd
> like to add a second view at some point that would show you the
> selected day by hours but that is much more work and the freeze
> is getting closer, so maybe that will have to wait till 5.6.
> 
> 
> Diffs
> -
> 
>   applets/digital-clock/package/contents/ui/CalendarView.qml b52eb10 
> 
> Diff: https://git.reviewboard.kde.org/r/125864/diff/
> 
> 
> Testing
> ---
> 
> Selecting a day correctly changes the date in the agenda and correctly 
> displays the events of the day.
> 
> Event removal/modification also removes/modifies it from the agenda.
> 
> 
> File Attachments
> 
> 
> Current look in Breeze
>   
> https://git.reviewboard.kde.org/media/uploaded/files/2015/10/29/5485250c-8d20-409e-8a5b-0eda7a9d7b8d__snapshot29.png
> Multiple same-day events
>   
> https://git.reviewboard.kde.org/media/uploaded/files/2015/10/29/d453a01e-f9cf-4da3-8f6a-fac5aa6aadf5__snapshot18.png
> 
> 
> Thanks,
> 
> Martin Klapetek
> 
>

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/
---

(Updated Oct. 30, 2015, 5:42 p.m.)


Review request for kwin and Plasma.


Repository: kwin


Description
---

make the minimize effect work by reading taskGeometry from 
plasmawindowmanagement and returning as iconGeometry().

It still supports a single taskbar as on x11. the architecture will have to 
change somehow to allow to know from where panel we want to minimize (or if not 
secified searching for the nearest panel)
suggestions welcome :)


Diffs (updated)
-

  abstract_client.h 128c141 
  client.h f22e690 
  shell_client.h fee22c4 
  shell_client.cpp 79a1ac5 

Diff: https://git.reviewboard.kde.org/r/125873/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin


> On Oct. 30, 2015, 4:52 p.m., Thomas Lübking wrote:
> > shell_client.cpp, line 413
> > 
> >
> > just store the iterator?

kindof prefer this way, but i can do it, sure


- Marco


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/#review87753
---


On Oct. 30, 2015, 5:42 p.m., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125873/
> ---
> 
> (Updated Oct. 30, 2015, 5:42 p.m.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwin
> 
> 
> Description
> ---
> 
> make the minimize effect work by reading taskGeometry from 
> plasmawindowmanagement and returning as iconGeometry().
> 
> It still supports a single taskbar as on x11. the architecture will have to 
> change somehow to allow to know from where panel we want to minimize (or if 
> not secified searching for the nearest panel)
> suggestions welcome :)
> 
> 
> Diffs
> -
> 
>   abstract_client.h 128c141 
>   client.h f22e690 
>   shell_client.h fee22c4 
>   shell_client.cpp 79a1ac5 
> 
> Diff: https://git.reviewboard.kde.org/r/125873/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin


> On Oct. 30, 2015, 4:52 p.m., Thomas Lübking wrote:
> > shell_client.cpp, line 412
> > 
> >
> > should the panel also be tested for being on the same screen (ie. same 
> > screen takes precedence over closer, but other screen)?

yep, good idea absolutely :)

are the screens of ShellClient and of the PlasmaShellSurface accessible from 
there?


- Marco


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/#review87753
---


On Oct. 30, 2015, 4:08 p.m., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125873/
> ---
> 
> (Updated Oct. 30, 2015, 4:08 p.m.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwin
> 
> 
> Description
> ---
> 
> make the minimize effect work by reading taskGeometry from 
> plasmawindowmanagement and returning as iconGeometry().
> 
> It still supports a single taskbar as on x11. the architecture will have to 
> change somehow to allow to know from where panel we want to minimize (or if 
> not secified searching for the nearest panel)
> suggestions welcome :)
> 
> 
> Diffs
> -
> 
>   abstract_client.h 128c141 
>   client.h f22e690 
>   shell_client.h fee22c4 
>   shell_client.cpp 79a1ac5 
> 
> Diff: https://git.reviewboard.kde.org/r/125873/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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


Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/
---

(Updated Oct. 30, 2015, 5:37 p.m.)


Review request for kwin and Plasma.


Repository: kwayland


Description
---

this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
order to make the minimize effects possible.
unlike on X11, it takes relative positions and it has one geometry per panel, 
making possible to have multiple taskbars working.

however this is still not completely exposed, as internally kwin has still only 
one geometry, it will need a change in kwin itself (suggestions welcome) 
probably the rotocol will need also a minimizeTo function that takes the panel 
as argument.

another thing completely missing is tests: unfortunately the whole 
plasma-windowmanagement doesn't have any autotest yet :/


Diffs (updated)
-

  autotests/client/CMakeLists.txt 1556c47 
  autotests/client/test_wayland_shell.cpp 94cc03d 
  autotests/client/test_wayland_windowmanagement.cpp PRE-CREATION 
  src/client/plasmawindowmanagement.h abd8fa6 
  src/client/plasmawindowmanagement.cpp 1f9674c 
  src/client/plasmawindowmodel.h 5a6aac4 
  src/client/plasmawindowmodel.cpp 355ef53 
  src/client/protocols/plasma-window-management.xml ca6a7cc 
  src/client/shell.h b545c07 
  src/client/shell.cpp f4b0ca5 
  src/server/plasmashell_interface.h 9db3f52 
  src/server/plasmashell_interface.cpp d29d7bc 
  src/server/plasmawindowmanagement_interface.h 6ccc22e 
  src/server/plasmawindowmanagement_interface.cpp ad714a5 
  src/server/seat_interface.h d4f23be 
  src/server/shell_interface.h e0c5bd2 
  src/server/shell_interface.cpp 69e22e6 

Diff: https://git.reviewboard.kde.org/r/125871/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Thomas Lübking

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/#review87753
---



abstract_client.h (line 601)


cough, kate/kwrite/kdevelop btw. has this fancy feature to autofix that for 
you (and so does vim ;-)



shell_client.cpp (line 402)


hint, start with INT_MAX.
Spares you a logic-error prone bug ;-)



shell_client.cpp (line 408)


can we please go for

for (auto i = windowManagementInterface()->taskGeometries().constBegin(), 
end = windowManagementInterface()->taskGeometries().constEnd(); i != end; ++i)

instead of while loops (with random increment position)?



shell_client.cpp (line 409)


local variable, "const int distance = ..." - this ain't C-99 ;-)



shell_client.cpp (line 410)


take a close look at this line, then fix it :-)



shell_client.cpp (line 412)


should the panel also be tested for being on the same screen (ie. same 
screen takes precedence over closer, but other screen)?



shell_client.cpp (line 413)


just store the iterator?


- Thomas Lübking


On Okt. 30, 2015, 4:08 nachm., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125873/
> ---
> 
> (Updated Okt. 30, 2015, 4:08 nachm.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwin
> 
> 
> Description
> ---
> 
> make the minimize effect work by reading taskGeometry from 
> plasmawindowmanagement and returning as iconGeometry().
> 
> It still supports a single taskbar as on x11. the architecture will have to 
> change somehow to allow to know from where panel we want to minimize (or if 
> not secified searching for the nearest panel)
> suggestions welcome :)
> 
> 
> Diffs
> -
> 
>   abstract_client.h 128c141 
>   client.h f22e690 
>   shell_client.h fee22c4 
>   shell_client.cpp 79a1ac5 
> 
> Diff: https://git.reviewboard.kde.org/r/125873/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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


Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Thomas Lübking

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/#review87751
---



src/client/plasmawindowmanagement.h (line 243)


"setMinimizedGeometry[On]"?



src/client/plasmawindowmanagement.h (line 248)


"unset/forget/releaseMinmizedGeometry[On]"?



src/server/plasmawindowmanagement_interface.cpp (line 455)


if (panelSurface) ...



src/server/plasmawindowmanagement_interface.cpp (line 459)


if (p->taskGeometries.remove(.)) ...



src/server/plasmawindowmanagement_interface.cpp (line 467)


same checks here


- Thomas Lübking


On Okt. 30, 2015, 2:15 nachm., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125871/
> ---
> 
> (Updated Okt. 30, 2015, 2:15 nachm.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwayland
> 
> 
> Description
> ---
> 
> this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
> order to make the minimize effects possible.
> unlike on X11, it takes relative positions and it has one geometry per panel, 
> making possible to have multiple taskbars working.
> 
> however this is still not completely exposed, as internally kwin has still 
> only one geometry, it will need a change in kwin itself (suggestions welcome) 
> probably the rotocol will need also a minimizeTo function that takes the 
> panel as argument.
> 
> another thing completely missing is tests: unfortunately the whole 
> plasma-windowmanagement doesn't have any autotest yet :/
> 
> 
> Diffs
> -
> 
>   autotests/client/CMakeLists.txt 1556c47 
>   autotests/client/test_wayland_windowmanagement.cpp PRE-CREATION 
>   src/client/plasmawindowmanagement.h abd8fa6 
>   src/client/plasmawindowmanagement.cpp 1f9674c 
>   src/client/plasmawindowmodel.h 5a6aac4 
>   src/client/plasmawindowmodel.cpp 355ef53 
>   src/client/protocols/plasma-window-management.xml ca6a7cc 
>   src/server/plasmashell_interface.h 9db3f52 
>   src/server/plasmashell_interface.cpp d29d7bc 
>   src/server/plasmawindowmanagement_interface.h 6ccc22e 
>   src/server/plasmawindowmanagement_interface.cpp ad714a5 
> 
> Diff: https://git.reviewboard.kde.org/r/125871/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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


Jenkins-kde-ci: plasma-workspace Plasma-5.4 stable-kf5-qt5 » Linux,gcc - Build # 39 - Fixed!

2015-10-30 Thread no-reply

GENERAL INFO

BUILD SUCCESS
Build URL: 
https://build.kde.org/job/plasma-workspace%20Plasma-5.4%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/39/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Fri, 30 Oct 2015 16:20:01 +
Build duration: 17 min

CHANGE SET
Revision d3d8edf5a1166e87dc2c12903f621a3c24ac9913 by aleixpol: (themeChanged 
needs to be called on every window the panel has)
  change: edit shell/panelview.cpp
Revision 7e8aad767a250845a182166876550fb4e9701de4 by aleixpol: (Window position 
is fundamental to determining what screen it's in)
  change: edit shell/panelview.cpp
Revision 4c4beb7a1097de831c3ec6b5f5155bb65446e155 by aleixpol: (Ensure the 
DesktopView has the correct size since the beginning)
  change: edit shell/desktopview.cpp


JUNIT RESULTS

Name: (root) Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 
10 test(s)

COBERTURA RESULTS

Cobertura Coverage Report
  PACKAGES 14/14 (100%)FILES 61/71 (86%)CLASSES 61/71 (86%)LINE 2453/4040 
(61%)CONDITIONAL 1459/2270 (64%)

By packages
  
drkonqi.parser
FILES 6/10 (60%)CLASSES 6/10 (60%)LINE 302/422 (72%)CONDITIONAL 
436/495 (88%)
drkonqi.tests.backtraceparsertest
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 77/77 (100%)CONDITIONAL 
33/50 (66%)
kioslave.desktop
FILES 2/3 (67%)CLASSES 2/3 (67%)LINE 91/149 (61%)CONDITIONAL 
31/52 (60%)
kioslave.desktop.tests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 66/66 (100%)CONDITIONAL 
26/50 (52%)
klipper
FILES 12/13 (92%)CLASSES 12/13 (92%)LINE 258/379 
(68%)CONDITIONAL 109/146 (75%)
klipper.autotests
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 614/677 (91%)CONDITIONAL 
377/742 (51%)
ksmserver.screenlocker
FILES 8/11 (73%)CLASSES 8/11 (73%)LINE 460/977 (47%)CONDITIONAL 
140/219 (64%)
ksmserver.screenlocker.autotests
FILES 5/5 (100%)CLASSES 5/5 (100%)LINE 165/169 (98%)CONDITIONAL 
65/124 (52%)
ksmserver.screenlocker.greeter
FILES 2/2 (100%)CLASSES 2/2 (100%)LINE 99/144 (69%)CONDITIONAL 
36/60 (60%)
ksmserver.screenlocker.greeter.autotests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 45/45 (100%)CONDITIONAL 
34/68 (50%)
libkworkspace
FILES 2/3 (67%)CLASSES 2/3 (67%)LINE 28/610 (5%)CONDITIONAL 
23/39 (59%)
runners.bookmarks
FILES 8/8 (100%)CLASSES 8/8 (100%)LINE 87/160 (54%)CONDITIONAL 
34/56 (61%)
runners.bookmarks.browsers
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 96/100 (96%)CONDITIONAL 
84/107 (79%)
runners.bookmarks.tests
FILES 2/2 (100%)CLASSES 2/2 (100%)LINE 65/65 (100%)CONDITIONAL 
31/62 (50%)___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Jenkins-kde-ci: plasma-workspace Plasma-5.4 stable-kf5-qt5 » Linux,gcc - Build # 39 - Fixed!

2015-10-30 Thread no-reply

GENERAL INFO

BUILD SUCCESS
Build URL: 
https://build.kde.org/job/plasma-workspace%20Plasma-5.4%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/39/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Fri, 30 Oct 2015 16:20:01 +
Build duration: 17 min

CHANGE SET
Revision d3d8edf5a1166e87dc2c12903f621a3c24ac9913 by aleixpol: (themeChanged 
needs to be called on every window the panel has)
  change: edit shell/panelview.cpp
Revision 7e8aad767a250845a182166876550fb4e9701de4 by aleixpol: (Window position 
is fundamental to determining what screen it's in)
  change: edit shell/panelview.cpp
Revision 4c4beb7a1097de831c3ec6b5f5155bb65446e155 by aleixpol: (Ensure the 
DesktopView has the correct size since the beginning)
  change: edit shell/desktopview.cpp


JUNIT RESULTS

Name: (root) Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 
10 test(s)

COBERTURA RESULTS

Cobertura Coverage Report
  PACKAGES 14/14 (100%)FILES 61/71 (86%)CLASSES 61/71 (86%)LINE 2453/4040 
(61%)CONDITIONAL 1459/2270 (64%)

By packages
  
drkonqi.parser
FILES 6/10 (60%)CLASSES 6/10 (60%)LINE 302/422 (72%)CONDITIONAL 
436/495 (88%)
drkonqi.tests.backtraceparsertest
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 77/77 (100%)CONDITIONAL 
33/50 (66%)
kioslave.desktop
FILES 2/3 (67%)CLASSES 2/3 (67%)LINE 91/149 (61%)CONDITIONAL 
31/52 (60%)
kioslave.desktop.tests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 66/66 (100%)CONDITIONAL 
26/50 (52%)
klipper
FILES 12/13 (92%)CLASSES 12/13 (92%)LINE 258/379 
(68%)CONDITIONAL 109/146 (75%)
klipper.autotests
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 614/677 (91%)CONDITIONAL 
377/742 (51%)
ksmserver.screenlocker
FILES 8/11 (73%)CLASSES 8/11 (73%)LINE 460/977 (47%)CONDITIONAL 
140/219 (64%)
ksmserver.screenlocker.autotests
FILES 5/5 (100%)CLASSES 5/5 (100%)LINE 165/169 (98%)CONDITIONAL 
65/124 (52%)
ksmserver.screenlocker.greeter
FILES 2/2 (100%)CLASSES 2/2 (100%)LINE 99/144 (69%)CONDITIONAL 
36/60 (60%)
ksmserver.screenlocker.greeter.autotests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 45/45 (100%)CONDITIONAL 
34/68 (50%)
libkworkspace
FILES 2/3 (67%)CLASSES 2/3 (67%)LINE 28/610 (5%)CONDITIONAL 
23/39 (59%)
runners.bookmarks
FILES 8/8 (100%)CLASSES 8/8 (100%)LINE 87/160 (54%)CONDITIONAL 
34/56 (61%)
runners.bookmarks.browsers
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 96/100 (96%)CONDITIONAL 
84/107 (79%)
runners.bookmarks.tests
FILES 2/2 (100%)CLASSES 2/2 (100%)LINE 65/65 (100%)CONDITIONAL 
31/62 (50%)___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: Review Request 125862: Add simple calendar events plugin based on KHolidays

2015-10-30 Thread Martin Klapetek


> On Oct. 30, 2015, 7:51 a.m., Martin Gräßlin wrote:
> > CMakeLists.txt, line 31
> > 
> >
> > Should it be a required dep? I think it wasn't in 4.x? And reading the 
> > code it should be easy to have it optional as we just need to make the one 
> > add_subdirectory call conditional.

Yeah, good point, it shouldn't be.


- Martin


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125862/#review87715
---


On Oct. 29, 2015, 5:01 p.m., Martin Klapetek wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125862/
> ---
> 
> (Updated Oct. 29, 2015, 5:01 p.m.)
> 
> 
> Review request for Plasma.
> 
> 
> Repository: plasma-workspace
> 
> 
> Description
> ---
> 
> This is very simple for now as there is no configuration
> yet, so it just takes the default region (your locale)
> and shows holidays from that.
> 
> Obviously this needs a config to set up which regions
> you want to show in there, but this is a start.
> 
> 
> Diffs
> -
> 
>   CMakeLists.txt 50091ea 
>   plasmacalendarintegration/CMakeLists.txt PRE-CREATION 
>   plasmacalendarintegration/holidaysevents.h PRE-CREATION 
>   plasmacalendarintegration/holidaysevents.cpp PRE-CREATION 
> 
> Diff: https://git.reviewboard.kde.org/r/125862/diff/
> 
> 
> Testing
> ---
> 
> Holidays are properly listed in calendar applet.
> 
> 
> Thanks,
> 
> Martin Klapetek
> 
>

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


Re: Review Request 125878: fix lost QuickViewSharedEngine initialSize on initializing

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125878/#review87752
---

Ship it!


Ship It!

- Marco Martin


On Oct. 30, 2015, 5:07 a.m., Takahiro Hashimoto wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125878/
> ---
> 
> (Updated Oct. 30, 2015, 5:07 a.m.)
> 
> 
> Review request for Plasma, David Edmundson and David Faure.
> 
> 
> Repository: kdeclarative
> 
> 
> Description
> ---
> 
> After my commit 1c3f42afe17cc090372eaf45647d71495de12c19, view's initialiSize 
> value is lost (remaining 0,0 in spite of item's size). It should be set by 
> item's size for some reusing purpose (with initialSize() getter) 
> 
> Sorry again my bad commit :(
> 
> 
> Diffs
> -
> 
>   src/quickaddons/quickviewsharedengine.cpp 323cf92 
> 
> Diff: https://git.reviewboard.kde.org/r/125878/diff/
> 
> 
> Testing
> ---
> 
> build and run test
> 
> kenya888@xps13 ~/devel/kf5/build/frameworks/kdeclarative $ ninja test
> [1/1] Running tests...
> Test project /home/kenya888/devel/kf5/build/frameworks/kdeclarative
> Start 1: fullmodelaccesstest
> 1/2 Test #1: fullmodelaccesstest ..   Passed0.05 sec
> Start 2: quickviewsharedengine
> 2/2 Test #2: quickviewsharedengine    Passed0.39 sec
> 
> 100% tests passed, 0 tests failed out of 2
> 
> Total Test time (real) =   0.44 sec
> 
> --
> 
> confirmed ksplashqml works well which use QuickViewSharedEngine.
> 
> 
> Thanks,
> 
> Takahiro Hashimoto
> 
>

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/
---

(Updated Oct. 30, 2015, 4:08 p.m.)


Review request for kwin and Plasma.


Changes
---

no friends anymore


Repository: kwin


Description
---

make the minimize effect work by reading taskGeometry from 
plasmawindowmanagement and returning as iconGeometry().

It still supports a single taskbar as on x11. the architecture will have to 
change somehow to allow to know from where panel we want to minimize (or if not 
secified searching for the nearest panel)
suggestions welcome :)


Diffs (updated)
-

  abstract_client.h 128c141 
  client.h f22e690 
  shell_client.h fee22c4 
  shell_client.cpp 79a1ac5 

Diff: https://git.reviewboard.kde.org/r/125873/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125655: Xembed SNI Proxy

2015-10-30 Thread David Edmundson

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125655/
---

(Updated Oct. 30, 2015, 3:54 p.m.)


Review request for Plasma.


Repository: plasma-workspace


Description
---

The goal of this project is to make xembed system trays available in Plasma.

This is to allow legacy apps (xchat, pidgin, tuxguitar) etc. system trays[1] 
available in Plasma which only supports StatusNotifierItem [2].

Ideally we also want this to work in an xwayland session, making X system tray 
icons available even when plasmashell only has a wayland connection.

How it works (in theory)

* We register a window as a system tray container
* We render embeded windows composited offscreen
* We render contents into an image and send this over DBus via the SNI protocol
* XDamage events trigger a repaint
* Activate and context menu events are replyed via X send event into the 
embedded container as left and right clicks


Code is a mix of hacks and bodges bashing client apps into place, and I happily 
acknowledge it looks pretty bad. Unfotunately most of it seems to be needed, 
but I'd love to be proved wrong on most of it.

---

CMakeLists changes are obviously currently wrong, I can strip half of 
find_packages and I need an add_subdirectory in the root file, but it's easier 
for me to sync with the separate repo mirror this way till we're close to 
merging. I expect this to take quite some revisions.


Diffs (updated)
-

  xembed-sni-proxy/xembedsniproxy.desktop PRE-CREATION 
  xembed-sni-proxy/xcbutils.h PRE-CREATION 
  xembed-sni-proxy/sniproxy.cpp PRE-CREATION 
  xembed-sni-proxy/snidbus.cpp PRE-CREATION 
  xembed-sni-proxy/sniproxy.h PRE-CREATION 
  xembed-sni-proxy/org.kde.StatusNotifierWatcher.xml PRE-CREATION 
  xembed-sni-proxy/snidbus.h PRE-CREATION 
  xembed-sni-proxy/org.kde.StatusNotifierItem.xml PRE-CREATION 
  xembed-sni-proxy/main.cpp PRE-CREATION 
  xembed-sni-proxy/fdoselectionmanager.cpp PRE-CREATION 
  xembed-sni-proxy/fdoselectionmanager.h PRE-CREATION 
  CMakeLists.txt 50091ea8ffb01177d34e18217b929cfb9ede3d23 
  xembed-sni-proxy/CMakeLists.txt PRE-CREATION 
  xembed-sni-proxy/Readme.md PRE-CREATION 

Diff: https://git.reviewboard.kde.org/r/125655/diff/


Testing
---


Thanks,

David Edmundson

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Martin Gräßlin


> On Oct. 30, 2015, 3:32 p.m., Martin Gräßlin wrote:
> > abstract_client.h, line 830
> > 
> >
> > why friend an inheriting class?
> 
> Marco Martin wrote:
> because m_windowManagementInterface is private in AbstractClient (should 
> be protected?)

adding a protected method which returns it sounds like a better solution than 
friending


- Martin


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/#review87746
---


On Oct. 30, 2015, 4:31 p.m., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125873/
> ---
> 
> (Updated Oct. 30, 2015, 4:31 p.m.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwin
> 
> 
> Description
> ---
> 
> make the minimize effect work by reading taskGeometry from 
> plasmawindowmanagement and returning as iconGeometry().
> 
> It still supports a single taskbar as on x11. the architecture will have to 
> change somehow to allow to know from where panel we want to minimize (or if 
> not secified searching for the nearest panel)
> suggestions welcome :)
> 
> 
> Diffs
> -
> 
>   abstract_client.h 128c141 
>   client.h 4fbaa5f 
>   shell_client.h fee22c4 
>   shell_client.cpp b466f97 
> 
> Diff: https://git.reviewboard.kde.org/r/125873/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/
---

(Updated Oct. 30, 2015, 3:31 p.m.)


Review request for kwin and Plasma.


Repository: kwin


Description
---

make the minimize effect work by reading taskGeometry from 
plasmawindowmanagement and returning as iconGeometry().

It still supports a single taskbar as on x11. the architecture will have to 
change somehow to allow to know from where panel we want to minimize (or if not 
secified searching for the nearest panel)
suggestions welcome :)


Diffs (updated)
-

  abstract_client.h 128c141 
  client.h 4fbaa5f 
  shell_client.h fee22c4 
  shell_client.cpp b466f97 

Diff: https://git.reviewboard.kde.org/r/125873/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin


> On Oct. 30, 2015, 2:32 p.m., Martin Gräßlin wrote:
> > main_wayland.cpp, lines 378-380
> > 
> >
> > only if you want to break kwin for everybody with an up to date Qt 5.6

ah, right sorry, forgot that :(


> On Oct. 30, 2015, 2:32 p.m., Martin Gräßlin wrote:
> > abstract_client.h, line 830
> > 
> >
> > why friend an inheriting class?

because m_windowManagementInterface is private in AbstractClient (should be 
protected?)


- Marco


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/#review87746
---


On Oct. 30, 2015, 1:43 p.m., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125873/
> ---
> 
> (Updated Oct. 30, 2015, 1:43 p.m.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwin
> 
> 
> Description
> ---
> 
> make the minimize effect work by reading taskGeometry from 
> plasmawindowmanagement and returning as iconGeometry().
> 
> It still supports a single taskbar as on x11. the architecture will have to 
> change somehow to allow to know from where panel we want to minimize (or if 
> not secified searching for the nearest panel)
> suggestions welcome :)
> 
> 
> Diffs
> -
> 
>   shell_client.cpp b466f97 
>   shell_client.h fee22c4 
>   abstract_client.h 128c141 
>   main_wayland.cpp 5dc7e9f 
> 
> Diff: https://git.reviewboard.kde.org/r/125873/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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


[Differential] [Updated, 917 lines] D409: new mobile components

2015-10-30 Thread mart (Marco Martin)
mart updated this revision to Diff 1110.

REPOSITORY
  rPLASMAMOBILE plasma-mobile

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D409?vs=1066&id=1110

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

AFFECTED FILES
  components/mobilecomponents/ActionGroup.qml
  components/mobilecomponents/ApplicationWindow.qml
  components/mobilecomponents/CMakeLists.txt
  components/mobilecomponents/ContextDrawer.qml
  components/mobilecomponents/GlobalDrawer.qml
  components/mobilecomponents/Page.qml
  components/mobilecomponents/examples/ActionGroup.qml
  components/mobilecomponents/examples/ApplicationWindow.qml
  components/mobilecomponents/examples/ContextDrawer.qml
  components/mobilecomponents/examples/ExampleApp.qml
  components/mobilecomponents/examples/GlobalDrawer.qml
  components/mobilecomponents/examples/Page.qml
  components/mobilecomponents/examples/PageRow.qml
  components/mobilecomponents/qmldir

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: mart, Plasma: Mobile, davidedmundson
Cc: davidedmundson, plasma-devel
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


Re: HIG and components API

2015-10-30 Thread Marco Martin
On Thu, Oct 22, 2015 at 7:15 PM, Thomas Pfeiffer
 wrote:
>
> If you're looking also for input on the HIG compliance, screenshots are
> helpful :)

sorry it taken a long time:
https://www.youtube.com/watch?v=WfhcWRHCEtA

(ignore the fixed scrollbars, that's because is on a laptop, and the
white rectangle in the left panel)

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Martin Gräßlin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/#review87746
---



abstract_client.h (line 830)


why friend an inheriting class?



main_wayland.cpp (lines 378 - 380)


only if you want to break kwin for everybody with an up to date Qt 5.6



shell_client.h (lines 41 - 47)


instead of duplicating the propery, I suggest to move it to AbstractClient 
and add the method as a virtual.



shell_client.cpp (line 364)


auto



shell_client.cpp (line 374)


this crashes if we don't find a candidatePanel


- Martin Gräßlin


On Oct. 30, 2015, 2:43 p.m., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125873/
> ---
> 
> (Updated Oct. 30, 2015, 2:43 p.m.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwin
> 
> 
> Description
> ---
> 
> make the minimize effect work by reading taskGeometry from 
> plasmawindowmanagement and returning as iconGeometry().
> 
> It still supports a single taskbar as on x11. the architecture will have to 
> change somehow to allow to know from where panel we want to minimize (or if 
> not secified searching for the nearest panel)
> suggestions welcome :)
> 
> 
> Diffs
> -
> 
>   shell_client.cpp b466f97 
>   shell_client.h fee22c4 
>   abstract_client.h 128c141 
>   main_wayland.cpp 5dc7e9f 
> 
> Diff: https://git.reviewboard.kde.org/r/125873/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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


Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/
---

(Updated Oct. 30, 2015, 2:15 p.m.)


Review request for kwin and Plasma.


Changes
---

* manage panels going away
* add api to remove the position for a given panel (use case: either a taskbar 
gets removed or changes filtering) (maybe putting it in 
plasmawindowmanageentinterface to instead remove references for this panel in 
all windowinterfaces everywhere?)


Repository: kwayland


Description
---

this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
order to make the minimize effects possible.
unlike on X11, it takes relative positions and it has one geometry per panel, 
making possible to have multiple taskbars working.

however this is still not completely exposed, as internally kwin has still only 
one geometry, it will need a change in kwin itself (suggestions welcome) 
probably the rotocol will need also a minimizeTo function that takes the panel 
as argument.

another thing completely missing is tests: unfortunately the whole 
plasma-windowmanagement doesn't have any autotest yet :/


Diffs (updated)
-

  autotests/client/CMakeLists.txt 1556c47 
  autotests/client/test_wayland_windowmanagement.cpp PRE-CREATION 
  src/client/plasmawindowmanagement.h abd8fa6 
  src/client/plasmawindowmanagement.cpp 1f9674c 
  src/client/plasmawindowmodel.h 5a6aac4 
  src/client/plasmawindowmodel.cpp 355ef53 
  src/client/protocols/plasma-window-management.xml ca6a7cc 
  src/server/plasmashell_interface.h 9db3f52 
  src/server/plasmashell_interface.cpp d29d7bc 
  src/server/plasmawindowmanagement_interface.h 6ccc22e 
  src/server/plasmawindowmanagement_interface.cpp ad714a5 

Diff: https://git.reviewboard.kde.org/r/125871/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/
---

(Updated Oct. 30, 2015, 1:43 p.m.)


Review request for kwin and Plasma.


Repository: kwin


Description
---

make the minimize effect work by reading taskGeometry from 
plasmawindowmanagement and returning as iconGeometry().

It still supports a single taskbar as on x11. the architecture will have to 
change somehow to allow to know from where panel we want to minimize (or if not 
secified searching for the nearest panel)
suggestions welcome :)


Diffs (updated)
-

  shell_client.cpp b466f97 
  shell_client.h fee22c4 
  abstract_client.h 128c141 
  main_wayland.cpp 5dc7e9f 

Diff: https://git.reviewboard.kde.org/r/125873/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Marco Martin


> On Oct. 29, 2015, 8:32 p.m., Thomas Lübking wrote:
> > What's the point of client relative geometries?
> > 
> > Afaics, there'll be two "problematic" scenarios.
> > 
> > 1) >= 2 taskbars on >= 1 screens, the window is minimized from the taskbar
> > 2) >= 2 taskbars on >= 2 screens, the window is NOT minimized from the 
> > taskbar (but the deco button, or wmctrl etc.)
> > 
> > (1) can be _easily_ resolved by the minimizing taskbar applet updating the 
> > (one is actually sufficient here) geometry right before minimizing the 
> > client
> > 
> > The challenge of (2) is to select a taskbar where to minimize to itfp (I 
> > guess one does not want to minimize to two regions at once, seems confusing)
> > The reasonable approach seems to minimize to any icon rect that is on the 
> > same screen the window is on (WMs free choice), so we need a list of global 
> > (or tagged screen relative) geometries where the WM can look for eg. the 
> > closes match on the current ("active") or the windows screen.
> > 
> > The only benefit of a window relative geometry would be (less overhead on) 
> > tracking a moving client while the window minimizes - but the only scenario 
> > I see here is an autohiding panel and then the only overhead (if one wants 
> > to buy into such feature at all) would be an update of the icon rect from 
> > the on-screen to the off-screen position of the panel.
> > 
> > Otoh, keeping a reference to a surface around
> > a) requires a surface itfp
> > b) sounds *extremely* bug prone, eg.:
> >- I don't see where the surface removal is tracked in the patch, so we 
> > could end up with a dangeling pointer.
> >- Another case is where the taskbar is moved from eg. a panel to the 
> > desktop - we'd have it in the desktop and -outdated- the panel at the same 
> > time)
> >- Also what if I add a taskbar to the top and the bottom of my desktop? 
> > That's not supported, is it?
> > 
> > => Imo we *need* one icon rect per screen.
> > It would be cool to have one "per taskbar" (calc closest distance on 
> > unrelated minimizations)
> > But I object the approach to assign the rects to particular surfaces.
> 
> Martin Gräßlin wrote:
> > It would be cool to have one "per taskbar" (calc closest distance on 
> unrelated minimizations)
> 
> this is kind of the idea here. Marco and I had discussed the needs and 
> came up with "each panel needs to set the geometry". So that KWin knows all 
> the possible geometries (we cannot use it yet, but well that's a different 
> problem). That's what the patch does: Plasma can set for different windows 
> (WindowManagement) an icon geometry relative to the a PlasmaSurface. My 
> thought was doing it the other way around, but that sounds to be details.
> 
> Thomas Lübking wrote:
> But surface != taskbar, is it?
> A systematic problem is the cooperative approach to keep the list clean 
> (ie. a buggy or crashing client shall not leave false rects behind forever, 
> kwin cannot be restarted to clear the list)
> 
> Assigning rects to windows/surfaces should be capable of catching crashy, 
> but not buggy clients - nor can it cover multiple taskbars per surface.
> Also I'd avoid resolving cached client pointers here (or you'd have to 
> look them up)
> 
> - I guess we won't get around resolving the surface (since it 
> doesn't/isn't supposed to know its position on screen?)
> - I'm not sure whether "one taskbar per surface" is a reasonable 
> restriction (my opinion still is "zero taskbars per nowhere" ;-)
> - The patch definitively lacks cleanup functionality, ie. at least a 
> cooperative solution to withdraw the rect (taskbar -or entry- removed from 
> panel) and hash maintainace ("is the surface pointer still valid at all"?)
> - If the panel <=> taskbar assumption isn't sufficient (additional 
> systray entry case?) we'll require further mapping (UID on top of surface) 
> and maintainance mechanisms (to not end up with 100 rects on the same surface)
> 
> Marco Martin wrote:
> I can see the problem of having leftover geometries due to clients 
> misbehaving.
> in the latest version at least removes those for panels that go away.
> An alternative may be instead the hash plasmawindow/geometry in 
> plasmasurfaceinterface instead, on kwayland side it may be slightly more 
> elegant.
> however i don't know how to make it work correctly from kwin, it shuld 
> iterate over all the existing plasmashellsurfaceinterfaces, that doesn't seem 
> much pretty

having the limit of one taskbar per panel is not great, but i think it's quite 
reasonable to expect that (the systray shouldn't really have actual 
applications in it)


- Marco


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/#review87697
---


On Oct. 30, 2015, 1:24 p.m., Marco Mar

Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Marco Martin


> On Oct. 29, 2015, 8:32 p.m., Thomas Lübking wrote:
> > What's the point of client relative geometries?
> > 
> > Afaics, there'll be two "problematic" scenarios.
> > 
> > 1) >= 2 taskbars on >= 1 screens, the window is minimized from the taskbar
> > 2) >= 2 taskbars on >= 2 screens, the window is NOT minimized from the 
> > taskbar (but the deco button, or wmctrl etc.)
> > 
> > (1) can be _easily_ resolved by the minimizing taskbar applet updating the 
> > (one is actually sufficient here) geometry right before minimizing the 
> > client
> > 
> > The challenge of (2) is to select a taskbar where to minimize to itfp (I 
> > guess one does not want to minimize to two regions at once, seems confusing)
> > The reasonable approach seems to minimize to any icon rect that is on the 
> > same screen the window is on (WMs free choice), so we need a list of global 
> > (or tagged screen relative) geometries where the WM can look for eg. the 
> > closes match on the current ("active") or the windows screen.
> > 
> > The only benefit of a window relative geometry would be (less overhead on) 
> > tracking a moving client while the window minimizes - but the only scenario 
> > I see here is an autohiding panel and then the only overhead (if one wants 
> > to buy into such feature at all) would be an update of the icon rect from 
> > the on-screen to the off-screen position of the panel.
> > 
> > Otoh, keeping a reference to a surface around
> > a) requires a surface itfp
> > b) sounds *extremely* bug prone, eg.:
> >- I don't see where the surface removal is tracked in the patch, so we 
> > could end up with a dangeling pointer.
> >- Another case is where the taskbar is moved from eg. a panel to the 
> > desktop - we'd have it in the desktop and -outdated- the panel at the same 
> > time)
> >- Also what if I add a taskbar to the top and the bottom of my desktop? 
> > That's not supported, is it?
> > 
> > => Imo we *need* one icon rect per screen.
> > It would be cool to have one "per taskbar" (calc closest distance on 
> > unrelated minimizations)
> > But I object the approach to assign the rects to particular surfaces.
> 
> Martin Gräßlin wrote:
> > It would be cool to have one "per taskbar" (calc closest distance on 
> unrelated minimizations)
> 
> this is kind of the idea here. Marco and I had discussed the needs and 
> came up with "each panel needs to set the geometry". So that KWin knows all 
> the possible geometries (we cannot use it yet, but well that's a different 
> problem). That's what the patch does: Plasma can set for different windows 
> (WindowManagement) an icon geometry relative to the a PlasmaSurface. My 
> thought was doing it the other way around, but that sounds to be details.
> 
> Thomas Lübking wrote:
> But surface != taskbar, is it?
> A systematic problem is the cooperative approach to keep the list clean 
> (ie. a buggy or crashing client shall not leave false rects behind forever, 
> kwin cannot be restarted to clear the list)
> 
> Assigning rects to windows/surfaces should be capable of catching crashy, 
> but not buggy clients - nor can it cover multiple taskbars per surface.
> Also I'd avoid resolving cached client pointers here (or you'd have to 
> look them up)
> 
> - I guess we won't get around resolving the surface (since it 
> doesn't/isn't supposed to know its position on screen?)
> - I'm not sure whether "one taskbar per surface" is a reasonable 
> restriction (my opinion still is "zero taskbars per nowhere" ;-)
> - The patch definitively lacks cleanup functionality, ie. at least a 
> cooperative solution to withdraw the rect (taskbar -or entry- removed from 
> panel) and hash maintainace ("is the surface pointer still valid at all"?)
> - If the panel <=> taskbar assumption isn't sufficient (additional 
> systray entry case?) we'll require further mapping (UID on top of surface) 
> and maintainance mechanisms (to not end up with 100 rects on the same surface)

I can see the problem of having leftover geometries due to clients misbehaving.
in the latest version at least removes those for panels that go away.
An alternative may be instead the hash plasmawindow/geometry in 
plasmasurfaceinterface instead, on kwayland side it may be slightly more 
elegant.
however i don't know how to make it work correctly from kwin, it shuld iterate 
over all the existing plasmashellsurfaceinterfaces, that doesn't seem much 
pretty


- Marco


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/#review87697
---


On Oct. 30, 2015, 1:24 p.m., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125871/
> -

Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/
---

(Updated Oct. 30, 2015, 1:24 p.m.)


Review request for kwin and Plasma.


Repository: kwayland


Description
---

this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
order to make the minimize effects possible.
unlike on X11, it takes relative positions and it has one geometry per panel, 
making possible to have multiple taskbars working.

however this is still not completely exposed, as internally kwin has still only 
one geometry, it will need a change in kwin itself (suggestions welcome) 
probably the rotocol will need also a minimizeTo function that takes the panel 
as argument.

another thing completely missing is tests: unfortunately the whole 
plasma-windowmanagement doesn't have any autotest yet :/


Diffs (updated)
-

  autotests/client/CMakeLists.txt 1556c47 
  autotests/client/test_wayland_windowmanagement.cpp PRE-CREATION 
  src/client/plasmawindowmanagement.h abd8fa6 
  src/client/plasmawindowmanagement.cpp 1f9674c 
  src/client/plasmawindowmodel.h 5a6aac4 
  src/client/plasmawindowmodel.cpp 355ef53 
  src/client/protocols/plasma-window-management.xml ca6a7cc 
  src/server/plasmashell_interface.h 9db3f52 
  src/server/plasmashell_interface.cpp d29d7bc 
  src/server/plasmawindowmanagement_interface.h 6ccc22e 
  src/server/plasmawindowmanagement_interface.cpp ad714a5 

Diff: https://git.reviewboard.kde.org/r/125871/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125873: preliminar support for task geometries in wayland

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125873/
---

(Updated Oct. 30, 2015, 1:13 p.m.)


Review request for kwin and Plasma.


Repository: kwin


Description
---

make the minimize effect work by reading taskGeometry from 
plasmawindowmanagement and returning as iconGeometry().

It still supports a single taskbar as on x11. the architecture will have to 
change somehow to allow to know from where panel we want to minimize (or if not 
secified searching for the nearest panel)
suggestions welcome :)


Diffs (updated)
-

  shell_client.cpp b466f97 
  shell_client.h fee22c4 
  main_wayland.cpp 5dc7e9f 
  abstract_client.h 128c141 

Diff: https://git.reviewboard.kde.org/r/125873/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/
---

(Updated Oct. 30, 2015, 1:13 p.m.)


Review request for kwin and Plasma.


Repository: kwayland


Description
---

this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
order to make the minimize effects possible.
unlike on X11, it takes relative positions and it has one geometry per panel, 
making possible to have multiple taskbars working.

however this is still not completely exposed, as internally kwin has still only 
one geometry, it will need a change in kwin itself (suggestions welcome) 
probably the rotocol will need also a minimizeTo function that takes the panel 
as argument.

another thing completely missing is tests: unfortunately the whole 
plasma-windowmanagement doesn't have any autotest yet :/


Diffs (updated)
-

  src/server/plasmawindowmanagement_interface.cpp ad714a5 
  src/server/plasmawindowmanagement_interface.h 6ccc22e 
  src/server/plasmashell_interface.h 9db3f52 
  src/server/plasmashell_interface.cpp d29d7bc 
  src/client/protocols/plasma-window-management.xml ca6a7cc 
  src/client/plasmawindowmodel.cpp 355ef53 
  src/client/plasmawindowmodel.h 5a6aac4 
  src/client/plasmawindowmanagement.cpp 1f9674c 
  src/client/plasmawindowmanagement.h abd8fa6 
  autotests/client/test_wayland_windowmanagement.cpp PRE-CREATION 
  autotests/client/CMakeLists.txt 1556c47 

Diff: https://git.reviewboard.kde.org/r/125871/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125851: [kscreenlocker] Remove KWorkspace dependency

2015-10-30 Thread Bhushan Shah


> On Oct. 29, 2015, 2:20 p.m., Martin Gräßlin wrote:
> > Ship It!

Submitted in 
http://commits.kde.org/plasma-workspace/ab258330725cc03af3a90c721e3dc684864d8cf1
 on behalf of Kai, though forgot review:


- Bhushan


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125851/#review87651
---


On Oct. 29, 2015, 2:31 a.m., Kai Uwe Broulik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125851/
> ---
> 
> (Updated Oct. 29, 2015, 2:31 a.m.)
> 
> 
> Review request for Plasma and Martin Gräßlin.
> 
> 
> Repository: plasma-workspace
> 
> 
> Description
> ---
> 
> Removes the sessions stuff
> 
> 
> Diffs
> -
> 
>   ksmserver/screenlocker/greeter/CMakeLists.txt e6768f0 
>   ksmserver/screenlocker/greeter/greeterapp.cpp a88b61a 
>   ksmserver/screenlocker/greeter/sessions.h 8a4c042 
>   ksmserver/screenlocker/greeter/sessions.cpp 5f831d5 
> 
> Diff: https://git.reviewboard.kde.org/r/125851/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Kai Uwe Broulik
> 
>

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


Re: Review Request 125774: [Lock Screen] Use org.kde.plasma.private.sessions for User Switcher

2015-10-30 Thread Kai Uwe Broulik

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125774/
---

(Updated Oct. 30, 2015, 12:09 p.m.)


Status
--

This change has been marked as submitted.


Review request for Plasma and Martin Gräßlin.


Changes
---

Submitted with commit 987f4f76030d1dce5729285df3eb595d50951b04 by Bhushan Shah 
on behalf of Kai Uwe Broulik to branch master.


Repository: plasma-workspace


Description
---

This migrates the Lock Screen qml from using ksmserver's Session model to the 
new one provided by components.

Changes:

* It now shows the user avatar and full name in the user switcher

* It only offers to switch sessions if there are any

I would like to remove the sessions model stuff from the screenlocker greeter 
(given it's unused then and would bitrot), however we probably cannot do this 
or else we break 3rd party look and feel packages.


Diffs
-

  lookandfeel/contents/components/UserSelect.qml 007a118 
  lookandfeel/contents/lockscreen/ChangeSession.qml 58974f6 
  lookandfeel/contents/lockscreen/LockScreen.qml 3a78a5f 
  lookandfeel/contents/lockscreen/MainBlock.qml 6d39a86 

Diff: https://git.reviewboard.kde.org/r/125774/diff/


Testing
---

Switching users (both to other X and TTY) as well as creating a new session 
works.
The model does not update, however, meaning if you log in elsewhere the "Switch 
session" button won't magically appear while the screen is locked. I don't 
think the old model did that either.

Also, when cancelling the user switch, it will scroll the view back to the 
first item so you're not stranded with two buttons with the user scrolled out 
of the view with no indication (I think there was a bug report and the code was 
there, it just tried to reset the wrong index property)


Thanks,

Kai Uwe Broulik

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


Re: Review Request 124980: Add org.kde.plasma.private.sessions with a SessionModel

2015-10-30 Thread Kai Uwe Broulik

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124980/
---

(Updated Oct. 30, 2015, 12:09 p.m.)


Status
--

This change has been marked as submitted.


Review request for Plasma and Martin Gräßlin.


Changes
---

Submitted with commit 667ed80cbe9866c87f238cd1a54516820fb8da83 by Bhushan Shah 
on behalf of Kai Uwe Broulik to branch master.


Repository: plasma-workspace


Description
---

This way it can be used in the lock screen, user switcher, and a user switcher 
plasmoid I'm planning.

Compared to the one in the lock screen it can also get the user's full name and 
avatar, and some other information.

Perhaps we could also try to have it wait for the screen to actually lock 
before switching sessions?


Diffs
-

  components/CMakeLists.txt 21fc61c 
  components/sessionsprivate/CMakeLists.txt PRE-CREATION 
  components/sessionsprivate/qmldir PRE-CREATION 
  components/sessionsprivate/sessionsmodel.h PRE-CREATION 
  components/sessionsprivate/sessionsmodel.cpp PRE-CREATION 
  components/sessionsprivate/sessionsprivateplugin.h PRE-CREATION 
  components/sessionsprivate/sessionsprivateplugin.cpp PRE-CREATION 

Diff: https://git.reviewboard.kde.org/r/124980/diff/


Testing
---

Lists my sessions, allows to switch between them and start new ones. Locking 
when creating a new session is missing.


Thanks,

Kai Uwe Broulik

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


Re: Review Request 125622: Use better guard against recursion when changing volume with sliders

2015-10-30 Thread David Rosca

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125622/
---

(Updated Oct. 30, 2015, 5:54 a.m.)


Status
--

This change has been marked as submitted.


Review request for Plasma.


Repository: plasma-pa


Description
---

As noted in https://git.reviewboard.kde.org/r/125088/, this should fix 
acessibility on volume sliders.
This also fixes changing the volume with keyboard (when slider has focus).


Diffs
-

  applet/contents/ui/ListItemBase.qml 54f6eb0 
  src/kcm/package/contents/ui/VolumeSlider.qml da77315 

Diff: https://git.reviewboard.kde.org/r/125622/diff/


Testing
---

Changing volume in applet still works + it fixes changing volume in kcm (i 
broke it with last commit - there is no setVolume() in kcm VolumeSlider).


Thanks,

David Rosca

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


Re: Review Request 125622: Use better guard against recursion when changing volume with sliders

2015-10-30 Thread Jeremy Whiting

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125622/#review87738
---


Sorry I put the wrong review number on the commit for 125662

- Jeremy Whiting


On Oct. 15, 2015, 8:12 a.m., David Rosca wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125622/
> ---
> 
> (Updated Oct. 15, 2015, 8:12 a.m.)
> 
> 
> Review request for Plasma.
> 
> 
> Repository: plasma-pa
> 
> 
> Description
> ---
> 
> As noted in https://git.reviewboard.kde.org/r/125088/, this should fix 
> acessibility on volume sliders.
> This also fixes changing the volume with keyboard (when slider has focus).
> 
> 
> Diffs
> -
> 
>   applet/contents/ui/ListItemBase.qml 54f6eb0 
>   src/kcm/package/contents/ui/VolumeSlider.qml da77315 
> 
> Diff: https://git.reviewboard.kde.org/r/125622/diff/
> 
> 
> Testing
> ---
> 
> Changing volume in applet still works + it fixes changing volume in kcm (i 
> broke it with last commit - there is no setVolume() in kcm VolumeSlider).
> 
> 
> Thanks,
> 
> David Rosca
> 
>

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


Re: Review Request 125662: mangonel: Initial port to Qt5/KF5

2015-10-30 Thread Jeremy Whiting

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125662/
---

(Updated Oct. 30, 2015, 5:53 a.m.)


Status
--

This change has been marked as submitted.


Review request for Plasma and Martin Tobias Holmedahl Sandsmark.


Repository: mangonel


Description
---

Port of Mangonel to Qt5/KF5


Diffs
-

  CMakeLists.txt fec95da 
  Label.cpp 136f70b 
  Mangonel.h 9c8a32f 
  Mangonel.cpp 63e10ab 
  main.cpp 1b0c4a3 
  providers/Applications.cpp 7674a97 
  providers/Paths.cpp 713aba3 

Diff: https://git.reviewboard.kde.org/r/125662/diff/


Testing
---

It builds and runs, but looks a bit strange since it's a plani QWidget. (Maybe 
we could say it's using Material design and call it good, dunno :p)


File Attachments


screenshot
  
https://git.reviewboard.kde.org/media/uploaded/files/2015/10/16/2f8f36d8-dea2-4679-8826-96ebbaa8c8e9__mangonel.png


Thanks,

Jeremy Whiting

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


Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Marco Martin

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/
---

(Updated Oct. 30, 2015, 11:29 a.m.)


Review request for kwin and Plasma.


Changes
---

added a test case


Repository: kwayland


Description
---

this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
order to make the minimize effects possible.
unlike on X11, it takes relative positions and it has one geometry per panel, 
making possible to have multiple taskbars working.

however this is still not completely exposed, as internally kwin has still only 
one geometry, it will need a change in kwin itself (suggestions welcome) 
probably the rotocol will need also a minimizeTo function that takes the panel 
as argument.

another thing completely missing is tests: unfortunately the whole 
plasma-windowmanagement doesn't have any autotest yet :/


Diffs (updated)
-

  autotests/client/test_wayland_windowmanagement.cpp PRE-CREATION 
  src/client/plasmawindowmanagement.h abd8fa6 
  src/client/plasmawindowmanagement.cpp 1f9674c 
  src/client/plasmawindowmodel.h 5a6aac4 
  src/client/plasmawindowmodel.cpp 355ef53 
  src/server/plasmashell_interface.cpp d29d7bc 
  src/server/plasmawindowmanagement_interface.h 6ccc22e 
  src/server/plasmawindowmanagement_interface.cpp ad714a5 
  src/client/protocols/plasma-window-management.xml ca6a7cc 
  src/server/plasmashell_interface.h 9db3f52 
  autotests/client/CMakeLists.txt 1556c47 

Diff: https://git.reviewboard.kde.org/r/125871/diff/


Testing
---


Thanks,

Marco Martin

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


Re: Review Request 125662: mangonel: Initial port to Qt5/KF5

2015-10-30 Thread Martin Tobias Holmedahl Sandsmark

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125662/#review87736
---

Ship it!


Ship It!

- Martin Tobias Holmedahl Sandsmark


On Oct. 16, 2015, 4:04 p.m., Jeremy Whiting wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125662/
> ---
> 
> (Updated Oct. 16, 2015, 4:04 p.m.)
> 
> 
> Review request for Plasma and Martin Tobias Holmedahl Sandsmark.
> 
> 
> Repository: mangonel
> 
> 
> Description
> ---
> 
> Port of Mangonel to Qt5/KF5
> 
> 
> Diffs
> -
> 
>   CMakeLists.txt fec95da 
>   Label.cpp 136f70b 
>   Mangonel.h 9c8a32f 
>   Mangonel.cpp 63e10ab 
>   main.cpp 1b0c4a3 
>   providers/Applications.cpp 7674a97 
>   providers/Paths.cpp 713aba3 
> 
> Diff: https://git.reviewboard.kde.org/r/125662/diff/
> 
> 
> Testing
> ---
> 
> It builds and runs, but looks a bit strange since it's a plani QWidget. 
> (Maybe we could say it's using Material design and call it good, dunno :p)
> 
> 
> File Attachments
> 
> 
> screenshot
>   
> https://git.reviewboard.kde.org/media/uploaded/files/2015/10/16/2f8f36d8-dea2-4679-8826-96ebbaa8c8e9__mangonel.png
> 
> 
> Thanks,
> 
> Jeremy Whiting
> 
>

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


Re: Review Request 125878: fix lost QuickViewSharedEngine initialSize on initializing

2015-10-30 Thread Aleix Pol Gonzalez

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125878/#review87734
---


+1

- Aleix Pol Gonzalez


On Oct. 30, 2015, 6:07 a.m., Takahiro Hashimoto wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125878/
> ---
> 
> (Updated Oct. 30, 2015, 6:07 a.m.)
> 
> 
> Review request for Plasma, David Edmundson and David Faure.
> 
> 
> Repository: kdeclarative
> 
> 
> Description
> ---
> 
> After my commit 1c3f42afe17cc090372eaf45647d71495de12c19, view's initialiSize 
> value is lost (remaining 0,0 in spite of item's size). It should be set by 
> item's size for some reusing purpose (with initialSize() getter) 
> 
> Sorry again my bad commit :(
> 
> 
> Diffs
> -
> 
>   src/quickaddons/quickviewsharedengine.cpp 323cf92 
> 
> Diff: https://git.reviewboard.kde.org/r/125878/diff/
> 
> 
> Testing
> ---
> 
> build and run test
> 
> kenya888@xps13 ~/devel/kf5/build/frameworks/kdeclarative $ ninja test
> [1/1] Running tests...
> Test project /home/kenya888/devel/kf5/build/frameworks/kdeclarative
> Start 1: fullmodelaccesstest
> 1/2 Test #1: fullmodelaccesstest ..   Passed0.05 sec
> Start 2: quickviewsharedengine
> 2/2 Test #2: quickviewsharedengine    Passed0.39 sec
> 
> 100% tests passed, 0 tests failed out of 2
> 
> Total Test time (real) =   0.44 sec
> 
> --
> 
> confirmed ksplashqml works well which use QuickViewSharedEngine.
> 
> 
> Thanks,
> 
> Takahiro Hashimoto
> 
>

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


Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Thomas Lübking


> On Okt. 29, 2015, 8:32 nachm., Thomas Lübking wrote:
> > What's the point of client relative geometries?
> > 
> > Afaics, there'll be two "problematic" scenarios.
> > 
> > 1) >= 2 taskbars on >= 1 screens, the window is minimized from the taskbar
> > 2) >= 2 taskbars on >= 2 screens, the window is NOT minimized from the 
> > taskbar (but the deco button, or wmctrl etc.)
> > 
> > (1) can be _easily_ resolved by the minimizing taskbar applet updating the 
> > (one is actually sufficient here) geometry right before minimizing the 
> > client
> > 
> > The challenge of (2) is to select a taskbar where to minimize to itfp (I 
> > guess one does not want to minimize to two regions at once, seems confusing)
> > The reasonable approach seems to minimize to any icon rect that is on the 
> > same screen the window is on (WMs free choice), so we need a list of global 
> > (or tagged screen relative) geometries where the WM can look for eg. the 
> > closes match on the current ("active") or the windows screen.
> > 
> > The only benefit of a window relative geometry would be (less overhead on) 
> > tracking a moving client while the window minimizes - but the only scenario 
> > I see here is an autohiding panel and then the only overhead (if one wants 
> > to buy into such feature at all) would be an update of the icon rect from 
> > the on-screen to the off-screen position of the panel.
> > 
> > Otoh, keeping a reference to a surface around
> > a) requires a surface itfp
> > b) sounds *extremely* bug prone, eg.:
> >- I don't see where the surface removal is tracked in the patch, so we 
> > could end up with a dangeling pointer.
> >- Another case is where the taskbar is moved from eg. a panel to the 
> > desktop - we'd have it in the desktop and -outdated- the panel at the same 
> > time)
> >- Also what if I add a taskbar to the top and the bottom of my desktop? 
> > That's not supported, is it?
> > 
> > => Imo we *need* one icon rect per screen.
> > It would be cool to have one "per taskbar" (calc closest distance on 
> > unrelated minimizations)
> > But I object the approach to assign the rects to particular surfaces.
> 
> Martin Gräßlin wrote:
> > It would be cool to have one "per taskbar" (calc closest distance on 
> unrelated minimizations)
> 
> this is kind of the idea here. Marco and I had discussed the needs and 
> came up with "each panel needs to set the geometry". So that KWin knows all 
> the possible geometries (we cannot use it yet, but well that's a different 
> problem). That's what the patch does: Plasma can set for different windows 
> (WindowManagement) an icon geometry relative to the a PlasmaSurface. My 
> thought was doing it the other way around, but that sounds to be details.

But surface != taskbar, is it?
A systematic problem is the cooperative approach to keep the list clean (ie. a 
buggy or crashing client shall not leave false rects behind forever, kwin 
cannot be restarted to clear the list)

Assigning rects to windows/surfaces should be capable of catching crashy, but 
not buggy clients - nor can it cover multiple taskbars per surface.
Also I'd avoid resolving cached client pointers here (or you'd have to look 
them up)

- I guess we won't get around resolving the surface (since it doesn't/isn't 
supposed to know its position on screen?)
- I'm not sure whether "one taskbar per surface" is a reasonable restriction 
(my opinion still is "zero taskbars per nowhere" ;-)
- The patch definitively lacks cleanup functionality, ie. at least a 
cooperative solution to withdraw the rect (taskbar -or entry- removed from 
panel) and hash maintainace ("is the surface pointer still valid at all"?)
- If the panel <=> taskbar assumption isn't sufficient (additional systray 
entry case?) we'll require further mapping (UID on top of surface) and 
maintainance mechanisms (to not end up with 100 rects on the same surface)


- Thomas


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/#review87697
---


On Okt. 29, 2015, 4:59 nachm., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125871/
> ---
> 
> (Updated Okt. 29, 2015, 4:59 nachm.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwayland
> 
> 
> Description
> ---
> 
> this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
> order to make the minimize effects possible.
> unlike on X11, it takes relative positions and it has one geometry per panel, 
> making possible to have multiple taskbars working.
> 
> however this is still not completely exposed, as internally kwin has still 
> only one geometry, it will need a change in kwin itself (

Re: Review Request 125871: WIP: task geometries to wayland for minimize effect

2015-10-30 Thread Martin Gräßlin


> On Oct. 29, 2015, 9:32 p.m., Thomas Lübking wrote:
> > What's the point of client relative geometries?
> > 
> > Afaics, there'll be two "problematic" scenarios.
> > 
> > 1) >= 2 taskbars on >= 1 screens, the window is minimized from the taskbar
> > 2) >= 2 taskbars on >= 2 screens, the window is NOT minimized from the 
> > taskbar (but the deco button, or wmctrl etc.)
> > 
> > (1) can be _easily_ resolved by the minimizing taskbar applet updating the 
> > (one is actually sufficient here) geometry right before minimizing the 
> > client
> > 
> > The challenge of (2) is to select a taskbar where to minimize to itfp (I 
> > guess one does not want to minimize to two regions at once, seems confusing)
> > The reasonable approach seems to minimize to any icon rect that is on the 
> > same screen the window is on (WMs free choice), so we need a list of global 
> > (or tagged screen relative) geometries where the WM can look for eg. the 
> > closes match on the current ("active") or the windows screen.
> > 
> > The only benefit of a window relative geometry would be (less overhead on) 
> > tracking a moving client while the window minimizes - but the only scenario 
> > I see here is an autohiding panel and then the only overhead (if one wants 
> > to buy into such feature at all) would be an update of the icon rect from 
> > the on-screen to the off-screen position of the panel.
> > 
> > Otoh, keeping a reference to a surface around
> > a) requires a surface itfp
> > b) sounds *extremely* bug prone, eg.:
> >- I don't see where the surface removal is tracked in the patch, so we 
> > could end up with a dangeling pointer.
> >- Another case is where the taskbar is moved from eg. a panel to the 
> > desktop - we'd have it in the desktop and -outdated- the panel at the same 
> > time)
> >- Also what if I add a taskbar to the top and the bottom of my desktop? 
> > That's not supported, is it?
> > 
> > => Imo we *need* one icon rect per screen.
> > It would be cool to have one "per taskbar" (calc closest distance on 
> > unrelated minimizations)
> > But I object the approach to assign the rects to particular surfaces.

> It would be cool to have one "per taskbar" (calc closest distance on 
> unrelated minimizations)

this is kind of the idea here. Marco and I had discussed the needs and came up 
with "each panel needs to set the geometry". So that KWin knows all the 
possible geometries (we cannot use it yet, but well that's a different 
problem). That's what the patch does: Plasma can set for different windows 
(WindowManagement) an icon geometry relative to the a PlasmaSurface. My thought 
was doing it the other way around, but that sounds to be details.


- Martin


---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125871/#review87697
---


On Oct. 29, 2015, 5:59 p.m., Marco Martin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125871/
> ---
> 
> (Updated Oct. 29, 2015, 5:59 p.m.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kwayland
> 
> 
> Description
> ---
> 
> this exposes the geometry of taskbar entries in plasma-windowmanagement, in 
> order to make the minimize effects possible.
> unlike on X11, it takes relative positions and it has one geometry per panel, 
> making possible to have multiple taskbars working.
> 
> however this is still not completely exposed, as internally kwin has still 
> only one geometry, it will need a change in kwin itself (suggestions welcome) 
> probably the rotocol will need also a minimizeTo function that takes the 
> panel as argument.
> 
> another thing completely missing is tests: unfortunately the whole 
> plasma-windowmanagement doesn't have any autotest yet :/
> 
> 
> Diffs
> -
> 
>   src/client/plasmawindowmanagement.h abd8fa6 
>   src/client/plasmawindowmanagement.cpp 1f9674c 
>   src/client/plasmawindowmodel.h 5a6aac4 
>   src/client/plasmawindowmodel.cpp 355ef53 
>   src/client/protocols/plasma-window-management.xml ca6a7cc 
>   src/server/plasmashell_interface.h 9db3f52 
>   src/server/plasmashell_interface.cpp d29d7bc 
>   src/server/plasmawindowmanagement_interface.h 6ccc22e 
>   src/server/plasmawindowmanagement_interface.cpp ad714a5 
> 
> Diff: https://git.reviewboard.kde.org/r/125871/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Marco Martin
> 
>

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