Re: [Ayatana] Papercut or not? Bug #495403 in On e Hundred Paper Cuts: “Do not raise windows o r dialogs without user input”

On 24 May 2010 21:34, Mark Shuttleworth wrote: > It's definitely not a papercut :-) > > Personally, I think trying to prevent focus-stealing does more harm than > good. If you do that, you end up with a LOT of suboptimal situations > like windows opening in the background. So I'm +1 the current ban

Re: [Ayatana] Papercut or not? Bug #495403 in On e Hundred Paper Cuts: “Do not raise windows o r dialogs without user input”

Alright, well cross that one off the list. On May 24, 2010 4:59 PM, "Tyler Brainerd" wrote: apparently its denying its a problem. On Mon, May 24, 2010 at 1:56 PM, Alex Schoof wrote: > > What's the current... ___ Mailing list: https://launchpad.net/

Re: [Ayatana] Inconsistencies from LHS buttons

On Mon, 2010-05-24 at 16:53 -0400, Alex Schoof wrote: > +1 > > Chromium now can do LHS, but you're right: there are a lot of common > applications where button placemennt is inconsistant. The gnome-shell > point isbalso valid, with gnome 3 just around the corner, we need to > nail this down. GNOM

Re: [Ayatana] Papercut or not? Bug #495403 in On e Hundred Paper Cuts: “Do not raise windows o r dialogs without user input”

apparently its denying its a problem. On Mon, May 24, 2010 at 1:56 PM, Alex Schoof wrote: > What's the current band aid? > > On May 24, 2010 3:34 PM, "Mark Shuttleworth" wrote: > > On 24/05/10 16:57, Conscious User wrote: > > I think the ideal would be not to steal focus *if the use... > > It's

Re: [Ayatana] Papercut or not? Bug #495403 in On e Hundred Paper Cuts: “Do not raise windows o r dialogs without user input”

What's the current band aid? On May 24, 2010 3:34 PM, "Mark Shuttleworth" wrote: On 24/05/10 16:57, Conscious User wrote: > I think the ideal would be not to steal focus *if the use... It's definitely not a papercut :-) Personally, I think trying to prevent focus-stealing does more harm than go

Re: [Ayatana] Inconsistencies from LHS buttons

+1 Chromium now can do LHS, but you're right: there are a lot of common applications where button placemennt is inconsistant. The gnome-shell point isbalso valid, with gnome 3 just around the corner, we need to nail this down. On May 24, 2010 4:13 PM, "Tyler Brainerd" wrote: +1 to all of these.

Re: [Ayatana] Fw: Re: Rethink the noninteractive Live CD default boot?

I don't think anyone would ever argue that we shouldn't be intergrity checking boot media (or at least presenting the option); while I never considered it a pain point, I guess I could see a new user getting confused and giving up. Maybe the solution is to have the FIRST menu a user sees be "boot o

[Ayatana] Fw: Re: Rethink the noninteractive Live CD default boot?

Arrgh, I just realized that I used an email address not registered with Ayatana when I sent this earlier, so apologies for the double post :^( --- On Mon, 5/24/10, erickbrunz...@sbcglobal.net wrote: From: erickbrunz...@sbcglobal.net Subject: Re: [Ayatana] Rethink the noninteractive Live CD de

Re: [Ayatana] Inconsistencies from LHS buttons

+1 to all of these. These are all inconsistencies that should be looked at, and smoothed out. If we are told certain areas are for certain things, then lets see it happen. On Mon, May 24, 2010 at 12:48 PM, Mark Curtis wrote: > This is not complaining about their position and demanding they be p

[Ayatana] Inconsistencies from LHS buttons

This is not complaining about their position and demanding they be put on the right. I know such a message would be pointless. I however notice a few inconsistencies brought about by their placement. Indicator Session: I brought this up in an earlier thread, but was drowned out by the thread a

Re: [Ayatana] Papercut or not? Bug #495403 in One Hundr ed Paper Cuts: “Do not raise windows or dialogs witho ut user input”

On 24/05/10 16:57, Conscious User wrote: > I think the ideal would be not to steal focus *if the user is > currently typing*, but then we go into non-trivial fix world > and out of the papercut world. > It's definitely not a papercut :-) Personally, I think trying to prevent focus-stealing doe

Re: [Ayatana] Clock Menu Redesign [was: Evolution && is: progress]

On 24/05/10 18:32, Vishnoo wrote: > On Mon, 2010-05-24 at 13:47 +0100, Mark Shuttleworth wrote: > >> On 21/05/10 18:47, Frederik Nnaji wrote: >> >>> Hi Nicholas ;) >>> >>> On Wed, May 19, 2010 at 18:01, Nicholas Ipsen wrote: >>> >>> I think it would be nice to include a weat

Re: [Ayatana] Clock Menu Redesign [was: Evolution && is: progress]

On Mon, 2010-05-24 at 13:47 +0100, Mark Shuttleworth wrote: > On 21/05/10 18:47, Frederik Nnaji wrote: > > Hi Nicholas ;) > > > > On Wed, May 19, 2010 at 18:01, Nicholas Ipsen wrote: > > > >> I think it would be nice to include a weather indicator, maybe to the left > >> of the Clock? I certain

Re: [Ayatana] Papercut or not? Bug #495403 in One Hundr ed Paper Cuts: “Do not raise windows or dialogs witho ut user input”

Le lundi 24 mai 2010 à 17:29 +0200, Sense Hofstede a écrit : > Hello, > > I would like to ask for some feedback regarding bug > , which was reported in December > 2009 and is still pending as a papercut. The reported issue is that it > is possible for windows to

[Ayatana] Papercut or not? Bug #495403 in On e Hundred Paper Cuts: “Do not raise windows o r dialogs without user input”

Hello, I would like to ask for some feedback regarding bug , which was reported in December 2009 and is still pending as a papercut. The reported issue is that it is possible for windows to steal the focus when you're typing something. The example given by the re

Re: [Ayatana] Two suggested designs for the Sound Indicator

On 22/05/10 12:26, Philipp Wendler wrote: >> Browsers are a problem, as there is no way for them to indicate the >> intention (and if websites would be given a way to indicate their >> intention, it would be abused by spammers from day one). I suppose the >> best solution is to have dedicated prog

Re: [Ayatana] Clock Menu Redesign [was: Evolution && is: progress]

On Mon, 2010-05-24 at 13:47 +0100, Mark Shuttleworth wrote: > On 21/05/10 18:47, Frederik Nnaji wrote: > > Hi Nicholas ;) > > > > On Wed, May 19, 2010 at 18:01, Nicholas Ipsen wrote: > > > >> I think it would be nice to include a weather indicator, maybe to the left > >> of the Clock? I certain

Re: [Ayatana] Papercuts in Maverick

On Mon, 2010-05-24 at 14:36 +0200, Sense Hofstede wrote: > Hello, > > The UDS hangover should be completely gone now and we all probably > can't wait to start working (even harder)! > I've got a couple of thing with regard the papercuts project I would > like to ask. > > Vish has already done som

Re: [Ayatana] Global menu and non-supported applications

Le lundi 24 mai 2010 à 13:02 +0100, Mark Shuttleworth a écrit : > On 24/05/10 10:55, Conscious User wrote: > > For the upcoming Netbook Global Menu, I was wondering what is > > the planned behavior for non-supported applications (which > > will inevitably exist, for example I'm supposing it won't

Re: [Ayatana] Clock Menu Redesign [was: Evolution && is: progress]

On 21/05/10 18:47, Frederik Nnaji wrote: > Hi Nicholas ;) > > On Wed, May 19, 2010 at 18:01, Nicholas Ipsen wrote: > >> I think it would be nice to include a weather indicator, maybe to the left >> of the Clock? I certainly appreciate this functionality in the current Gnome >> Clock Applet, but

[Ayatana] Papercuts in Maverick

Hello, The UDS hangover should be completely gone now and we all probably can't wait to start working (even harder)! I've got a couple of thing with regard the papercuts project I would like to ask. Vish has already done some serious triaging for the papercuts project and I've done a few as well,

Re: [Ayatana] Global menu and non-supported applications

On 24/05/10 10:55, Conscious User wrote: > For the upcoming Netbook Global Menu, I was wondering what is > the planned behavior for non-supported applications (which > will inevitably exist, for example I'm supposing it won't > support legacy Qt3 or Gtk1 applications... and is Java Swing > support

[Ayatana] Global menu and non-supported applications

Hi, For the upcoming Netbook Global Menu, I was wondering what is the planned behavior for non-supported applications (which will inevitably exist, for example I'm supposing it won't support legacy Qt3 or Gtk1 applications... and is Java Swing support planned?). In fact, I pretty much doubt that