Re: the next step on the desktop

On Monday, January 31, 2011, Markus Slopianka wrote: > You asked for comments and I commented. So don't be a bitch just because my > opinion differs from yours! i was "a bitch" because i don't think it is too much to ask that we come to these kinds of discussion with informed ideas and opinion. w

Re: the next step on the desktop

Dude, calm down a little. I was blaming no one of anything. You need to understand that when somebody simply states what he observes (that programmers with many programs and windows open tend to like Activities more than people who execute only 3 applications) it's not an insult against anyone.

Re: The next step (4.7) Maybe MORE MOUSE BUTTONS ?

KWin zoom effect using the mouse wheel would be awesome, as a web developer, is something I really miss from my Compiz time. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel

Re: the next step on the desktop

On Monday 31 January 2011, Aaron J. Seigo wrote: > On Monday, January 31, 2011, Alex Fiestas wrote: > > Well, then I guess that the only thing we can do is wait until desktop > > summit and try to push the GNOME developers to collaborate again... > > +10 to that. > > > Is understandable that in t

Re: the next step on the desktop

On Monday 31 January 2011, Aaron J. Seigo wrote: > On Monday, January 31, 2011, Marco Martin wrote: > > On Mon, Jan 31, 2011 at 2:22 AM, Aaron J. Seigo wrote: > > > it is time to go to that next step and move people away from the old > > > ways. > > > > yep, I would still like to push desktop bey

Re: The next step (4.7) Maybe MORE MOUSE BUTTONS ?

On Monday, January 31, 2011, Rick Stockton wrote: > Aaron, you've inspired me to slightly "pre-announce" something which > I've not yet completed within Qt: Support for more mouse buttons. oh, that is such good news! > also be enhanced. But, for people to *SEE* something new and cool on > 4.7, ri

Re: the next step on the desktop

A Segunda, 31 de Janeiro de 2011 21:23:44 Steven Sroka você escreveu: > On 31 January 2011 14:51, Aaron J. Seigo wrote: > > On Monday, January 31, 2011, Alex Fiestas wrote: > >> So, if the situation is as bad as you think it is we should organize a > >> sprint or something and try to fix the curre

a little bit of sunshine on your day

hi all ... are we doing a good job here? are our efforts really moving us in a good direction? the Linux Action Show thinks so! enjoy a bit of well-deserved (and entertaining) positive feedback: http://www.youtube.com/watch?v=44wJQ_S1PiE&feature=player_detailpage#t=1194s congrats to us all :)

Re: the next step on the desktop

On Monday, January 31, 2011, Alex Fiestas wrote: > Well, then I guess that the only thing we can do is wait until desktop > summit and try to push the GNOME developers to collaborate again... +10 to that. > Is understandable that in their current situation they can't be commited > to any new sta

Re: the next step on the desktop

On Monday, January 31, 2011, Steven Sroka wrote: > Discourage people from using GNOME 3, by making KDE even better (as > stated above) and continue pushing it as a formidable desktop and not > by outwardly and publicly criticizing GNOME devs attitudes. You are > tip-toeing on a fine line. I say thi

Re: The next step (4.7) Maybe MORE MOUSE BUTTONS ?

Aaron, you've inspired me to slightly "pre-announce" something which I've not yet completed within Qt: Support for more mouse buttons. (Within KDE, that corresponds to Bug# 34362 and all of it's related, dependent bugs. In Qt, I'm QTBUG-16092

Re: the next step on the desktop

On 31 January 2011 14:51, Aaron J. Seigo wrote: > On Monday, January 31, 2011, Alex Fiestas wrote: >> So, if the situation is as bad as you think it is we should organize a >> sprint or something and try to fix the current freedesktop situation, > > that would require GNOME developers attending wi

Re: the next step on the desktop

On 01/31/2011 08:51 PM, Aaron J. Seigo wrote: > that would require GNOME developers attending with the same goal in mind. > unfortunately, they have demonstrated repeatedly during gnome-shell > devleopment that they have no intention to cooperate more. if anything, they > have demonstrated that the

Re: the next step on the desktop

On Monday, January 31, 2011, Marco Martin wrote: > yeah, i see better to introduce changes at small steps. > for instance, we can put for 4.7 the milestone of screwing bit more with > the systray and merge toolbox and krunner (even have the activity chooser > ui there? I'm a bit intrigued with thi

Re: the next step on the desktop

On Monday 31 January 2011, Aaron J. Seigo wrote: > On Sunday, January 30, 2011, todd rme wrote: > > On Sun, Jan 30, 2011 at 8:22 PM, Aaron J. Seigo wrote: > > > * a new panel layout (TBD: let's work on this together!) > > > * improve the tasks widget to have some of the nice features of widgets >

Re: the next step on the desktop

On Monday, January 31, 2011, Ivan Čukić wrote: > > hm.. but they don't show up in window titlebar context menus when they > > are stopped; so a "bug" in kwin, then? it should be possible imho to > > send windows to any defined activity. we could put the stopped > > activities at the bottom of > >

Re: the next step on the desktop

On Monday, January 31, 2011, Marco Martin wrote: > On Mon, Jan 31, 2011 at 2:22 AM, Aaron J. Seigo wrote: > > it is time to go to that next step and move people away from the old > > ways. > > yep, I would still like to push desktop beyond the desktop, resistence > against is so amazing that i f

Re: the next step on the desktop

On Sunday, January 30, 2011, todd rme wrote: > On Sun, Jan 30, 2011 at 8:22 PM, Aaron J. Seigo wrote: > > * a new panel layout (TBD: let's work on this together!) > > * improve the tasks widget to have some of the nice features of widgets > > like "smooth tasks" with the mouse over highlights >

Re: the next step on the desktop

> hm.. but they don't show up in window titlebar context menus when they are > stopped; so a "bug" in kwin, then? it should be possible imho to send windows > to any defined activity. we could put the stopped activities at the bottom of What would that do? 1. Start the activity in question 2. Sto

Re: the next step on the desktop

On Monday, January 31, 2011, Ivan Cukic wrote: > > * have all activities avaiable in kactivitmanagerd, even if they are > > "stopped" in plasma-desktop > > ? Activities that are stopped are still in kamd. hm.. but they don't show up in window titlebar context menus when they are stopped; so a "b

Re: the next step on the desktop

On Monday, January 31, 2011, Alex Fiestas wrote: > So, if the situation is as bad as you think it is we should organize a > sprint or something and try to fix the current freedesktop situation, that would require GNOME developers attending with the same goal in mind. unfortunately, they have demo

Re: the next step on the desktop

On Monday 31 January 2011 20:40:41 Aaron J. Seigo wrote: > On Monday, January 31, 2011, Diego Casella ([Po]lentino) wrote: > > Panels, in the current implementation, are shared across different > > activities: what about adding an option like "stick to current activity", > > in order to achieve dif

Re: the next step on the desktop

On Monday, January 31, 2011, Diego Casella ([Po]lentino) wrote: > Panels, in the current implementation, are shared across different > activities: what about adding an option like "stick to current activity", > in order to achieve different panels for different activities? as long as the UI is kep

Re: the next step on the desktop

On Sunday, January 30, 2011, Markus Slopianka wrote: > > let's try something big and new. let's make that Big Move and step away > > from ~/Desktop. > > Frankly, I like my dumping ground. and you can retain it. nobody is taking it away from you. even though i personally think you'd find far bett

Re: the next step on the desktop

> What about just middle-click on the group? I've had a talk (IRC) with Martin and I decided to pull out the proposal since due to one reason (at least for the time being) - it is not useful in general, but only for specific SDI applications. -- Cheerio, Ivan -- While you were hanging yourself

Re: the next step on the desktop

On 01/31/2011 05:29 PM, Marco Martin wrote: >> and they are developing a new standard and already prepared a wiki page >> which includes all apps they need to change (also lists various KDE apps); >> http://live.gnome.org/GnomeShell/Design/Guidelines/MessageTray/Compatibili >> ty >> >> Ah and they

Re: the next step on the desktop

On Monday 31 January 2011, todd rme wrote: > > The same goes when using Konqueror with KWin tabs instead of innter tabs. > > > > While my main input device is the keyboard, I missed a button like this > > quite a few times. > > What about just middle-click on the group? > taken for ungrouping ;

Re: the next step on the desktop

On 01/31/2011 05:04 PM, Marco Martin wrote: > duh! > so wouldn't break something that now is working after all ;) > all of this should depend on resolutions returning different values, so Imho we should disable that feature by default and improve the application default size. Maybe the correct way

Re: the next step on the desktop

On Mon, Jan 31, 2011 at 12:55 PM, Ivan Cukic wrote: > >> you know ctrl+f7, do you? > > Yes, naturally, but having a key-shortcut for something doesn't mean there > shouldn't be a mouse-way for the same thing. (for example winmenu - alt > f3, close alt f4 etc.) > >> I don't think it's a good idea t

Re: the next step on the desktop

> you know ctrl+f7, do you? Yes, naturally, but having a key-shortcut for something doesn't mean there shouldn't be a mouse-way for the same thing. (for example winmenu - alt f3, close alt f4 etc.) > I don't think it's a good idea to add random buttons. It is not like it is a 'run A.M.O.R. ap

Re: the next step on the desktop

On Monday 31 January 2011, Martin Gräßlin wrote: > On Monday 31 January 2011 17:09:51 Marco Martin wrote: > > On Monday 31 January 2011, Alex Fiestas wrote: > > > On 01/31/2011 04:11 PM, Marco Martin wrote: > > > > eh. > > > > *cough* statusNotifierItem *cough* ;) > > > > > > GNOME 3 doesn't use s

Re: the next step on the desktop

On Monday 31 January 2011 17:38:21 Ivan Cukic wrote: > On Monday, 31. January 2011. 17.29.04 Martin Gräßlin wrote: > > But changing the semantics of Maximized button depending on whether the > > app is modern or not is also a no go > > While we are on the topic of adding new captionbar buttons -

Re: the next step on the desktop

On Monday 31 January 2011 17:49:19 Fredrik Höglund wrote: > On Monday 31 January 2011, Martin Gräßlin wrote: > > - Ursprüngliche Mitteilung - > > > > > A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > > > > provocation: remove the maximize button by default? ;) (as t

Re: the next step on the desktop

On Monday 31 January 2011 17:09:51 Marco Martin wrote: > On Monday 31 January 2011, Alex Fiestas wrote: > > On 01/31/2011 04:11 PM, Marco Martin wrote: > > > eh. > > > *cough* statusNotifierItem *cough* ;) > > > > GNOME 3 doesn't use statusNotifierItem? > > nope, they are still with xembed ones ;

Re: the next step on the desktop

> yeah, that as well, now it's possible with ctrl+click on the taskbar > group, but i don't think many people actually know it, it's so > carefully hidden ;) And it should work even if people (like me) don't use taskbar groups. Honestly, I always found that the taskbar was a misguided concept, b

Re: the next step on the desktop

On Monday 31 January 2011, Alex Fiestas wrote: > On 01/31/2011 04:11 PM, Marco Martin wrote: > > eh. > > *cough* statusNotifierItem *cough* ;) > > GNOME 3 doesn't use statusNotifierItem? nope, they are still with xembed ones ;) i think also support for systray icons at all was rushed in recently

Re: the next step on the desktop

On Monday 31 January 2011, Ivan Cukic wrote: > On Monday, 31. January 2011. 17.29.04 Martin Gräßlin wrote: > > But changing the semantics of Maximized button depending on whether the > > app is modern or not is also a no go > > While we are on the topic of adding new captionbar buttons - the thin

Re: the next step on the desktop

On Monday 31 January 2011, Alex Fiestas wrote: > On 01/31/2011 03:35 PM, Marco Martin wrote: > > yeah, tis is a good point indeed. > > what happens now when ap application that saved its geometry when closed > > on a bigger screen gets started on the small one? > > That you get used to maximize th

Re: the next step on the desktop

On 01/31/2011 04:11 PM, Marco Martin wrote: > eh. > *cough* statusNotifierItem *cough* ;) GNOME 3 doesn't use statusNotifierItem? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel

Re: the next step on the desktop

On 01/31/2011 03:35 PM, Marco Martin wrote: > yeah, tis is a good point indeed. > what happens now when ap application that saved its geometry when closed on a > bigger screen gets started on the small one? That you get used to maximize the window because the window doesn't fit into the small scre

Re: the next step on the desktop

On Monday 31 January 2011, Martin Gräßlin wrote: > - Ursprüngliche Mitteilung - > > A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > > > provocation: remove the maximize button by default? ;) (as the netbook > > > doesn't have minimize) > > > > will talk to mgrslin t

Re: the next step on the desktop

On Monday, 31. January 2011. 17.29.04 Martin Gräßlin wrote: > But changing the semantics of Maximized button depending on whether the > app is modern or not is also a no go While we are on the topic of adding new captionbar buttons - the thing that I think would be nice is a a button to invoke p

Re: the next step on the desktop

On Monday 31 January 2011 17:08:59 todd rme wrote: > On Mon, Jan 31, 2011 at 10:54 AM, Martin Gräßlin > > wrote: > > - Ursprüngliche Mitteilung - > > > >> A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > >> > provocation: remove the maximize button by default? ;) (

Re: the next step on the desktop

On Monday 31 January 2011 16:11:45 Marco Martin wrote: > On Monday 31 January 2011, Martin Gräßlin wrote: > > - Ursprüngliche Mitteilung - > > > > > A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > > > > provocation: remove the maximize button by default? ;) (as the

Re: the next step on the desktop

On Monday 31 January 2011, Martin Gräßlin wrote: > - Ursprüngliche Mitteilung - > > > A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > > > provocation: remove the maximize button by default? ;) (as the netbook > > > doesn't have minimize) > > > > will talk to mgrsli

Re: the next step on the desktop

On Mon, Jan 31, 2011 at 10:54 AM, Martin Gräßlin wrote: > - Ursprüngliche Mitteilung - >> A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: >> > provocation: remove the maximize button by default? ;) (as the netbook >> > doesn't have minimize) >> >> will talk to mgrslin

Re: the next step on the desktop

- Ursprüngliche Mitteilung - > A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > > provocation: remove the maximize button by default? ;) (as the netbook > > doesn't have minimize) > > will talk to mgrslin this afternoon but somthing like a optimal size > buton  inst

Re: the next step on the desktop

On Monday 31 January 2011, Alex Fiestas wrote: > In KDE we're used to resize the windows to fulfill our personal needs, > and let the application save the "last used size". I guess that is > because of that feature that a lot of applications doesn't care about > the correct size. > > A good experi

Re: the next step on the desktop

In KDE we're used to resize the windows to fulfill our personal needs, and let the application save the "last used size". I guess that is because of that feature that a lot of applications doesn't care about the correct size. A good experiment would be disable that feature in trunk (having a wa

Re: the next step on the desktop

A Segunda, 31 de Janeiro de 2011 13:54:45 Marco Martin você escreveu: > On Monday 31 January 2011, Nuno Pinheiro wrote: > > A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > > > On Monday 31 January 2011, Nuno Pinheiro wrote: > > > > > my proposal is this: > > > > > > > > > >

Re: the next step on the desktop

On Monday 31 January 2011, Nuno Pinheiro wrote: > A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > > On Monday 31 January 2011, Nuno Pinheiro wrote: > > > > my proposal is this: > > > > > > > > * by default, Search and Launch on the desktop > > > > > > We talked about this

Re: the next step on the desktop

A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > On Monday 31 January 2011, Nuno Pinheiro wrote: > > > my proposal is this: > > > > > > * by default, Search and Launch on the desktop > > > > We talked about this in last tokamac remember? > > Imo a merge of krunner, activity

Re: the next step on the desktop

A Segunda, 31 de Janeiro de 2011 13:00:50 Marco Martin você escreveu: > On Monday 31 January 2011, Nuno Pinheiro wrote: > > > my proposal is this: > > > > > > * by default, Search and Launch on the desktop > > > > We talked about this in last tokamac remember? > > Imo a merge of krunner, activity

Re: the next step on the desktop

> Let's publish and trumpet a roadmap for that: > * in 4.7 watch out for those changes, they would put the basis for the > next revolution > * market it as a big revolution where -you- can be in (i.e. to get > people to join) > * as in pre 4.0 start to publish mockups, as imaes as qml, as longer >

Re: the next step on the desktop

On Monday 31 January 2011, Diego Casella ([Po]lentino) wrote: > Panels, in the current implementation, are shared across different > activities: what about adding an option like "stick to current activity", > in order to achieve different panels for different activities? > That would be great imho

Re: the next step on the desktop

On Monday 31 January 2011, Ivan Cukic wrote: > While I tend to agree with the notion that a continued (r)evolution is > needed, I have a few problems with some of these ideas. > > > * by default, Search and Launch on the desktop > > * an icon in this S&L that takes you to your desktop folder .. in

Re: the next step on the desktop

On Monday 31 January 2011, Nuno Pinheiro wrote: > > my proposal is this: > > > > * by default, Search and Launch on the desktop > > We talked about this in last tokamac remember? > Imo a merge of krunner, activityes management, and the cashew and a few > specific tryicons (just the hardware vital

Re: KWin GLES, cleanup and coding style change

2011/1/30 Martin Gräßlin > There is of course the option to change it manually. I would not like to do > it, but if there is no automatic way I will waste tomorrow evening ;-) > Don't know about astyle, but I'd do something like: - find . -exec sed -i "s/if(/if (/g" {} \; # Change all occurren

Re: the next step on the desktop

On Mon, Jan 31, 2011 at 2:22 AM, Aaron J. Seigo wrote: > hi... > > back when we started the path towards plasma i said that we needed to slowly > evolve the desktop beyond the desktop folder with icons littered on the > desktop. > > now we have activities, kick-ass containments like search and lau

Re: the next step on the desktop

On Monday 31 January 2011 13:42:31 Diego Casella ([Po]lentino) wrote: > > -- Messaggio inoltrato -- > > From: "Aaron J. Seigo" > > To: plasma-devel@kde.org > > Date: Sun, 30 Jan 2011 17:22:41 -0800 > > Subject: the next step on the desktop > > > > my proposal is this: > > [...] >

Re: the next step on the desktop

While I tend to agree with the notion that a continued (r)evolution is needed, I have a few problems with some of these ideas. > * by default, Search and Launch on the desktop > * an icon in this S&L that takes you to your desktop folder .. in a file > manager. SAL is awesome. But it is designed

Re: the next step on the desktop

Sorry for the clutter in my previous email, I forgot to fully clean the body of the email :( ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel

Re: the next step on the desktop

> -- Messaggio inoltrato -- > From: "Aaron J. Seigo" > To: plasma-devel@kde.org > Date: Sun, 30 Jan 2011 17:22:41 -0800 > Subject: the next step on the desktop > > my proposal is this: > [...] > * a new panel layout (TBD: let's work on this together!) > Panels, in the current imp

Re: KWin GLES, cleanup and coding style change

On Sunday, January 30, 2011 20:15:02 Martin Gräßlin wrote: > > I am just going through the coding style changes and it looks fine so > > far. Except that the astyle script generated > > if(foo) { > > } > > instead of > > if (foo) { > > } > > > > I used the astyle-kdelibs script in kdesdk. If anyone