Written by UbuntuNinja the 14 Mar 09 at 02:18.

Create a native Mac OS X application (for Intel Macs) that would install Ubuntu on the same partition that OS X runs from much like the current Wubi installer does to Windows. The Ubuntu system might be able to be installed just in a sub-directory of the OS X partition (without the creation of a virtual disk) because, lets not be forgetting, Mac OS X is Unix-like and includes a Bash shell.

Create a native Mac OS X application (for Intel Macs) that would install Ubuntu on the same partition that OS X runs from much like the current Wubi installer does to Windows. The Ubuntu system might be able to be installed just in a sub-directory of the OS X partition (without the creation of a virtual disk) because, lets not be forgetting, Mac OS X is Unix-like and includes a Bash shell.

Written by rbsfou the 16 Apr 09 at 19:36.

I agree about the idea of OSX support software on the disc. A wizard should be provided (visible to macs, a hybrid ISO basically), that can assist a user to install ubuntu.

Also, Wubi / Windows support package should detect apple machines, and inform the user that they should really proceed from inside OSX (unless one can install reFit from windows) - but let them do it anyway.

We should add detection for (genuine!) Intel Apple machines, and perform the following steps:

1. Use diskutil to resize down the OSX root partition
2. install reFit (to EFI syst partition)
3. Boot the ubuntu installer & get it to install grub to the boot sector of the partition, not the (pseudo) MBR.

For a wubi style-alternative, i would imagine that it be paramount to inform the user they would have
to disable journalling in order to allow writing to the image file.

Also, hfsutils should be installed if hfs partitions are present (see my idea on OSX migration assistant)

I agree about the idea of OSX support software on the disc. A wizard should be provided (visible to macs, a hybrid ISO basically), that can assist a user to install ubuntu. Also, Wubi / Windows support package should detect apple machines, and inform the user that they should really proceed from inside OSX (unless one can install reFit from windows) - but let them do it anyway. We should add detection for (genuine!) Intel Apple machines, and perform the following steps: 1. Use diskutil to resize down the OSX root partition 2. install reFit (to EFI syst partition) 3. Boot the ubuntu installer & get it to install grub to the boot sector of the partition, not the (pseudo) MBR. For a wubi style-alternative, i would imagine that it be paramount to inform the user they would have to disable journalling in order to allow writing to the image file. Also, hfsutils should be installed if hfs partitions are present (see my idea on OSX migration assistant)

Written by yanom the 30 Sep 11 at 01:27.

I thought it should support manually overriding the requirement that it be marked executable. So I rewrote /usr/bin/cautious-launcher. This should do it (I think. I have never used shell script before). Code is at this url:

http://pastebin.com/4ZcvyenL

I thought it should support manually overriding the requirement that it be marked executable. So I rewrote /usr/bin/cautious-launcher. This should do it (I think. I have never used shell script before). Code is at this url: http://pastebin.com/4ZcvyenL

Written by glomboi the 22 Oct 11 at 07:09.

If you can't edit the file to make it executable, add a "Try to Run" option. If the user has the correct permissions, an "Allow Execution" button could appear.
The current system confuses new users and is an unnecessary hassle to more experienced users.

If you can't edit the file to make it executable, add a "Try to Run" option. If the user has the correct permissions, an "Allow Execution" button could appear. The current system confuses new users and is an unnecessary hassle to more experienced users.

Written by Laslow the 17 Jan 12 at 05:16.

Either as part of the installer when detecting the system type, or as a configurable option, or both, allow the "NumLock is Enabled" warning to be changed to "NumLock is Disabled" to remind desktop users when this is the case.

Either as part of the installer when detecting the system type, or as a configurable option, or both, allow the "NumLock is Enabled" warning to be changed to "NumLock is Disabled" to remind desktop users when this is the case.

Written by jonasPlatte the 17 Jan 12 at 16:02.

I think it's better to have a selection between warning for only capsLock, only numLock, both or none. And perhaps it would be good to have the choice to "invert" the warning for numLock, like Solution #1.

I think it's better to have a selection between warning for only capsLock, only numLock, both or none. And perhaps it would be good to have the choice to "invert" the warning for numLock, like Solution #1.

Written by PaddyLandau the 17 Jan 12 at 19:15.

It used to be that the computer would remember your preference. Turn on Num Lock? It would still be on when you were ready to log in next time. Turn off Num Lock? It would still be off when you were ready to log in the next time.

That makes so much more sense.

It used to be that the computer would remember your preference. Turn on Num Lock? It would still be on when you were ready to log in next time. Turn off Num Lock? It would still be off when you were ready to log in the next time. That makes so much more sense.

Written by anichols2000 the 21 Oct 11 at 15:09.

A new throttling mode, 'temp', that allows me to switch between the two modes automatically based on the current highest core temperature being reported through lmsensors. If the temp reaches a cutout (preferably a few degrees less than the thermal cutout for your particular laptop....user-adjustable but defaults to 85 C) it drops you into powersave, otherwise it pushes you into ondemand. This way you get the functionality of ondemand's cpu governor as long as doing so won't threaten to turn off your laptop.

A new throttling mode, 'temp', that allows me to switch between the two modes automatically based on the current highest core temperature being reported through lmsensors. If the temp reaches a cutout (preferably a few degrees less than the thermal cutout for your particular laptop....user-adjustable but defaults to 85 C) it drops you into powersave, otherwise it pushes you into ondemand. This way you get the functionality of ondemand's cpu governor as long as doing so won't threaten to turn off your laptop.

Written by zooounds the 2 Mar 09 at 15:56.

Now you only have:

* Latest comment
* Popularuty

I miss options like:

* Time created / idea number
* By name

etc

Now you only have: * Latest comment * Popularuty I miss options like: * Time created / idea number * By name etc

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 christophski the 3 Jun 09 at 10:51.

We could use the new Ubuntu notifications to do provide this alert. Just something simple like "USB Webcam detected" with an icon of a webcam.

We could use the new Ubuntu notifications to do provide this alert. Just something simple like "USB Webcam detected" with an icon of a webcam.

Written by cheesehead the 3 Jun 09 at 15:50.

Since I already have hotplug scripts that execute when a new device is detected, I don't need these notifications. In this case, detection notifications would be a nuisance.

Since I already have hotplug scripts that execute when a new device is detected, I don't need these notifications. In this case, detection notifications would be a nuisance.

Written by DnaX the 6 Jun 09 at 00:11.

An implementation of solution #1: There is this python script that notify new devices discovered by HAL. Work fine.

https://code.launchpad.net/~dnax88/+junk/hal-notify

Some examples:

An implementation of solution #1: There is this python script that notify new devices discovered by HAL. Work fine. https://code.launchpad.net/~dnax88/+junk/hal-notify Some examples: <img src="http://dnax.netsons.org/storage/hal-notify.png" /> <img src="http://dnax.netsons.org/storage/hal-notify2.png" />

Written by jamespgray the 7 Jun 09 at 18:47.

I expect when I plug in a new device it will be detected and configured and ready for my use within 10 seconds or so. A notification can be displayed if the device is NOT usable for some reason or isn't ready within the 10 seconds. (2 different notification messages).

The old equation: silence = success

I expect when I plug in a new device it will be detected and configured and ready for my use within 10 seconds or so. A notification can be displayed if the device is NOT usable for some reason or isn't ready within the 10 seconds. (2 different notification messages). The old equation: silence = success

Written by walterav the 7 Jun 09 at 22:37.

It might give a "false assumption" that the hardware is also supported and directly working with ubuntu.

My suggestion would be that it gives a notification that is green/if the hardware directly works, it might fade away!

Other wise make the notification "red" with a extra dialog box that say's this hardware is not supported, or needs the following procedure, or something with cancel.

This idea can be combined with solution 1 / 3

It might give a "false assumption" that the hardware is also supported and directly working with ubuntu. My suggestion would be that it gives a notification that is green/if the hardware directly works, it might fade away! Other wise make the notification "red" with a extra dialog box that say's this hardware is not supported, or needs the following procedure, or something with cancel. This idea can be combined with solution 1 / 3

Written by Mentalikryst the 14 Jun 09 at 22:05.

Give a menu that gives some information such as:

*Status
*Compatibility
*Type of Device
*Programs which use the device (So give Nautilus/Dolphin for a USB Flash Drive, Network Manager for a WiFi adapter, etc.)

The menu would fade away and would not be obtrusive, but would give the user information about the device and give options on what to do.

Give a menu that gives some information such as: *Status *Compatibility *Type of Device *Programs which use the device (So give Nautilus/Dolphin for a USB Flash Drive, Network Manager for a WiFi adapter, etc.) The menu would fade away and would not be obtrusive, but would give the user information about the device and give options on what to do.

Written by DaVince the 15 Jun 09 at 22:25.

It would probably be a good idea to have an icon pop up while a notification is shown, so that accessibility to configuration of this little tool is available. Anyone who doesn't like the notifications or wants to disable them for certain hardware will be able to do so by clicking this icon (a special configuration window will pop up).

The icon will automatically disappear shortly after the notification was shown.

It would probably be a good idea to have an icon pop up while a notification is shown, so that accessibility to configuration of this little tool is available. Anyone who doesn't like the notifications or wants to disable them for certain hardware will be able to do so by clicking this icon (a special configuration window will pop up). The icon will automatically disappear shortly after the notification was shown.

Written by lokster the 6 May 11 at 22:08.

I have developed an application for this purpose. It shows notifications for many devices (not just Flash Drives and WebCams), and works on Ubuntu 10.10, 11.04 (and derivatives). Maybe on 10.04 too, but I haven't tested it yet. Its name is udev-notify and you can find more info and packages here: http://udev-notify.learnfree.eu/

I have developed an application for this purpose. It shows notifications for many devices (not just Flash Drives and WebCams), and works on Ubuntu 10.10, 11.04 (and derivatives). Maybe on 10.04 too, but I haven't tested it yet. Its name is udev-notify and you can find more info and packages here: http://udev-notify.learnfree.eu/

Written by zwyber the 8 Mar 09 at 19:55.

Very plain and simple, show a (extra) notification, telling the user that they are running in a live session and that Ubuntu runs very slow now.

Why extra? If Ubuntu developers are going to create a welcome screen where they put this information some people are not going to read this. Just a small dialogue after the welcome screen has been closed would be nice.

OR

Put the message in the default wallpaper, easier but not really the best solution.

Very plain and simple, show a (extra) notification, telling the user that they are running in a live session and that Ubuntu runs very slow now. Why extra? If Ubuntu developers are going to create a welcome screen where they put this information some people are not going to read this. Just a small dialogue after the welcome screen has been closed would be nice. OR Put the message in the default wallpaper, easier but not really the best solution.

Written by kidmodify the 9 Mar 09 at 02:07.

Use a Live CD "Cloud" if the computer is connected to the Internet to help increase speed. That way you have two sources of incoming data, the CD, and the Web.

Use a Live CD "Cloud" if the computer is connected to the Internet to help increase speed. That way you have two sources of incoming data, the CD, and the Web.

Written by kidmodify the 9 Mar 09 at 02:14.

Some computers have more than one CD drive. Make it possible to use for example two disk drives each with an ubuntu CD. This could (as far as I know) double the speed, depending on the drive speeds.

Some computers have more than one CD drive. Make it possible to use for example two disk drives each with an ubuntu CD. This could (as far as I know) double the speed, depending on the drive speeds.

Written by Cé the 13 Mar 09 at 12:24.

Cache the executable files on the CD very agressively.
Cache the data files a lot less.
If there's a lot of RAM, precache executable files, if possible all of them.
This will make the use of the CD (or a slow HD) a lot faster.

Cache the executable files on the CD very agressively. Cache the data files a lot less. If there's a lot of RAM, precache executable files, if possible all of them. This will make the use of the CD (or a slow HD) a lot faster.

Written by scubanator87 the 13 Mar 09 at 13:45.

Some live CDs (like puppy for instance) have the option to load the OS into memory.

Provided there is enough RAM (2GB?) Allow users the option to load the OS into memory and to continue to boot from there.

Some live CDs (like puppy for instance) have the option to load the OS into memory. Provided there is enough RAM (2GB?) Allow users the option to load the OS into memory and to continue to boot from there.

Written by sci-fi guy the 16 Mar 09 at 23:08.

Maybe integrate a checkbox to turn it on with Solution #1 above.

Maybe integrate a checkbox to turn it on with Solution #1 above.

Written by Basem the 22 Mar 09 at 08:54.

While booting the OS, add a line that says "Enjoy ubuntu in full speed by installing it"

While booting the OS, add a line that says "Enjoy ubuntu in full speed by installing it"

Written by euxneks the 26 Mar 09 at 19:01.

I like the idea of letting them know that they are using a LiveCD on the desktop - we should also have interaction with it so that a user can get an idea of what a LiveCD is and why it's slower than the real system.

Once they close this, allow them the ability to open it again.

I like the idea of letting them know that they are using a LiveCD on the desktop - we should also have interaction with it so that a user can get an idea of what a LiveCD is and why it's slower than the real system. Once they close this, allow them the ability to open it again.

Written by ahsaeed the 29 Mar 09 at 16:11.

When I use Ubuntu in live session i don't wont to play games for example .. and some users do..
So..
i recommend to add another option to the boot menu as an advanced option..
"select programs to load during live sessions " .

When I use Ubuntu in live session i don't wont to play games for example .. and some users do.. So.. i recommend to add another option to the boot menu as an advanced option.. "select programs to load during live sessions <to speedup the session>" .

Written by sanketmedhi the 2 Apr 09 at 11:23.

Everyone might not have 2 GB of RAM but everyone has a USB drive. Live sessions booted from CDs can be cached onto USB storage for improved performance.

Everyone might not have 2 GB of RAM but everyone has a USB drive. Live sessions booted from CDs can be cached onto USB storage for improved performance.

Written by sanketmedhi the 2 Apr 09 at 11:51.

Bootable USB images should be promoted rather than live CDs. Bootable USB drives can be prepared using software such as the one showed on https://help.ubuntu.com/community/Installation/FromUSBStick . Alternatively, the software that runs on Windows when an Ubuntu live CD is inserted should include such a functionality.

Bootable USB images should be promoted rather than live CDs. Bootable USB drives can be prepared using software such as the one showed on https://help.ubuntu.com/community/Installation/FromUSBStick . Alternatively, the software that runs on Windows when an Ubuntu live CD is inserted should include such a functionality.

Written by Dorje the 2 Apr 09 at 22:10.

like solution #9 add an option to deselect unnecessary programmes and also give the percentage increase each unselection generates .
like for eg.
deselecting games =increase in speed 10%
and so on

PS:i don't know much about programmes so i dont know how much speed gain every (possible)deselection will generate

like solution #9 add an option to deselect unnecessary programmes and also give the percentage increase each unselection generates . like for eg. deselecting games =increase in speed 10% and so on PS:i don't know much about programmes so i dont know how much speed gain every (possible)deselection will generate

Written by deriamis the 4 Apr 09 at 18:40.

Since the majority of load times is in late-linking the libraries, why not have the often-used libraries in a ramdisk and use UnionFS to overlay those files on a path? In combination with pre-caching (#4), this could be a significant speed boost. If we combine it with using a LiveUSB distro (#11), we could be on par with the performance of the computer itself.

Since the majority of load times is in late-linking the libraries, why not have the often-used libraries in a ramdisk and use UnionFS to overlay those files on a path? In combination with pre-caching (#4), this could be a significant speed boost. If we combine it with using a LiveUSB distro (#11), we could be on par with the performance of the computer itself.

Written by pepperpupper the 5 Apr 09 at 12:47.

Add an option for creating a live-usb to the autorun menu that pops up when mounting or inserting the cd/iso. Many people will use daemon-tool or similar to mount the cd in Windows, and if they see an option to create a live-usb from the popup menu, that would be a way of making it easier for everyone to do so.

Add an option for creating a live-usb to the autorun menu that pops up when mounting or inserting the cd/iso. Many people will use daemon-tool or similar to mount the cd in Windows, and if they see an option to create a live-usb from the popup menu, that would be a way of making it easier for everyone to do so.

Written by pepperpupper the 5 Apr 09 at 12:54.

The title is self-descriptive. This would be another way of making it easier for people to find out about the possibility of creating a live-usb.

The title is self-descriptive. This would be another way of making it easier for people to find out about the possibility of creating a live-usb.

Written by ll the 6 Apr 09 at 03:52.

A modified background that includes a warning can be used instead of a notification. Many computers at universities that are meant for multiple users use the background to communicate a special procedure especially in libraries for catalogue searches. This will decrease confusion and not use as many resources as a notification (I assume).

A modified background that includes a warning can be used instead of a notification. Many computers at universities that are meant for multiple users use the background to communicate a special procedure especially in libraries for catalogue searches. This will decrease confusion and not use as many resources as a notification (I assume).

Written by pepperpupper the 7 Apr 09 at 14:14.

Make it possible to install a native Ubuntu installation from within Windows to another partition than the one running Windows from or to an USB-memory key, making it easier to install Ubuntu without having to boot into live mode.

Make it possible to install a native Ubuntu installation from within Windows to another partition than the one running Windows from or to an USB-memory key, making it easier to install Ubuntu without having to boot into live mode.

Written by lackscr8ivity the 7 Apr 09 at 14:25.

When running the live session I would guess the memory, processor, hard disk read/write speed (maybe not this one), etc. system hardware & performance are evaluated.
As well, when running a program (game, OpenOffice, etc.) the CD read/write & load time could stored. Thus, when the user ends the live session, in the log-out window list some statistics: "These are the 5 programs you used the most:
From the live CD it took X-amount of real-time to load, but based on your system's hardware, if this were installed, we would expect it would X% faster."

When running the live session I would guess the memory, processor, hard disk read/write speed (maybe not this one), etc. system hardware & performance are evaluated. As well, when running a program (game, OpenOffice, etc.) the CD read/write & load time could stored. Thus, when the user ends the live session, in the log-out window list some statistics: "These are the 5 programs you used the most: From the live CD it took X-amount of real-time to load, but based on your system's hardware, if this were installed, we would expect it would X% faster."

Written by moose the 14 Apr 09 at 08:08.

So the live-cd shouldn't start services which are not neccessary for testing ubuntu (as some people use the live-cd as a secure system, services like cups are neccessary):

# anachron, atd, cron: I never used a live-cd longer than six hours - why should I create a cronjob?
# acpid, acpi-support, apmd, powernowd, powernowd.early: If I use the live-cd, I want to test if my hardware works and if the software fits my expections, not if the sleep option works.

So the live-cd shouldn't start services which are not neccessary for testing ubuntu (as some people use the live-cd as a secure system, services like cups are neccessary): # anachron, atd, cron: I never used a live-cd longer than six hours - why should I create a cronjob? # acpid, acpi-support, apmd, powernowd, powernowd.early: If I use the live-cd, I want to test if my hardware works and if the software fits my expections, not if the sleep option works.

Written by Ssdg the 29 Apr 09 at 11:25.

My idea would be to tell it on the first screen (the one that offers you to test, install, etc...).

Like:
Try ubuntu without
Install on your hard drive for better performances
...

not by demoting the live CD mode, but by promoting the installation.

I'm not in advertisement, but ubuntu will look much better.

My idea would be to tell it on the first screen (the one that offers you to test, install, etc...). Like: Try ubuntu without Install on your hard drive for better performances ... not by demoting the live CD mode, but by promoting the installation. I'm not in advertisement, but ubuntu will look much better.

Written by chareos the 6 May 09 at 14:08.

Make the Ubuntu download to be an EXE file which lets user choose to create a LiveCD (with performance warning here) OR a LiveUSB.

Also, a performance warning on LiveCD boot itself would be great !

Make the Ubuntu download to be an EXE file which lets user choose to create a LiveCD (with performance warning here) OR a LiveUSB. Also, a performance warning on LiveCD boot itself would be great !

Written by Avantarius the 10 May 09 at 09:42.

For systems with 1 GiB RAM or less, where solution #5 can't be applied, load the content of the CD in a virtual file system which could be located in a file on the computer's harddisk, i.e. create file on a existing ntfs-partition, an unpartitioned space or even use the m$-windows-swapspace.

For systems with 1 GiB RAM or less, where solution #5 can't be applied, load the content of the CD in a virtual file system which could be located in a file on the computer's harddisk, i.e. create file on a existing ntfs-partition, an unpartitioned space or even use the m$-windows-swapspace.

Written by Kver the 16 May 09 at 20:51.

When a live cd shows the loading bar, there's plenty of time for a message such as "Loading and running content from this DVD will result in slow performance, and changes or customizations will not be saved."

When a live cd shows the loading bar, there's plenty of time for a message such as "Loading and running content from this DVD will result in slow performance, and changes or customizations will not be saved."

Written by aroach31291 the 22 Oct 09 at 17:19.

Firstly, I think that many of the solutions above are solving the wrong problem. People that try out Ubuntu may think that it is installed by just inserting the CD. The user may have no idea that they are using a LiveCD. After they discover that Ubuntu is "slow", they give up and reboot back into Windows. Notifying the user that they haven't installed Ubuntu yet would be the best way to solve this problem.

Utilize the new notification system. Have it simply display a message when the desktop has finished loading similar to:

Ubuntu is not installed yet! Feel free to use Ubuntu before installing it, but beware that it may be a little slow. If you like what you see click the install icon on your desktop!

Firstly, I think that many of the solutions above are solving the wrong problem. People that try out Ubuntu may think that it is installed by just inserting the CD. The user may have no idea that they are using a LiveCD. After they discover that Ubuntu is "slow", they give up and reboot back into Windows. Notifying the user that they haven't installed Ubuntu yet would be the best way to solve this problem. Utilize the new notification system. Have it simply display a message when the desktop has finished loading similar to: Ubuntu is not installed yet! Feel free to use Ubuntu before installing it, but beware that it may be a little slow. If you like what you see click the install icon on your desktop!

Written by mikko.rantalainen the 7 Oct 10 at 06:45.

Live session from USB/flash memory should be pretty okay even today but the real problem is accessing files from optical drive. Even there, the problem is latency, usually not the bandwidth.

The live session should run a small background service that displays a notification message when system is waiting for CD drive to access required data. The message could be along the line "Reading data from CD (installing on the hard drive would improve performance)" [however, the label should not claim to be reading CD if one is booting from e.g. usb memory stick]. The notification should be displayed if read command has waited in disk scheduler queue for more than a second.

This could be extended to deal with installed system, too. It would make sense to point out bottlenecks in the system to the user. If the system feels slow and a notification pops up that says "Waiting for disks (installing a fast SSD drive would improve performance)" would give a reasonable hint to the user which hardware upgrade would help the most. This could be even further extended and a similar notification should pop up if all CPU cores have been taken for more than 5 seconds ("Waiting for processor (upgrading the processor would improve performance)").

Live session from USB/flash memory should be pretty okay even today but the real problem is accessing files from optical drive. Even there, the problem is latency, usually not the bandwidth. The live session should run a small background service that displays a notification message when system is waiting for CD drive to access required data. The message could be along the line "Reading data from CD (installing on the hard drive would improve performance)" [however, the label should not claim to be reading CD if one is booting from e.g. usb memory stick]. The notification should be displayed if read command has waited in disk scheduler queue for more than a second. This could be extended to deal with installed system, too. It would make sense to point out bottlenecks in the system to the user. If the system feels slow and a notification pops up that says "Waiting for disks (installing a fast SSD drive would improve performance)" would give a reasonable hint to the user which hardware upgrade would help the most. This could be even further extended and a similar notification should pop up if all CPU cores have been taken for more than 5 seconds ("Waiting for processor (upgrading the processor would improve performance)").

Written by rouge568 the 29 Feb 08 at 00:39.

Have a drop-down menu display when I right-click on an item, with choices such as "edit this item" "delete this item", and "add a new menu item". Also, if I click and hold on an item, it should hover and I should be able to drag it through the menus to reposition it.

Have a drop-down menu display when I right-click on an item, with choices such as "edit this item" "delete this item", and "add a new menu item". Also, if I click and hold on an item, it should hover and I should be able to drag it through the menus to reposition it.

Written by robertjlee the 29 Mar 09 at 16:50.

When you right-click on a submenu's menu item, it should not close the submenu. Instead, it should bring up a context menu with additional options to edit this submenu in the menu editor, and to hide this submenu (as well as the existing options you would get from right-clicking on a menu item within that sub-menu).

For a menu item, add extra context menu options to edit this menu item in the menu editor, to directly edit the menu item's launcher's properties, and to hide the menu item.

It should also be possible to drag menu items (including entire sub-menus), within each menu. Additionally, each sub-menu item should have a "lock to menu" checkbox option on its context menu to prevent it from being dragged (similar to panel items' "lock to panel" checkbox option).

It may even be possible to use panels and drawers to build the menus and use common code to handle the behaviour of both consistently.

The edit menus item would still be needed to remove items, and would still be useful for "bulk" changes where the user may not want to open the applications menu each time.

When you right-click on a submenu's menu item, it should not close the submenu. Instead, it should bring up a context menu with additional options to edit this submenu in the menu editor, and to hide this submenu (as well as the existing options you would get from right-clicking on a menu item within that sub-menu). For a menu item, add extra context menu options to edit this menu item in the menu editor, to directly edit the menu item's launcher's properties, and to hide the menu item. It should also be possible to drag menu items (including entire sub-menus), within each menu. Additionally, each sub-menu item should have a "lock to menu" checkbox option on its context menu to prevent it from being dragged (similar to panel items' "lock to panel" checkbox option). It may even be possible to use panels and drawers to build the menus and use common code to handle the behaviour of both consistently. The edit menus item would still be needed to remove items, and would still be useful for "bulk" changes where the user may not want to open the applications menu each time.

Written by leael the 18 Apr 09 at 13:48.

To be consistent with the panels, the user has to unlock the menu in order for the drag'n'drop to become possible. Possible implementations could be a global "Unlock Menu Elements" or better "Allow Dragging of Menu Elements".

To be consistent with the panels, the user has to unlock the menu in order for the drag'n'drop to become possible. Possible implementations could be a global "Unlock Menu Elements" or better "Allow Dragging of Menu Elements".

Written by leael the 18 Apr 09 at 13:58.

To be consistent with the panels, each item gets an "Move" entry in its context menu, thus locking the item in the mouse and let the user drag it to other locations as also into submenus, until the mouse button is clicked again.

To be consistent with the panels, each item gets an "Move" entry in its context menu, thus locking the item in the mouse and let the user drag it to other locations as also into submenus, until the mouse button is clicked again.

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