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

If the updates are successful, the Update Manager should simply close.

If the updates are successful, the Update Manager should simply close.

Written by smenjas the 5 Feb 09 at 10:39.

The dialog that tells you that all updates were successful looks the same as it does when it's performing the updates.

Quickly glancing at the dialog I usually think that it's still working and leave it open. I should not have to read the text to know that it's finished.

If the dialog *must* remain open for some reason, at least provide a large, obvious icon that conveys whether the update succeeded or failed.

The dialog that tells you that all updates were successful looks the same as it does when it's performing the updates. Quickly glancing at the dialog I usually think that it's still working and leave it open. I should not have to read the text to know that it's finished. If the dialog *must* remain open for some reason, at least provide a large, obvious icon that conveys whether the update succeeded or failed.

Written by smenjas the 5 Feb 09 at 10:51.

I usually have no interest in watching the updates stream in and apply in minute detail. Nevertheless, I don't want updates installing completely in the background; I want to look them over before installing them.

I can easily minimize the app to the task bar manually, but having two windows (the update notification and the progress dialog) can be confusing to people who aren't familiar with computers. I imagine few people would be upset if the whole lot were to shrink away to the sidelines once the update starts.

I usually have no interest in watching the updates stream in and apply in minute detail. Nevertheless, I don't want updates installing completely in the background; I want to look them over before installing them. I can easily minimize the app to the task bar manually, but having two windows (the update notification and the progress dialog) can be confusing to people who aren't familiar with computers. I imagine few people would be upset if the whole lot were to shrink away to the sidelines once the update starts.

Written by Spo1ler the 1 Mar 09 at 10:40.

Make an option, that will allow you to exclude from update list some application.
For example: I don't want update evolution and all of its components. Then I simply press a button and exclude it from update list AT ALL. That means that I will not see it in updates list in future. And of cource we should give a possiblility to return it to update list

Make an option, that will allow you to exclude from update list some application. For example: I don't want update evolution and all of its components. Then I simply press a button and exclude it from update list AT ALL. That means that I will not see it in updates list in future. And of cource we should give a possiblility to return it to update list

Written by mahan_h the 17 Jul 09 at 12:46.

We can add boxes to indicate their “removal” or “ban update from now on” too. This way you will maintain your applications and packages regularly.

a sample image is prepared here:
http://www.4shared.com/file/118723239/18de0995/Enhanced-Update_Manager.html


Remove | BanUpdate | Update |

Note: check boxes automatically update themselves (if any selected, the other two will be deselected. They could be radio buttons too)

We can add boxes to indicate their “removal” or “ban update from now on” too. This way you will maintain your applications and packages regularly. a sample image is prepared here: http://www.4shared.com/file/118723239/18de0995/Enhanced-Update_Manager.html Remove | BanUpdate | Update | Note: check boxes automatically update themselves (if any selected, the other two will be deselected. They could be radio buttons too)

Written by qense the 1 Mar 08 at 14:15.

Allow people to submit ideas to projects and vote on them, like people can now do on Brainstorm.

This would be integrated in as another tab (like answers and bugs). Once an idea has been marked as in development it would become/link to a blueprint.

This would improve the brainstorm interface, as launchpad has a clean user interface that works with small screens.

It would also improve developer interaction, as developers would be automatically able to control and interact with there projects brainstorm.

brainstorm.ubuntu.com would remain as an interface to the collective of brainstorms existing on launchpad connected with the ubuntu project.

Allow people to submit ideas to projects and vote on them, like people can now do on Brainstorm. This would be integrated in as another tab (like answers and bugs). Once an idea has been marked as in development it would become/link to a blueprint. This would improve the brainstorm interface, as launchpad has a clean user interface that works with small screens. It would also improve developer interaction, as developers would be automatically able to control and interact with there projects brainstorm. brainstorm.ubuntu.com would remain as an interface to the collective of brainstorms existing on launchpad connected with the ubuntu project.

Written by Kev the 13 Jul 09 at 22:38.

I've already an launchpad account. Why do I need to create a new account here to vote for a brainstorm idea? Making brainstorm using OpenID could be a first step to integrate brainstorm with launchpad. This would help people retain ownership of ideas as they move across.

I've already an launchpad account. Why do I need to create a new account here to vote for a brainstorm idea? Making brainstorm using OpenID could be a first step to integrate brainstorm with launchpad. This would help people retain ownership of ideas as they move across.

Written by Warbo the 1 Jul 08 at 18:23.

Wishlist bugs on Launchpad should spawn an appropriate idea on Brainstorm. Use a duplicate matching algorithm to prevent too many duplicates. The ideas would, of course, have the Launchpad bug attached.

Wishlist bugs on Launchpad should spawn an appropriate idea on Brainstorm. Use a duplicate matching algorithm to prevent too many duplicates. The ideas would, of course, have the Launchpad bug attached.