Idea #9645: Some Synaptic UI Suggestions

1) The list of searches (in "Search Results") is cleared after changes are applied. It should not be cleared until the program exits. You may want to include erasing the list after applying changes as an option, but the default action should be to not clear the list.

2) The search button should be replaced with a text input field with the same function. It makes the UI a bit easier to work with. The search box should remember the last searched term until changes are applied (or the program exits). The search box idea itself is from other ideas, but the point of this one is that it should remember the last searched term until changes are applied. In other words, this part is not a complete duplicate.

3) Sections should NOT be grouped into stuff like:
Something
Something (multiverse)
Something (universe)
Something (restricted)

All of the Somethings should be in a single group. Put in an option to see subgroups if the user wants to see where the package is coming from (official, multiverse, universe, or restricted).

4) Sections should be follow the packages placement in the "Applications" pull-down menu. This will make it easier on the user to see where the program goes instead of hunting for it (for instance, where would something like Limewire or Songbird go - music or internet?).

5) Create a restore point before each change or upgrade. This should help the few unlucky admins that let their boxes get away from them. Yes, we all know they should be smarter than that, and that they should learn their OS before attempting to roll it out, and its their own fault, and they are stupid morons, and they shouldn't be admins if they don't understand things. We all know that. But sometimes life isn't really that simple, and people are forced to admin boxes whether or not they are ready for it (my boss had me image and admin a few winblows boxes - yes, I know I should be using Linux in the office, and no, that decision is not up to me, and yes, if it was I would be using a completely Linux office - even though there was a CS major with plenty of time already on staff). Let me be the first person to say that no, I am not completely read up on how to admin things, but I'm not going to tell me boss to give it to somebody else and look like I'm passing the buck. And he didn't want this done when I was ready, he wanted it done fast, and I need the money for school. Anyway, the point is that by creating restore points prior to any program changes (you could even have it ask or put in an option to not make restore points), it makes it really easy for me as a reluctant admin, to roll back any changes I end up not wanting to do. I personally think that Synaptic should copy any config files for a package and the version of the package. Then if after an update, I need to restore the previous package version, Synaptic will re-download the old package, uninstall the new version, and install the old package with my customized config file.

No attachments.