Written by Klau3 the 17 Oct 10 at 13:56.

If two windows use all vertical space and they touch each other it should be possible to resize both windows, dragging the mouse cursor between them to the left or the right.

If two windows use all vertical space and they touch each other it should be possible to resize both windows, dragging the mouse cursor between them to the left or the right.

Written by Ssdg the 18 Oct 10 at 08:19.

In order not to mess with people's habits, the "multiple-resizing" feature should be associated with another button. Because left is linked with "legacy resizing" and because right shows the menu (I use it a lot, it helps see a window bigger than the screen) so let's use the middle mouse button.

In order not to mess with people's habits, the "multiple-resizing" feature should be associated with another button. Because left is linked with "legacy resizing" and because right shows the menu (I use it a lot, it helps see a window bigger than the screen) so let's use the middle mouse button.

Written by Lachu the 18 Oct 10 at 13:55.

Allow to use now floating mode in Metacity, but restrict settings to certain window. Each window will remember positioning type. By switching window, we switching also positioning mode.

You can imagine that like using fullscreen app. By switching to this window, it takes whole screen. When switching it off, it are minimized. We can extend this to remember different settings of sets of window, but each will be related to one main window. Now, by select another main window fullscreen application will be showed as normal window in ex. right-bottom edge.

Allow to use now floating mode in Metacity, but restrict settings to certain window. Each window will remember positioning type. By switching window, we switching also positioning mode. You can imagine that like using fullscreen app. By switching to this window, it takes whole screen. When switching it off, it are minimized. We can extend this to remember different settings of sets of window, but each will be related to one main window. Now, by select another main window fullscreen application will be showed as normal window in ex. right-bottom edge.

Written by Aielyn the 19 Oct 10 at 07:04.

Give the system the ability to attach windows to each other as far as layout issues are concerned - basically, you could anchor one window to another one, with various settings to allow you to anchor them in the way that suits you.

This would not only enable the functionality desired by this idea (moving two, or more than two, connected window boundaries simultaneously), but would also grant a few other features, including the ability to always keep the windows together in the display stack (so, in the image above, if you minimise the writer, it minimises firefox, and vice versa, and if you give one focus, the other is displayed directly "beneath" it in terms of display depth, above all other windows).

Options for the anchoring process would include:

- "Common Frame", which would make the windows operate as though they were a single window for the purposes of resizing, etc (drag Writer's right border to the left, and Firefox shrinks in proportion, while keeping the borders aligned - halve Writer's width, and Firefox's width is also halved).
- "Common Border", which would do as suggested in the idea, and move both borders without moving any other borders.
- "Glued Border", which would cause the borders to be held together, but otherwise leave all details of the windows separate; move the Writer right border to the left, and the Firefox window moves to the left so the borders still remain aligned, but the Firefox window keeps its size and shape.
- "Free Borders", which would decouple the window borders, but still attach the windows to each other.

Give the system the ability to attach windows to each other as far as layout issues are concerned - basically, you could anchor one window to another one, with various settings to allow you to anchor them in the way that suits you. This would not only enable the functionality desired by this idea (moving two, or more than two, connected window boundaries simultaneously), but would also grant a few other features, including the ability to always keep the windows together in the display stack (so, in the image above, if you minimise the writer, it minimises firefox, and vice versa, and if you give one focus, the other is displayed directly "beneath" it in terms of display depth, above all other windows). Options for the anchoring process would include: - "Common Frame", which would make the windows operate as though they were a single window for the purposes of resizing, etc (drag Writer's right border to the left, and Firefox shrinks in proportion, while keeping the borders aligned - halve Writer's width, and Firefox's width is also halved). - "Common Border", which would do as suggested in the idea, and move both borders without moving any other borders. - "Glued Border", which would cause the borders to be held together, but otherwise leave all details of the windows separate; move the Writer right border to the left, and the Firefox window moves to the left so the borders still remain aligned, but the Firefox window keeps its size and shape. - "Free Borders", which would decouple the window borders, but still attach the windows to each other. In all cases above, moving one window would also move the other window. Further gluing would be possible in order to attach more windows to each other, even sharing a single border. In the "Free Borders" option, only movement of windows would make a difference, resizing of windows would not matter.

Written by Mrinal Saurabh the 19 Oct 10 at 18:51.

Every new window opened should be a tab in title bar. Then a multiple display feature could be used to see more than one windows together.

Every new window opened should be a tab in title bar. Then a multiple display feature could be used to see more than one windows together.

Written by dsterry the 20 Oct 10 at 22:08.

If you want two windows to split the screen, you should be able to grab each one and move them toward their respective sides of the screen to put them in this auto-resized mode. Then if you want to move the boundary between them, you should be able to grab the boundary on either side of that split and move it back and forth horizontally.

This is similar to what another OS does but the addition of being able to drag the adjoining barrier can make this more useful for me. For example, I may want my web browser to be bigger than my gedit with as few clicks and drags as possible.

This may collide with compiz's ability to drag windows between desktops but it's a valid tradeoff.

Furthermore, this should be default behavior for Ubuntu.

If you want two windows to split the screen, you should be able to grab each one and move them toward their respective sides of the screen to put them in this auto-resized mode. Then if you want to move the boundary between them, you should be able to grab the boundary on either side of that split and move it back and forth horizontally. This is similar to what another OS does but the addition of being able to drag the adjoining barrier can make this more useful for me. For example, I may want my web browser to be bigger than my gedit with as few clicks and drags as possible. This may collide with compiz's ability to drag windows between desktops but it's a valid tradeoff. Furthermore, this should be default behavior for Ubuntu.

Written by 3esmit the 21 Oct 10 at 19:17.

Built as a Compiz 'plugin'.
While pressing super button, select windows to resize, and if the resizing selected window reaches other selected window, it will move it and if there is no space to move, resize it.

Built as a Compiz 'plugin'. While pressing super button, select windows to resize, and if the resizing selected window reaches other selected window, it will move it and if there is no space to move, resize it.

Written by david4dev the 24 Oct 10 at 23:19.

Introduce a window manager mode where windows do not overlap and act more like frames. By default the screen space should be shared equally but the borders between frames should be adjustable (a bit like terminator). Opening a new application window or selecting a frame from the window list (or alternatives) should add this window to the list of frames on the screen. The existing frames should automatically resize to accommodate the new frame. Clicking on the window list button for a particular frame that is showing (so the minimise action) should remove it from the screen and the existing windows should automatically resize to fill the space. This should not be a default but should be easy to enable or disable.

Introduce a window manager mode where windows do not overlap and act more like frames. By default the screen space should be shared equally but the borders between frames should be adjustable (a bit like terminator). Opening a new application window or selecting a frame from the window list (or alternatives) should add this window to the list of frames on the screen. The existing frames should automatically resize to accommodate the new frame. Clicking on the window list button for a particular frame that is showing (so the minimise action) should remove it from the screen and the existing windows should automatically resize to fill the space. This should not be a default but should be easy to enable or disable.

Written by argh0 the 25 Oct 10 at 08:11.

Introduce new options when right-clicking on the windows list (gnome-panel applet) :
- rearange the open windows vertically
- rearange the open windows horizontally
-> and when doing that, associate the connecting windows borders in order to move them together

Introduce new options when right-clicking on the windows list (gnome-panel applet) : - rearange the open windows vertically - rearange the open windows horizontally -> and when doing that, associate the connecting windows borders in order to move them together

Written by ganassa the 26 Oct 10 at 17:18.

In a tiling Wm like Ion, Xmonad, i3 etc., this problem is solved at the source: windows can't overlap each other, with some exception using floating windows and tabbed frames. It would really nice if metacity, or whetever WM adopted, could manage this behaviour.

In a tiling Wm like Ion, Xmonad, i3 etc., this problem is solved at the source: windows can't overlap each other, with some exception using floating windows and tabbed frames. It would really nice if metacity, or whetever WM adopted, could manage this behaviour.

Written by lemuelinchrist the 3 Nov 10 at 03:09.

Most users, when using a big screen (say 22'') almost never use the maximize button anymore. So why not give the user freedom to customize the maximize button such that it would only fill half or maybe 2/3 or 1/3 of the screen depending on his choice?

Or if we want to preserve the function of the maximize button, why not add a fourth button for this in addition to the min, max, and close button.

Sometimes manually resizing windows can be burdensome. pressing the maximize window is a lot quicker to fill up screens

Most users, when using a big screen (say 22'') almost never use the maximize button anymore. So why not give the user freedom to customize the maximize button such that it would only fill half or maybe 2/3 or 1/3 of the screen depending on his choice? Or if we want to preserve the function of the maximize button, why not add a fourth button for this in addition to the min, max, and close button. Sometimes manually resizing windows can be burdensome. pressing the maximize window is a lot quicker to fill up screens

Written by ejh the 4 Nov 10 at 17:32.

This is one area that I think windows 7 beats ubuntu. Windows 7's "aerosnap" function works as shown in this video: youtu.be/bopeB6QbOjI.

Ubuntu could implement the windows 7 functionality, then make it better by allowing you to move the vertical boundary between two programs which are sharing your screen left and right, by holding ctrl or shift or using a different mouse button.

This is one area that I think windows 7 beats ubuntu. Windows 7's "aerosnap" function works as shown in this video: youtu.be/bopeB6QbOjI. Ubuntu could implement the windows 7 functionality, then make it better by allowing you to move the vertical boundary between two programs which are sharing your screen left and right, by holding ctrl or shift or using a different mouse button.

Written by cyprys the 10 Nov 10 at 01:15.

Windows attached in the following manner should maximise and share one virtual space: there's a windows list on the bottom gnome-panel in Ubuntu - drag one window from this list and drop it on another window while holding "Super" key, repeat as needed.

When manually changing the width of one window neighbouring window should auto-resize (shrink or grow).

When certain width of the neighbouring window is approached during shrinking auto-resize of the next neighbouring window should start or the process should stop (when there are no more neighbouring windows).

Minimizing one of the attached windows should hide whole virtual space and all windows sharing it.

Unmaximising one of the attached windows should unattach only this one window and release previously occupied space so it could be redistributed between other attached windows.

Multiple virtual spaces on one workspace should be created by attaching two windows to each other (one virtual space) and then attaching two different windows to each other (second virtual space), etc.

When switching between windows (e.g. alt+tab), virtual space should be treated as one window regardless of number of actual windows sharing it.

Windows attached in the following manner should maximise and share one virtual space: there's a windows list on the bottom gnome-panel in Ubuntu - drag one window from this list and drop it on another window while holding "Super" key, repeat as needed. When manually changing the width of one window neighbouring window should auto-resize (shrink or grow). When certain width of the neighbouring window is approached during shrinking auto-resize of the next neighbouring window should start or the process should stop (when there are no more neighbouring windows). Minimizing one of the attached windows should hide whole virtual space and all windows sharing it. Unmaximising one of the attached windows should unattach only this one window and release previously occupied space so it could be redistributed between other attached windows. Multiple virtual spaces on one workspace should be created by attaching two windows to each other (one virtual space) and then attaching two different windows to each other (second virtual space), etc. When switching between windows (e.g. alt+tab), virtual space should be treated as one window regardless of number of actual windows sharing it.

Written by jeffster the 10 Nov 10 at 05:07.

If there is one window that is already set up, taking half the screen, double clicking another window's corner will fill the remaining space.

If there is one window that is already set up, taking half the screen, double clicking another window's corner will fill the remaining space.

Written by koenfloris the 14 Nov 10 at 09:33.

kubuntu already does this, just implent it in compiz and metacity

kubuntu already does this, just implent it in compiz and metacity

Written by Gonz-IT the 11 Nov 10 at 12:16.

Windows 7 implements a very neat way for window resizing and positioning. If you select a window and type WindowsKey (Super) + Right Arrow, the window will take exactly half of the space available in the right side of the screen, and so on with the WindowsKey + Left combo.

I think this is a very nice usability feature that should be implemented with Ubuntu.

Windows 7 implements a very neat way for window resizing and positioning. If you select a window and type WindowsKey (Super) + Right Arrow, the window will take exactly half of the space available in the right side of the screen, and so on with the WindowsKey + Left combo. I think this is a very nice usability feature that should be implemented with Ubuntu.

Written by thamawij pirajnaraporn the 28 Dec 10 at 08:53.

- User may increase/decrease slot numbers for a single workspace.
- Treat each slot as a cell in a spreadsheet, a user may merge them with the adjacent cells.

Currently, I'm not so clear about how it should works or the way that possibly implemented, I will add some details later.

- User may increase/decrease slot numbers for a single workspace. - Treat each slot as a cell in a spreadsheet, a user may merge them with the adjacent cells. Currently, I'm not so clear about how it should works or the way that possibly implemented, I will add some details later.

Written by thamawij pirajnaraporn the 28 Dec 10 at 09:11.

It would be nice if we can make one of our workspace split; for example, a 1280x960 may split into 4, 640x480, screens or 2, 640x960, screens as virtual attached monitors. Maximize make a window fit a monitor.

(In my head, it looks like compiz's Expo view with adjustable numbers of adjacent workspaces to show at the time)

I'm not so sure if this idea is implementable. Just share the idea so the superior in system and programming may see the way to go.

It would be nice if we can make one of our workspace split; for example, a 1280x960 may split into 4, 640x480, screens or 2, 640x960, screens as virtual attached monitors. Maximize make a window fit a monitor. (In my head, it looks like compiz's Expo view with adjustable numbers of adjacent workspaces to show at the time) I'm not so sure if this idea is implementable. Just share the idea so the superior in system and programming may see the way to go.

Written by bluenova the 23 Apr 09 at 07:44.

Rather than asking for the users password when clicking 'Check' in the update manager, ask for the password when the user clicks 'Install Updates'.

Rather than asking for the users password when clicking 'Check' in the update manager, ask for the password when the user clicks 'Install Updates'.

Written by grofaty the 25 Apr 09 at 19:13.

Now Ubuntu has an option in System | Administration | Software Sources | Update tab to install security updates automatically. Make an option to automatically install all updates.

Now Ubuntu has an option in System | Administration | Software Sources | Update tab to install security updates automatically. Make an option to automatically install all updates.

Written by tchalvakspam the 26 Aug 09 at 17:11.

The real issue is even gathering the information (which may tell you that there are no updates needed) requires the password step. So currently, there is a zero-benefit step:
Action: Open up update-manager. Effect: Nothing changes from before.
Action: Click check and put in password. Effect: Check for newer updates.
Action: Click Install updates. Effect: Finally install updates.

Because opening up update-manager is a declaration of the wish to at least check for updates, this should be revised to:

Action: Open up update-manager. Effect: perform check for updates, but download nothing.

Action: Click install updates and put in password. Effect: download & install currently "checked" updates.

The real issue is even gathering the information (which may tell you that there are no updates needed) requires the password step. So currently, there is a zero-benefit step: Action: Open up update-manager. Effect: Nothing changes from before. Action: Click check and put in password. Effect: Check for newer updates. Action: Click Install updates. Effect: Finally install updates. Because opening up update-manager is a declaration of the wish to at least check for updates, this should be revised to: Action: Open up update-manager. Effect: perform check for updates, but download nothing. Action: Click install updates and put in password. Effect: download & install currently "checked" updates.

Written by shubham the 2 Dec 11 at 14:32.

Be able to pause and check the progress by adding progress bar and a tray notification easy control and progress bar and files size has been uploaded and downloaded

Be able to pause and check the progress by adding progress bar and a tray notification easy control and progress bar and files size has been uploaded and downloaded

Written by readmanr the 6 Mar 10 at 21:00.

Move the buttons back over to the top right for the final Ubuntu 10.04 release.

Move the buttons back over to the top right for the final Ubuntu 10.04 release.

Written by Akerbos the 6 Mar 10 at 21:38.

I think it is most intuitive if the buttons are ordered the same in relation to the window center ("To close, click the outermost button"), so

Right: min-max-close

relates to

Left: close-max-min

I think it is most intuitive if the buttons are ordered the same in relation to the window center ("To close, click the outermost button"), so Right: min-max-close relates to Left: close-max-min

Written by jeffd1830 the 7 Mar 10 at 08:56.

I think having the buttons on both sides would also be a viable option. I understand that this would detract visually from the simplicity, but maybe if the buttons were subdued until the mouse hovers over the bar?

(I feel less than confident about this solution, but thought it needed mentioning.)

I think having the buttons on both sides would also be a viable option. I understand that this would detract visually from the simplicity, but maybe if the buttons were subdued until the mouse hovers over the bar? (I feel less than confident about this solution, but thought it needed mentioning.)

Written by Long Lazuli the 7 Mar 10 at 11:34.

In xubuntu, user cas can choose where are the button on the titlebar.

In xubuntu, user cas can choose where are the button on the titlebar.

Written by la_serpe the 7 Mar 10 at 16:29.

It can be movable so the user could change it intuitively

It can be movable so the user could change it intuitively

Written by Vlad_Alfredov the 8 Mar 10 at 11:13.

Well the title pretty much says it...Default is to have it on right, but to include an option in "Change Desktop Background" >> Theme >> Customize, to move the buttons to a user defined position.

Well the title pretty much says it...Default is to have it on right, but to include an option in "Change Desktop Background" >> Theme >> Customize, to move the buttons to a user defined position.

Written by marvo the 10 Mar 10 at 10:28.

There are some themes that look better when the buttons are placed on the left side (like Ambiance, Radiance and Gorilla) and there are some themes that look better with the buttons being on the right side (like Glider, Human, Clearlooks or SphereCrystal).

So i propose to set the default alignment depending on the chosen theme and make it easily switchable.

The current way to change the alignment of the buttons back to the right by typing
gconftool-2 --type string --set /apps/metacity/general/button_layout "menu:minimize,maximize,close"
is a bit tedious.

There are some themes that look better when the buttons are placed on the left side (like Ambiance, Radiance and Gorilla) and there are some themes that look better with the buttons being on the right side (like Glider, Human, Clearlooks or SphereCrystal). So i propose to set the default alignment depending on the chosen theme and make it easily switchable. The current way to change the alignment of the buttons back to the right by typing gconftool-2 --type string --set /apps/metacity/general/button_layout "menu:minimize,maximize,close" is a bit tedious.

Written by Lex the 10 Mar 10 at 11:04.

Put Close button in the corner - depending on chosen solution will be left or right corner or window.

Put Close button in the corner - depending on chosen solution will be left or right corner or window.

Written by euxneks the 11 Mar 10 at 01:31.

I think that Minimize and Maximize are more similar to the menu anyway, so put them on the left, and put the close button on the right, this harkens back to the days of old Unix and I think would still allow the theme to stand out.

I think that Minimize and Maximize are more similar to the menu anyway, so put them on the left, and put the close button on the right, this harkens back to the days of old Unix and I think would still allow the theme to stand out.

Written by i386dx the 14 Mar 10 at 12:50.

Move the Min, Max and Close-buttons back to the right.

Be able to close a window by double-clicking the window-icon at the left. This is much faster than clicking the icon and selecting 'Close' in the menu.

Move the Min, Max and Close-buttons back to the right. Be able to close a window by double-clicking the window-icon at the left. This is much faster than clicking the icon and selecting 'Close' in the menu.

Written by MoebusNet the 15 Mar 10 at 01:04.

Rationale: In VirtualBox without Guest Additions, the right-hand side of the desktop and the lower part of the desktop are not visible until you scroll. Having the above-mentioned buttons on the top-left side of the window by default makes them accessible when (not if) Guest Additions do not work/are unavailable or when scrolling for whatever reason does not work. This is especially true for development versions.

I _am_ in favor of choice, so this should be fairly easy for a user to change (preferably by GUI) to right, left or both.

Just my opinion.

Rationale: In VirtualBox without Guest Additions, the right-hand side of the desktop and the lower part of the desktop are not visible until you scroll. Having the above-mentioned buttons on the top-left side of the window by default makes them accessible when (not if) Guest Additions do not work/are unavailable or when scrolling for whatever reason does not work. This is especially true for development versions. I _am_ in favor of choice, so this should be fairly easy for a user to change (preferably by GUI) to right, left or both. Just my opinion.

Written by neblogas the 16 Mar 10 at 15:58.

Because Mark said that in 10.10 the windows will have something new in the right side, but now, there is no need to change the buttons, and this is LTS release! in 10.10 when you will finish the new mysteriuos window features on the right then you can put the buttons on the left. As I said, there is no need now to change. Its an LTS release and the people and companies won't change until the next LTS, so there won't be for them new mysteriuos windows features on the right!

Because Mark said that in 10.10 the windows will have something new in the right side, but now, there is no need to change the buttons, and this is LTS release! in 10.10 when you will finish the new mysteriuos window features on the right then you can put the buttons on the left. As I said, there is no need now to change. Its an LTS release and the people and companies won't change until the next LTS, so there won't be for them new mysteriuos windows features on the right!

Written by TrueSongMedia the 16 Mar 10 at 17:16.

Yes the button location can be changed via Terminal, but for the average user...the Terminal can be a bit scary. I think it would be appropriate to place a simple option in the Appearance Preferences window.

Something like this:
http://launchpadlibrarian.net/40647960/window_controls_position_gui.png

Yes the button location can be changed via Terminal, but for the average user...the Terminal can be a bit scary. I think it would be appropriate to place a simple option in the Appearance Preferences window. Something like this: http://launchpadlibrarian.net/40647960/window_controls_position_gui.png

Written by ichido the 17 Mar 10 at 17:53.

Move the Top Bar to the Right Side-Vertical Bar and the Bottom Bar would be on the Left Side Vertical.
This would allow for more Vertical Space.
The user would be able to Swap the Left Bar with the Right Bar and also the Size/Thickness of the Bars.
Applications could maintain the Top Bar or a Side or a Bottom bar for their Window.

Move the Top Bar to the Right Side-Vertical Bar and the Bottom Bar would be on the Left Side Vertical. This would allow for more Vertical Space. The user would be able to Swap the Left Bar with the Right Bar and also the Size/Thickness of the Bars. Applications could maintain the Top Bar or a Side or a Bottom bar for their Window.

Written by Wiplash4 the 19 Mar 10 at 12:17.

Hello
I would like to add one idea: Replace the menubar (File, Edit, View, etc.), which can be found in every window, with an icon and put that icon into the titlebar. It worked out for my terminal.
Regards

Hello I would like to add one idea: Replace the menubar (File, Edit, View, etc.), which can be found in every window, with an icon and put that icon into the titlebar. It worked out for my terminal. Regards

Written by Wiplash4 the 19 Mar 10 at 16:40.

I figured out that the status bar is only filled up to 1 / 4. Why not put those messages displayed in the status bar in the title bar?

I figured out that the status bar is only filled up to 1 / 4. Why not put those messages displayed in the status bar in the title bar?

Written by a_pirard the 20 Mar 10 at 03:14.

Modify all applications to be consistent with Lucid : move all close buttons to the left, for example, OpenOffice document close, Firefox tab close, File Explorer side pane close, etc... etc...

Modify all applications to be consistent with Lucid : move all close buttons to the left, for example, OpenOffice document close, Firefox tab close, File Explorer side pane close, etc... etc...

Written by luojie-dune the 20 Mar 10 at 21:01.

Instead of corner, make it POSSIBLE to place buttons in the MIDDLE.

I knew there is no such a solution according to "ewmh".

But, I guess most people have their cursor in the middle of a window for most of the time they using it.

Instead of corner, make it POSSIBLE to place buttons in the MIDDLE. I knew there is no such a solution according to "ewmh". But, I guess most people have their cursor in the middle of a window for most of the time they using it.

Written by LukeM33P the 25 Mar 10 at 01:13.

Compiz managers and decorators are already effective at options. Placing the Metacity and Kwin options in Emerald Decorator manager, which would be preinstalled, along with CCSM (or a custom replacement) would be the solution, with CCSM/replacement simplified to look like (in functionality and basic organization) the KDE settings manager, but using default schemes and such, of course.

For KDE users, alongside the CCSM/replacement, the interface would be integrated into the System Settings, just like the traditional settings.

The reason I propose this is because options, while not easy to find and configure (and why I propose the reorg) are very powerful. Setting up Metacity and KWin to show up as options and adding the appropriate settings, if necessary, seems to make sense (to me) as a long-term solution. The operating system needs to seem as encompassing as KDE or even more so, and combining these options so that the system is even more universal would be a step towards this.

An addition to the application of managing the system title bar like the KDE or GNOME dashboards would be similarly useful, and may be all of this potential solution that should be used. Default should stay in line with last-gen human theme, even if the colors and buttons look different.

Compiz managers and decorators are already effective at options. Placing the Metacity and Kwin options in Emerald Decorator manager, which would be preinstalled, along with CCSM (or a custom replacement) would be the solution, with CCSM/replacement simplified to look like (in functionality and basic organization) the KDE settings manager, but using default schemes and such, of course. For KDE users, alongside the CCSM/replacement, the interface would be integrated into the System Settings, just like the traditional settings. The reason I propose this is because options, while not easy to find and configure (and why I propose the reorg) are very powerful. Setting up Metacity and KWin to show up as options and adding the appropriate settings, if necessary, seems to make sense (to me) as a long-term solution. The operating system needs to seem as encompassing as KDE or even more so, and combining these options so that the system is even more universal would be a step towards this. An addition to the application of managing the system title bar like the KDE or GNOME dashboards would be similarly useful, and may be all of this potential solution that should be used. Default should stay in line with last-gen human theme, even if the colors and buttons look different.

Written by 2cute4u the 25 Mar 10 at 03:37.

XFCE has for many years had a very easy convient way to configure the placment of titlebar buttons. See.http://www.xfce.org/documentation/4.2/manuals/xfwm4#wm-settings
It would not be too difficult to add somethng like this to gnome; that way everyone can be happy.

XFCE has for many years had a very easy convient way to configure the placment of titlebar buttons. See.http://www.xfce.org/documentation/4.2/manuals/xfwm4#wm-settings It would not be too difficult to add somethng like this to gnome; that way everyone can be happy.

Written by MisterLinOx the 26 Mar 10 at 21:52.

Have the min, max, close buttons on both sides of the title bar, but hide them. The only time they should show is on mouseover of the bar, but depending on which side you mouseover decides which side the buttons show.

For example, cursor closer to the left side? Mouse over the top-left and the buttons will appear. Vice-versa for the right side.

Have the min, max, close buttons on both sides of the title bar, but hide them. The only time they should show is on mouseover of the bar, but depending on which side you mouseover decides which side the buttons show. For example, cursor closer to the left side? Mouse over the top-left and the buttons will appear. Vice-versa for the right side.

Written by emucosmos the 27 Mar 10 at 03:11.

make apear a messagebox in the begining of the instalation asking where do we want to have those buttons, coz personally I love the new mac style, but considering the ubuntu objectives, it's a good option to let the users choice.

make apear a messagebox in the begining of the instalation asking where do we want to have those buttons, coz personally I love the new mac style, but considering the ubuntu objectives, it's a good option to let the users choice.

Written by darkham the 29 Mar 10 at 08:23.

Let user chose on the First Run, after installation.

Let user chose on the First Run, after installation.

Written by tomjb24 the 3 Apr 10 at 09:25.

Hover over the window border, click the middle mouse button, scroll to choose (close, minimise, maximise)

Hover over the window border, click the middle mouse button, scroll to choose (close, minimise, maximise)

Written by rrnwexec the 3 Apr 10 at 20:26.

Create a version of Ubuntu for those who like the (standard) Ubuntu desktop's "look and feel" just the way it is. Solicit Mark's (SABDFL) endorsement.

Enjoy how growingly quaint it feels as time passes by!

Create a version of Ubuntu for those who like the (standard) Ubuntu desktop's "look and feel" just the way it is. Solicit Mark's (SABDFL) endorsement. Enjoy how growingly quaint it feels as time passes by!

Written by jase21 the 4 Apr 10 at 11:54.

Make Mac styled menu bar which is available in KDE. The current active windows menu appears on the bar. So no accidental closing of windows.

Or move the window control buttons to the right.

Make Mac styled menu bar which is available in KDE. The current active windows menu appears on the bar. So no accidental closing of windows. Or move the window control buttons to the right.

Written by Jon Monreal the 17 Apr 10 at 23:49.

Please note that this is not an idea for the imminent release of 10.04, but would be better included in the next update ISO.

Experienced users already know how to change the buttons back to the original location, so server installations shouldn't be so much of a problem.

For absolute beginner users, the first slide in the installation slideshow could be one explaining the benefits of having the buttons on the left side and asking the user to choose what they could like to do.

In the minimal install, it would also be easy to add a simple option (most users using the minimal install are probably fairly experienced).

This would solve the real issue here: beginners possibly not using Ubuntu at all because it changes something.

Please note that this is not an idea for the imminent release of 10.04, but would be better included in the next update ISO. Experienced users already know how to change the buttons back to the original location, so server installations shouldn't be so much of a problem. For absolute beginner users, the first slide in the installation slideshow could be one explaining the benefits of having the buttons on the left side and asking the user to choose what they could like to do. In the minimal install, it would also be easy to add a simple option (most users using the minimal install are probably fairly experienced). This would solve the real issue here: beginners possibly not using Ubuntu at all because it changes something.

Written by land_grab the 5 May 10 at 23:23.

I found this extremely easy fix how to move the min, max, and close buttons back to the right side.


http://www.howtogeek.com/howto/13535/move-window-buttons-back-to-the-right-in-u buntu-10.04/

Even I was able to follow these directions and make it happen!

I found this extremely easy fix how to move the min, max, and close buttons back to the right side. http://www.howtogeek.com/howto/13535/move-window-buttons-back-to-the-right-in-ubuntu-10.04/ Even I was able to follow these directions and make it happen!

Written by turbolad the 5 Jul 10 at 15:42.

As per title. Buttons to the right by default, with an option to move to the left.

Don't forget to keep the little circle, which when clicked on, has options such as "Always On Top", "Move to Workspace Right" etc. These options should never be removed and I think the 3 buttons should be on the right by default, as most newbies are familiar with that setup.

As per title. Buttons to the right by default, with an option to move to the left. Don't forget to keep the little circle, which when clicked on, has options such as "Always On Top", "Move to Workspace Right" etc. These options should never be removed and I think the 3 buttons should be on the right by default, as most newbies are familiar with that setup.

Written by baretobareto the 3 Aug 10 at 20:31.

Fisrt of all, sorry for my English.

Why we really needs buttons to the right? Well theres no real difference between having your buttons on the left or on the right, its just a matter of have the enough time to get used to one position or another.
But what about if we have these button in a complete new position.
What about having min, max, close buttons on the right BUT in the lower side of the windows instead of the upper side.

If you think about it, when you open a document or a web-page, you need to scroll down to really knows if that document is what you are looking for. When a document is too long, you need to use the scroll down arrow. So your mouse-arrow will be closer to the lower right of the window instead of the upper side of the window.
If you want to look to a minimize window that you think it would be not useful anymore, you need to un-minimize this window. If the buttons are in the lower right of the window it will be needed much less movement of your hand to close it after un-minimize because the close button will be closer to the task bar.

<a target="_blank" title="ImageShack - Image And Video Hosting" href="http://img641.imageshack.us/i/screenshot5qs.png/"><img src="http://img641.imageshack.us/img641/8462/screenshot5qs.png" border="0"/></a> Fisrt of all, sorry for my English. Why we really needs buttons to the right? Well theres no real difference between having your buttons on the left or on the right, its just a matter of have the enough time to get used to one position or another. But what about if we have these button in a complete new position. What about having min, max, close buttons on the right BUT in the lower side of the windows instead of the upper side. If you think about it, when you open a document or a web-page, you need to scroll down to really knows if that document is what you are looking for. When a document is too long, you need to use the scroll down arrow. So your mouse-arrow will be closer to the lower right of the window instead of the upper side of the window. If you want to look to a minimize window that you think it would be not useful anymore, you need to un-minimize this window. If the buttons are in the lower right of the window it will be needed much less movement of your hand to close it after un-minimize because the close button will be closer to the task bar. As you see there are some reason to have buttons in the lower side of the window BUT I know there are others to have this buttons on others positions. So, why not to put this buttons in a completely new position. This could be a ubuntu-only-feature just like the recycle bin in the task bar is a ubuntu-only-feature.

Written by risbac the 15 Jan 09 at 13:04.

I think that when it comes bundled on computers like Dell's ones, there should be some kind of introduction on the desktop the first time you boot the computer. Some kind of "Coming from Windows? Learn how to do the same in Ubuntu".

Then it should explain the biggest differences:

-Openoffice is compatible with Word, you can save docs using Office format
-you don't use Windows softwares or CDs anymore
-you don't download & install softwares from internet like on Windows,
but use the built-in software (and you give more details and
advantages)
-you don't need to install the drivers and crap softwares from
hardware vendors just to access internet or install a printer
-etc... etc...

As usually, to have good ideas is great, but if you don't promote them the good way, it's just useless. Maybe Canonical should consider that and work with Dell to make sure the transition is easier. That would benefit both to Dell and to Canonical. Currently new users are a bit
left in the mist. I agree that it's possible to find this info, but you have to look for it. I think it should be displayed on the desktop, when you boot for the first time.

I think that when it comes bundled on computers like Dell's ones, there should be some kind of introduction on the desktop the first time you boot the computer. Some kind of "Coming from Windows? Learn how to do the same in Ubuntu". Then it should explain the biggest differences: -Openoffice is compatible with Word, you can save docs using Office format -you don't use Windows softwares or CDs anymore -you don't download & install softwares from internet like on Windows, but use the built-in software (and you give more details and advantages) -you don't need to install the drivers and crap softwares from hardware vendors just to access internet or install a printer -etc... etc... As usually, to have good ideas is great, but if you don't promote them the good way, it's just useless. Maybe Canonical should consider that and work with Dell to make sure the transition is easier. That would benefit both to Dell and to Canonical. Currently new users are a bit left in the mist. I agree that it's possible to find this info, but you have to look for it. I think it should be displayed on the desktop, when you boot for the first time.

Written by Oli the 15 Jan 09 at 15:05.

While I think there should be a full tour for new users, I think it can be made better for more than just Dell/other-preinstall customers.

I thinking a full "support centre" where users can learn how to do things, and to an extent, automate certain initial-setup tasks.

One example would be networking. Give the user tasks based on what hardware is available. If they ask for wireless networking, check to see if the driver is working. If it's not, get ndiswrapper set up. Finalise by walking them through the network manager applet.

Similar things for printers, scanners, phones, alternative software, Wine, codecs, etc.

The most important thing (in my eyes) would be some form of IRC integration. There are hundreds of people in #ubuntu that can help so why not leverage it better?

The interface has to be simple. I'm thinking the user initially just sees a text box asking them what's wrong. They type their question, click a button. Behind the scenes, it connects to IRC as guest-3423483. We all hide that from the user. When somebody replies to them (prefixing their name) that message gets shown to the user.

While I think there should be a full tour for new users, I think it can be made better for more than just Dell/other-preinstall customers. I thinking a full "support centre" where users can learn how to do things, and to an extent, automate certain initial-setup tasks. One example would be networking. Give the user tasks based on what hardware is available. If they ask for wireless networking, check to see if the driver is working. If it's not, get ndiswrapper set up. Finalise by walking them through the network manager applet. Similar things for printers, scanners, phones, alternative software, Wine, codecs, etc. The most important thing (in my eyes) would be some form of IRC integration. There are hundreds of people in #ubuntu that can help so why not leverage it better? The interface has to be simple. I'm thinking the user initially just sees a text box asking them what's wrong. They type their question, click a button. Behind the scenes, it connects to IRC as guest-3423483. We all hide that from the user. When somebody replies to them (prefixing their name) that message gets shown to the user.

Written by Primož Papič the 16 Jan 09 at 00:26.

eugene2k has provided an interesting story: http://www.wkowtv.com/Global/story.asp?S=9667184 now it dosen't say how well specified that the computer uses Ubuntu instead of Windows, but I guess not enough as this probably wouldn't happen if it would.
So Canonical should demand that vendors specify and educate users that the computer that they are buying has Ubuntu instead of Windows.
And that vendors should provide informations that are presented in solution #1.

eugene2k has provided an interesting story: http://www.wkowtv.com/Global/story.asp?S=9667184 now it dosen't say how well specified that the computer uses Ubuntu instead of Windows, but I guess not enough as this probably wouldn't happen if it would. So Canonical should demand that vendors specify and educate users that the computer that they are buying has Ubuntu instead of Windows. And that vendors should provide informations that are presented in solution #1.

Written by tchalvakspam the 23 Jan 09 at 18:29.

File-format issues should be cleared up as the attempted use occurs, not in text that the user may never read or connect to the actions that they do later, so:

First attempted use of an exe file should point at Add/Remove Software as a better solution, and then offer to install Wine.

Opening a .doc file in open office should result in defaulting to saving in .doc format, and OOo already provides an explanatory "microsoft format document files aren't very open, are you sure you want to save in that format" message.

File-format issues should be cleared up as the attempted use occurs, not in text that the user may never read or connect to the actions that they do later, so: First attempted use of an exe file should point at Add/Remove Software as a better solution, and then offer to install Wine. Opening a .doc file in open office should result in defaulting to saving in .doc format, and OOo already provides an explanatory "microsoft format document files aren't very open, are you sure you want to save in that format" message.

Written by tchalvakspam the 23 Jan 09 at 18:40.

The "Add/Remove Software" concept has been polluted by windows' horrible non-open-repository methods of dealing with installation.
In windows, Add/Remove Software effectively means: YOU-CAN-ONLY-REMOVE-SOFTWARE-HERE.
In ubuntu, Add/Remove Software effectively means: YOU-CAN-ADD-99999-DIFFERENT-APPLICATIONS-HERE. (Personally I rarely if ever bother to even uninstall software, since there is rarely any disadvantage to having it lying around dormant, a major contrast with Windows).

The ability to add free applications in a few clicks is the BIGGEST advantage of Ubuntu, but it is under-emphasized and under-promoted.

Making this ability a more obvious and clearly different-from-windows feature of Ubuntu would be an all-around win.

The "Add/Remove Software" concept has been polluted by windows' horrible non-open-repository methods of dealing with installation. In windows, Add/Remove Software effectively means: YOU-CAN-ONLY-REMOVE-SOFTWARE-HERE. In ubuntu, Add/Remove Software effectively means: YOU-CAN-ADD-99999-DIFFERENT-APPLICATIONS-HERE. (Personally I rarely if ever bother to even uninstall software, since there is rarely any disadvantage to having it lying around dormant, a major contrast with Windows). The ability to add free applications in a few clicks is the BIGGEST advantage of Ubuntu, but it is under-emphasized and under-promoted. Making this ability a more obvious and clearly different-from-windows feature of Ubuntu would be an all-around win.

Written by JoeLeKiffeur the 29 Jan 09 at 01:51.

(My English level is not very good)

1) Many beginners in the world of GNU/Linux think Ubuntu is not difficult to understand the GUI, but can be lost by a lack of documentation. I note that there are too much GUI softwares doesn't have help, or haven't the famous F1 shortcut.

2) Windows Vista have a great search feature in documentation pages. This feature can search documentation in all pages of all softwares I think. We can't waste our time with this help system.

3) A general tutorial icon in the desktop could be a good solution because beginners could find many informations about how works the system, and how to be helped offline (Linuxian must be easily helped despite internet connexions problems).

(My English level is not very good) 1) Many beginners in the world of GNU/Linux think Ubuntu is not difficult to understand the GUI, but can be lost by a lack of documentation. I note that there are too much GUI softwares doesn't have help, or haven't the famous F1 shortcut. 2) Windows Vista have a great search feature in documentation pages. This feature can search documentation in all pages of all softwares I think. We can't waste our time with this help system. 3) A general tutorial icon in the desktop could be a good solution because beginners could find many informations about how works the system, and how to be helped offline (Linuxian must be easily helped despite internet connexions problems).

Written by Warbo the 29 Jan 09 at 22:12.

The Ubuntu help wiki (help.ubuntu.com and help.ubuntu.com/community) is a great resource for help.

Whilst forums and IRC are good for specific issues, they're not too good as a reference since you need to wade through everyone else's specific problems, and often don't find much reference-style documentation.

The Help Wiki is organised and categorised, constantly being updated and is an informative resource about the Ubuntu system.

I was tempted to say that only the networking pages should be packaged, to help people get online and access the rest, but that's rather elitist since not everyone has Internet access.

To keep size down only the latest revision is needed, only pages applying to default setups and common needs (ie. keep restricted formats installation instructions, don't need Enemy Territory installation instructions), only a static format is needed (ie. no Wiki software) and only those applying to the release of Ubuntu they're packaged for are needed. This should be a reasonable size when compressed with 7zip.

The Ubuntu help wiki (help.ubuntu.com and help.ubuntu.com/community) is a great resource for help. Whilst forums and IRC are good for specific issues, they're not too good as a reference since you need to wade through everyone else's specific problems, and often don't find much reference-style documentation. The Help Wiki is organised and categorised, constantly being updated and is an informative resource about the Ubuntu system. I was tempted to say that only the networking pages should be packaged, to help people get online and access the rest, but that's rather elitist since not everyone has Internet access. To keep size down only the latest revision is needed, only pages applying to default setups and common needs (ie. keep restricted formats installation instructions, don't need Enemy Territory installation instructions), only a static format is needed (ie. no Wiki software) and only those applying to the release of Ubuntu they're packaged for are needed. This should be a reasonable size when compressed with 7zip.

Written by tn071280 the 3 Feb 09 at 12:32.

On the top panel there should be a quick lanch of an irq client. At the first time it should open a wizard that aid users to configure the right channel (distro and language).

On the top panel there should be a quick lanch of an irq client. At the first time it should open a wizard that aid users to configure the right channel (distro and language).

Written by gcbzzzz the 4 Feb 09 at 02:05.

Teaching the user that linux you can't break anything like windows (flashing registry edit warnings), and it's all just a bunch of simple text files, will make more good then an introduction that 110% of the experienced users will just curse to death every time.

Makes every GUI app tells what it's doing. Or at least put help button near the action that tells how/what it's doing.

Something like gparted does with file/device names and commands would be awesome.

E.g. network manager, it should at least mention that when you add a interface there, you are adding a couple of lines to /etc/network/interfaces. Who here knows that? I only know because i used older distros. The point is, if the user wants to do something that does not have a visible button, he will panic. knowing the files help him search online.

Teaching the user that linux you can't break anything like windows (flashing registry edit warnings), and it's all just a bunch of simple text files, will make more good then an introduction that 110% of the experienced users will just curse to death every time. Makes every GUI app tells what it's doing. Or at least put help button near the action that tells how/what it's doing. Something like gparted does with file/device names and commands would be awesome. E.g. network manager, it should at least mention that when you add a interface there, you are adding a couple of lines to /etc/network/interfaces. Who here knows that? I only know because i used older distros. The point is, if the user wants to do something that does not have a visible button, he will panic. knowing the files help him search online.

Written by nloewen the 11 Feb 09 at 23:47.

As part of the solution, there should be a utility were a user can search for different hardware that they are thinking about buying. with different categories for printers, scanners, wireless cards, etc. It should tell the user weather the hardware will be automatically detected, needs to be set up, needs some form of windows driver, needs a driver available from the manufacturers web sight, is not supported, etc. and should give instructions on how to set it up. This would be extremely helpful for the new user who doesn't know what hardware to buy or how to set it up in ubuntu.

As part of the solution, there should be a utility were a user can search for different hardware that they are thinking about buying. with different categories for printers, scanners, wireless cards, etc. It should tell the user weather the hardware will be automatically detected, needs to be set up, needs some form of windows driver, needs a driver available from the manufacturers web sight, is not supported, etc. and should give instructions on how to set it up. This would be extremely helpful for the new user who doesn't know what hardware to buy or how to set it up in ubuntu.

Written by PC Expert 001 the 13 Feb 09 at 14:35.

Because of all the old computers out there, some people are repairing them to make a small profit. Because they can't spend $100s on Windows, as well as the compatibility issues with older systems, they look at Ubuntu to run them.

Because it is a good idea to test the computers, you need to be able to boot into the OS. But, because of an introduction, it would also have run and not played, so there should be an option that you can tell it to run the introduction on the next boot from in the OS.

Because of all the old computers out there, some people are repairing them to make a small profit. Because they can't spend $100s on Windows, as well as the compatibility issues with older systems, they look at Ubuntu to run them. Because it is a good idea to test the computers, you need to be able to boot into the OS. But, because of an introduction, it would also have run and not played, so there should be an option that you can tell it to run the introduction on the next boot from in the OS.

Written by jamessnell the 13 Feb 09 at 17:27.

There should be a basic integrated/offline tour feature intended to get users online & browsing.

Beyond that, there should be an interface/hooks in to the already well-established online documentation & user forms.

High-value documents need to be prioritised so the user has to dig deep to be exposed to untested or really convoluted solutions/instructions.

There should be a basic integrated/offline tour feature intended to get users online & browsing. Beyond that, there should be an interface/hooks in to the already well-established online documentation & user forms. High-value documents need to be prioritised so the user has to dig deep to be exposed to untested or really convoluted solutions/instructions.

Written by kazagistar the 13 Feb 09 at 22:23.

Add a button to the loading bar of the installation. If the user wants, while they are waiting for their computer to be installed, they can watch some videos and read about exactly what they are getting into. It sure beats watching a bar slowly move forward, and is a much more elegant and seamless experience.

Add a button to the loading bar of the installation. If the user wants, while they are waiting for their computer to be installed, they can watch some videos and read about exactly what they are getting into. It sure beats watching a bar slowly move forward, and is a much more elegant and seamless experience.

Written by shane.halloran the 17 Feb 10 at 20:47.

I know it may sound too simple, but directly saying at the start of any tutorial "Ubuntu is better than Windows, here's why...", and then stating very clearly why, would be an effective approach to reducing the number of users switching-back to Windows.

Of course, factors such as security, speed, etc are mentioned.

I know it may sound too simple, but directly saying at the start of any tutorial "Ubuntu is better than Windows, here's why...", and then stating very clearly why, would be an effective approach to reducing the number of users switching-back to Windows. Of course, factors such as security, speed, etc are mentioned.

Written by smenjas the 29 Feb 08 at 01:34.

If an application needs my attention, it's task bar button should simply pulse so I can turn my attention to it when I'm ready. Pidgin does this; why not everything else?

If an application needs my attention, it's task bar button should simply pulse so I can turn my attention to it when I'm ready. Pidgin does this; why not everything else?

Written by smenjas the 5 Feb 09 at 09:59.

On Mac OS X, Growl provides a system-wide way to notify the user that something has happened without getting in the way. I'd very much like to see Ubuntu adopt something like that.

On Mac OS X, Growl provides a system-wide way to notify the user that something has happened without getting in the way. I'd very much like to see Ubuntu adopt something like that.

Written by runesvend the 29 Mar 09 at 17:40.

I'm imagining that pressing and holding a button (Control, Alt, or some other key of choice) while clicking on a program launcher icon in the panel, would make the window of the newly launched program appear _behind_ the currently active window. That way, I can quickly and easily press Alt+Tab to get to the newly opened application window when I wish to.

I'm imagining that pressing and holding a button (Control, Alt, or some other key of choice) while clicking on a program launcher icon in the panel, would make the window of the newly launched program appear _behind_ the currently active window. That way, I can quickly and easily press Alt+Tab to get to the newly opened application window when I wish to.

Written by MathUHenry the 9 Jul 09 at 18:09.

When a program is launched, it is granted the "active window" status. I would like programs to not be able to grant themselves the "active window" status. When another program is selected, the loading program is moved to the background and should be forced to stay there (until the user selects it). When I press ctrl alt d, I want it to minimize until I select it.

In short, don't let programs bring themselves to the front (even update manager). If a program MUST notify me of something, then I think the new notification system is the coolest/most-convenient-ever way to do it.

When a program is launched, it is granted the "active window" status. I would like programs to not be able to grant themselves the "active window" status. When another program is selected, the loading program is moved to the background and should be forced to stay there (until the user selects it). When I press ctrl alt d, I want it to minimize until I select it. In short, don't let programs bring themselves to the front (even update manager). If a program MUST notify me of something, then I think the new notification system is the coolest/most-convenient-ever way to do it.

Written by pererik87 the 6 Jan 10 at 09:44.

The "preload window" should set the order position and workspace, then the program should not be able to steal focus or change workspace any more after started. If a program does not have a preload screen and uses long time to start it should be given a container or something.

In other words: programs should be locked to the order and workspace they get when someone start them unless user changer the order.

Gimp is an example of a program that takes long time to start and then steals your focus, even if you change workspace and select unlimited of other windows.

The "preload window" should set the order position and workspace, then the program should not be able to steal focus or change workspace any more after started. If a program does not have a preload screen and uses long time to start it should be given a container or something. In other words: programs should be locked to the order and workspace they get when someone start them unless user changer the order. Gimp is an example of a program that takes long time to start and then steals your focus, even if you change workspace and select unlimited of other windows.

Written by orblivion the 16 Sep 09 at 22:22.

1) More things should pop under. This could of course be annoying if you're trying to run a program and have to switch windows every time.

2) Warning periods. If things pop over, I need to have a warning. Maybe in Compiz, windows could fade in for a certain period of time (.5 to 1 seconds, user configured) without yet having focus. In Metacity, they could disable input controls for the same period. This interrupts what I'm doing, but at least I notice before I inadvertently do anything.

For notifications or dialogs, I think #1 would be just fine. I'll get to the window when I have a chance. #2 would be good for programs I deliberately open, or dialogs that really need my attention.

1) More things should pop under. This could of course be annoying if you're trying to run a program and have to switch windows every time. 2) Warning periods. If things pop over, I need to have a warning. Maybe in Compiz, windows could fade in for a certain period of time (.5 to 1 seconds, user configured) without yet having focus. In Metacity, they could disable input controls for the same period. This interrupts what I'm doing, but at least I notice before I inadvertently do anything. For notifications or dialogs, I think #1 would be just fine. I'll get to the window when I have a chance. #2 would be good for programs I deliberately open, or dialogs that really need my attention.

Written by owenduffy the 3 Oct 09 at 14:44.

Why not prevent windows from stealing focus, but have their icons on the Gnome panel (or awn, or whatever) blink or otherwise make themselves conspicuous? That way the user is aware that another window requires attention, but doesn't have to deal with it immediately, either to respond to it or close/minimise it.

Why not prevent windows from stealing focus, but have their icons on the Gnome panel (or awn, or whatever) blink or otherwise make themselves conspicuous? That way the user is aware that another window requires attention, but doesn't have to deal with it immediately, either to respond to it or close/minimise it.

Written by xubaj the 10 Nov 09 at 12:38.

while typing, no window should be allowed to steal focus until the keyboard is unused for about 2 secs. instead they should pop-under.

while typing, no window should be allowed to steal focus until the keyboard is unused for about 2 secs. instead they should pop-under.

Written by xubaj the 10 Nov 09 at 12:44.

if windows want to pop-up and steal focus, they should be displayed highlighted in background (or very glassy in foreground), so you know that a window wants to get focus. but the windows stay in background until you stop typing. when you stop typing they all appear in there original order.

if windows want to pop-up and steal focus, they should be displayed highlighted in background (or very glassy in foreground), so you know that a window wants to get focus. but the windows stay in background until you stop typing. when you stop typing they all appear in there original order.

Written by lapgoat the 13 Oct 10 at 12:09.

The window manager should watch mouse movement and keyboard usage. If there has been a keystroke in the last second or the mouse pointer has moved more than a few pixels in the last half second, assume that the user may continue typing or click. Place the new popup at the lowest Z-level to minimize risk of accidentally clicking and retain keyboard focus on the current window.

If an application is in need of input but has been denied it, flash the task switcher or add an icon to the notification area to get the user's attention. If the application urgently needs attention, send a notification to via the selected preferred method (libnotify or such).

If there hasn't been any input in the above timeframes, the new window can be granted the ability to pop up at the top Z-level, but it should be denied keyboard focus until the user interacts with it.

If the user has requested an application window to open, the expected behavior is that the new window will come to the top and be given focus. Some heuristics should be developed to maximize the probability that this expected behavior occurs, otherwise the window manager becomes difficult to use.

The window manager should watch mouse movement and keyboard usage. If there has been a keystroke in the last second or the mouse pointer has moved more than a few pixels in the last half second, assume that the user may continue typing or click. Place the new popup at the lowest Z-level to minimize risk of accidentally clicking and retain keyboard focus on the current window. If an application is in need of input but has been denied it, flash the task switcher or add an icon to the notification area to get the user's attention. If the application urgently needs attention, send a notification to via the selected preferred method (libnotify or such). If there hasn't been any input in the above timeframes, the new window can be granted the ability to pop up at the top Z-level, but it should be denied keyboard focus until the user interacts with it. If the user has requested an application window to open, the expected behavior is that the new window will come to the top and be given focus. Some heuristics should be developed to maximize the probability that this expected behavior occurs, otherwise the window manager becomes difficult to use.

Written by der_hede the 15 Oct 10 at 12:14.

There are many reasons why focus stealing is annoying. One is you have to find your old window if you do not want to use the new window directly.

The other is the group of simple popup windows asking you short questions or inform you about something.

While the first one is no problem, you still can switch to your desired window, the second one is very bad if you are writing a letter or something else.

Imagine the popup "Are you shure you want to do something [no][yes]" pops up while you are writing something and the default value you are accepting with [space] (an often pressed key in writings) is not the one you intentionally wanted to press...

For the later one there's a KISS solution: No one can react to any new windows in a certain time period. Lets say 1-2 Seconds. So there's simply no chance there is any usable input to such windows inside a 1-2 Seconds time frame from the creation of the window.

So one solution would be to simply ignore all new input to new windows for 1-2 Seconds.

This could be as simple as a default option for "Popup" Style Windows in GTK/Qt/etc.

There are many reasons why focus stealing is annoying. One is you have to find your old window if you do not want to use the new window directly. The other is the group of simple popup windows asking you short questions or inform you about something. While the first one is no problem, you still can switch to your desired window, the second one is very bad if you are writing a letter or something else. Imagine the popup "Are you shure you want to do something [no][yes]" pops up while you are writing something and the default value you are accepting with [space] (an often pressed key in writings) is not the one you intentionally wanted to press... For the later one there's a KISS solution: No one can react to any new windows in a certain time period. Lets say 1-2 Seconds. So there's simply no chance there is any usable input to such windows inside a 1-2 Seconds time frame from the creation of the window. So one solution would be to simply ignore all new input to new windows for 1-2 Seconds. This could be as simple as a default option for "Popup" Style Windows in GTK/Qt/etc.

Written by Lachu the 16 Oct 10 at 13:54.

Instead of allowing to steal focus, only suggest user to switch onto new window or window asking for focus. Solution is already implemented in KDE SC - the task item will higlights, but we needs some think more visible.

I suggest to show transparent preview of window asking for focus in top-right corner of screen. Desktop environment will display this preview only, when keyboard/mouse are inactive for long period of time. Also, it will be displayed for few second after asking for focus.

Instead of allowing to steal focus, only suggest user to switch onto new window or window asking for focus. Solution is already implemented in KDE SC - the task item will higlights, but we needs some think more visible. I suggest to show transparent preview of window asking for focus in top-right corner of screen. Desktop environment will display this preview only, when keyboard/mouse are inactive for long period of time. Also, it will be displayed for few second after asking for focus.

Written by Aielyn the 19 Oct 10 at 06:46.

It seems the problem is that you want to not lose the *focus* on the current window, but you also want to be able to quickly see and react to new windows that pop up.

Why not essentially push new windows to the top of the stack as far as display is concern, but keep the focus on the original window? Then, perhaps a time-based element could allow the system to automatically switch to the new window if no input is occurring within the set time. Another alternative would be to have it pushed to the top of the display stack, but after a set number of seconds, it would minimise (showing the minimise effect) and put a highlight on the tab for the new window.

This would be an option, of course, and the time-based element would be an option as well.

It seems the problem is that you want to not lose the *focus* on the current window, but you also want to be able to quickly see and react to new windows that pop up. Why not essentially push new windows to the top of the stack as far as display is concern, but keep the focus on the original window? Then, perhaps a time-based element could allow the system to automatically switch to the new window if no input is occurring within the set time. Another alternative would be to have it pushed to the top of the display stack, but after a set number of seconds, it would minimise (showing the minimise effect) and put a highlight on the tab for the new window. This would be an option, of course, and the time-based element would be an option as well.

Written by shadowentity the 28 Sep 11 at 09:31.

a plug-in interface to use a module that makes decisions about the z-level, focus and maybe even the workspace and/or window-size and/or orientation of the window that is about coming up.

a configurable default module should exist and be used by default to apply simple rulesets such as "never", "always", "only raise'", etc. and offer an option to eval a script function or something.

it would keep simple things simple and make complex things possible.

a plug-in interface to use a module that makes decisions about the z-level, focus and maybe even the workspace and/or window-size and/or orientation of the window that is about coming up. a configurable default module should exist and be used by default to apply simple rulesets such as "never", "always", "only raise'", etc. and offer an option to eval a script function or something. it would keep simple things simple and make complex things possible.

Written by gaxi the 21 Oct 11 at 07:27.

CompizConfig Settings Manager > General > General Options > Focus & Raise Behaviour
Focus Prevention Level = "Very High"

For me this works perfectly, new windows do not steal my focus any more when typing.
I'm using 11.04

CompizConfig Settings Manager > General > General Options > Focus & Raise Behaviour Focus Prevention Level = "Very High" For me this works perfectly, new windows do not steal my focus any more when typing. I'm using 11.04

Written by mydoghasworms the 25 Nov 11 at 07:37.

Provide a key binding to open Rhythmbox again once it is hidden. Should work as a toggle to show and hide.

Ideally this should work for other music players as well, but seeing as Rhythmbox is again going to be the default in the next release, it would be great if it could be made to work with Rhythmbox for now.

Provide a key binding to open Rhythmbox again once it is hidden. Should work as a toggle to show and hide. Ideally this should work for other music players as well, but seeing as Rhythmbox is again going to be the default in the next release, it would be great if it could be made to work with Rhythmbox for now.

Written by freexe the 3 Sep 08 at 16:34.

Ubuntu Brainstorm was updated in January 2009. Since the idea #12763 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #12763 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by ubbrainy the 14 Mar 10 at 22:05.

Something like this: http://www.mozilla-europe.org/img/en/tignish/features/find.png

It's much easier to handle, stays open, and doesn't bother you...

Something like this: http://www.mozilla-europe.org/img/en/tignish/features/find.png It's much easier to handle, stays open, and doesn't bother you...

Written by annex666 the 26 Mar 10 at 12:40.

I often find myself editing a number of files at once and think an option to search in all files would be really useful - rather than having to search in each file separately.

I often find myself editing a number of files at once and think an option to search in all files would be really useful - rather than having to search in each file separately.

Written by Penguin Guy the 29 Mar 10 at 19:50.

Like #1, but also include a dropdown that'll extend the box to include the usual options such as 'match case' and 'match entire word only'.

Like #1, but also include a dropdown that'll extend the box to include the usual options such as 'match case' and 'match entire word only'. <img src="http://dl.dropbox.com/u/1217030/Ubuntu%20Brainstorm/Chrome%20Find%20Dropdown.png" />

Written by Penguin Guy the 29 Mar 10 at 20:17.

Like #1, but also add a similar feature for the find and replace dialogue.

Like #1, but also add a similar feature for the find and replace dialogue. <img src="http://dl.dropbox.com/u/1217030/Ubuntu%20Brainstorm/Chrome%20Find%20Replace.png" />

Written by SuNk8 the 11 Apr 10 at 09:43.

GNOME Do is quite popular. So, instead of creating another application, we could simply integrate GNOME DO Search into Nautilus. That was we can search not only our files but also all our bookmarks, mail and such other stuff.

And if I'm not mistaken, GNOME DO is maintained by Canonical and is under heavy development.

GNOME Do is quite popular. So, instead of creating another application, we could simply integrate GNOME DO Search into Nautilus. That was we can search not only our files but also all our bookmarks, mail and such other stuff. And if I'm not mistaken, GNOME DO is maintained by Canonical and is under heavy development.

Written by avgUser the 7 Dec 11 at 08:31.

According to a survey done by codestyle.org,

Arial
Arial Black
Arial Narrow
Comic Sans MS
Courier New
Georgia
Impact
Lucida Sans
Tahoma
Times New Roman
Trebuchet MS
Verdana

these fonts are common to both OS X and Windows. We could make Ubuntu better by including all of these fonts in a standard installation. That way when a website or document calls these quintessential fonts, everything will just work.

According to a survey done by codestyle.org, Arial Arial Black Arial Narrow Comic Sans MS Courier New Georgia Impact Lucida Sans Tahoma Times New Roman Trebuchet MS Verdana these fonts are common to both OS X and Windows. We could make Ubuntu better by including all of these fonts in a standard installation. That way when a website or document calls these quintessential fonts, everything will just work.

Written by alms66 the 7 Dec 11 at 21:48.

Or maybe do a "Restricted Fonts" package instead...?

This might make the fonts more visible to folks.

Or maybe do a "Restricted Fonts" package instead...? This might make the fonts more visible to folks.