Written by DanielHendrycks the 14 Jun 11 at 18:22.

Implement or take ideas from the mock-ups for the Update Manager: http://goo.gl/Xhngx
This hides much of the information and divides the options into something users are familiar with: tabs.
[Updated]

Implement or take ideas from the mock-ups for the Update Manager: http://goo.gl/Xhngx This hides much of the information and divides the options into something users are familiar with: tabs. [Updated]

Written by enoop the 18 Jun 11 at 00:07.

Clean up the update manager so that it would show only an easy to recognize name. Group the updates that new users would not recognize (python etc.) into one group that power users could open and turn off specific updates.

Clean up the update manager so that it would show only an easy to recognize name. Group the updates that new users would not recognize (python etc.) into one group that power users could open and turn off specific updates.

Written by mihalybaci the 14 Jul 11 at 04:05.

Leave the update manager mostly the way it is, but add a 'help' hyperlink for each option opening a new window with a paragraph or more of detail as appropriate. This could even be done with a separate 'Help' tab that when clicked would provide a list of the possible options and/or a search option. The tab would eliminate the need for dozens of help links.

Examples: Under Update Manager Settings > Software Sources, what's the difference between "canonical-supported" and "community-maintained" software and why should people check/uncheck those boxes? Or under "Updates", why wait for "recommended" updates when you can get the "pre-released" updates?

Leave the update manager mostly the way it is, but add a 'help' hyperlink for each option opening a new window with a paragraph or more of detail as appropriate. This could even be done with a separate 'Help' tab that when clicked would provide a list of the possible options and/or a search option. The tab would eliminate the need for dozens of help links. Examples: Under Update Manager Settings > Software Sources, what's the difference between "canonical-supported" and "community-maintained" software and why should people check/uncheck those boxes? Or under "Updates", why wait for "recommended" updates when you can get the "pre-released" updates?

Written by fluteflute the 24 May 11 at 08:29.

I don't know the technical details of packaging, but I think there is/should be some way for packages to mark that they want grub.cfg regenerated.

Then once all the packages are installed, the package manager looks and says "oh look, this package wanted grub.cfg updated, let's do it". This way if multiple packages request for grub.cfg to be regenerated it only happens once.

I don't know the technical details of packaging, but I think there is/should be some way for packages to mark that they want grub.cfg regenerated. Then once all the packages are installed, the package manager looks and says "oh look, this package wanted grub.cfg updated, let's do it". This way if multiple packages request for grub.cfg to be regenerated it only happens once.