Re: Evolving Appdash

2016-01-27 Thread Martin Graesslin
On Thursday, December 17, 2015 1:01:44 PM CET Martin Graesslin wrote: > On Thursday, December 17, 2015 12:52:35 PM CET Marco Martin wrote: > > On Wednesday 16 December 2015, Martin Klapetek wrote: > > > > Also the appdash is almost unusable without a blur effect (which for > > > > example > > > > h

Re: Evolving Appdash

2015-12-17 Thread Eike Hein
On 12/17/2015 01:01 PM, Martin Graesslin wrote: > I'll investigate after the Christmas break how to expose a downsampling blur > in the effects infrastructure. Ideally this can be achieved with zero costs > in > the rendering. Awesome :) > Cheers > Martin Cheers, Eike _

Re: Evolving Appdash

2015-12-17 Thread Martin Graesslin
On Thursday, December 17, 2015 12:52:35 PM CET Marco Martin wrote: > On Wednesday 16 December 2015, Martin Klapetek wrote: > > > Also the appdash is almost unusable without a blur effect (which for > > > example > > > happens with GLES, XRender and QPainter backends). > > > > How about generating

Re: Evolving Appdash

2015-12-17 Thread Marco Martin
On Wednesday 16 December 2015, Martin Klapetek wrote: > > Also the appdash is almost unusable without a blur effect (which for > > example > > happens with GLES, XRender and QPainter backends). > > How about generating blurred wallpaper at some point, storing it > and then using that as background

Re: Evolving Appdash

2015-12-16 Thread Martin Klapetek
On Wed, Dec 16, 2015 at 11:30 AM, Aleix Pol wrote: > > Well you'd still need to blur the windows under it, no? > No, it wouldn't be a live blur, it would simply be a background image for performance reasons. Possibly the live blur could stay too as an option for those with powerful machines. Ch

Re: Evolving Appdash

2015-12-16 Thread Eike Hein
Some relevant IRC log: [15:37] mgraesslin: i wonder if we can get a kwin effect that only blurs in the desktop layer and cuts out the windows, as a fallback or even default for dashboard [15:37] mgraesslin: or we can resurrect the kde3 approach to translucency and have plasma export the wallpap

Re: Evolving Appdash

2015-12-16 Thread Aleix Pol
On Wed, Dec 16, 2015 at 5:00 PM, Martin Klapetek wrote: > On Wed, Dec 16, 2015 at 3:12 AM, Martin Graesslin > wrote: >> >> On Tuesday, December 15, 2015 6:48:32 PM CET Eike Hein wrote: >> > The VDG has offered to join in with some cool mockups to maxi- >> > mize potential. >> >> it would be cool

Re: Evolving Appdash

2015-12-16 Thread Martin Klapetek
On Wed, Dec 16, 2015 at 3:12 AM, Martin Graesslin wrote: > On Tuesday, December 15, 2015 6:48:32 PM CET Eike Hein wrote: > > The VDG has offered to join in with some cool mockups to maxi- > > mize potential. > > it would be cool if the VDG could also look into a non-blur variant for the > appdash

Re: Evolving Appdash

2015-12-16 Thread Martin Graesslin
On Tuesday, December 15, 2015 8:27:28 PM CET Marco Martin wrote: > > Appdash from edge swipe sounds really cool. Sounds like this would > > be combined with the hot corner KCM? > > it should probably be something kwin-driven, as an invisible window to take > the input is probably too invasive (sho

Re: Evolving Appdash

2015-12-16 Thread Martin Graesslin
On Tuesday, December 15, 2015 6:48:32 PM CET Eike Hein wrote: > The VDG has offered to join in with some cool mockups to maxi- > mize potential. it would be cool if the VDG could also look into a non-blur variant for the appdash. I'm still very concerned about the full screen blur as the KWin ef

Re: Evolving Appdash

2015-12-15 Thread Eike Hein
On 12/15/2015 08:27 PM, Marco Martin wrote: > if available even just by shortcut, it should strictly be lazy loading as i > wouldn't like something expensive that is loaded and then quite hidden (at > this point one could put the toolbox entry in). and in this case i would also > like to be ab

Re: Evolving Appdash

2015-12-15 Thread Marco Martin
On Tuesday 15 December 2015, Eike Hein wrote: > > I think elevating the visibility based on touchscreen presence could > make sense. How do you see this in practice? edge swiping only in touchscreen, toolbox/context menu entry maybe only on touchscreen, hot corner i would say just if explicitly

Re: Evolving Appdash

2015-12-15 Thread Eike Hein
On 12/15/2015 08:11 PM, Martin Klapetek wrote: > I feel like this argument is not holding very well. We already provide > KRunner > by default, which I believe falls into the very same category as this. It's > just another way to do the same thing (launching an app plus much more > duplicated fun

Re: Evolving Appdash

2015-12-15 Thread Marco Martin
On Tuesday 15 December 2015, Martin Klapetek wrote: > I feel like this argument is not holding very well. We already provide > KRunner > by default, which I believe falls into the very same category as this. It's > just another way to do the same thing (launching an app plus much more > duplicated

Re: Evolving Appdash

2015-12-15 Thread Martin Klapetek
On Tue, Dec 15, 2015 at 1:45 PM, Marco Martin wrote: > On Tuesday 15 December 2015, Eike Hein wrote: > > I'd like to propose moving kdeplasma-addon's Appdash UI out of > > kdeplasma-addons into plasma-desktop, fleshing it out a little > > more and making it available in the following ways: > > >

Re: Evolving Appdash

2015-12-15 Thread Eike Hein
On 12/15/2015 07:45 PM, Marco Martin wrote: > I think I still wouldn't like having it always by default for everybody, 2 > ways to do the same thing (launching an app) by default i don't think is a > good pattern in general, especially since a fullscreen grid of very distanced > icons while lo

Re: Evolving Appdash

2015-12-15 Thread Marco Martin
On Tuesday 15 December 2015, Eike Hein wrote: > I'd like to propose moving kdeplasma-addon's Appdash UI out of > kdeplasma-addons into plasma-desktop, fleshing it out a little > more and making it available in the following ways: > > a) Global default keyboard shortcut > b) Desktop Toolbox entry >

Evolving Appdash

2015-12-15 Thread Eike Hein
I'd like to propose moving kdeplasma-addon's Appdash UI out of kdeplasma-addons into plasma-desktop, fleshing it out a little more and making it available in the following ways: a) Global default keyboard shortcut b) Desktop Toolbox entry c) Available as hot corner action d) Available as a now-op