Community
Participate
Working Groups
20060301 The UI of the 'import preferences' wizard could be imporved the following ways: - remove empty space between 'From preference file' input box and 'Import all' radio button - fix all button sizes to follow the button size rules (they are too small) - when 'import all' is selected, the table should be disabled and all elements checked so it is clear what 'all' means - I can click on select all / deselect all when 'import all' is selected. what does that mean? - the group box seems unnecessary. Why repeating 'Preferences' here?
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
See also bug 290918.
>- fix all button sizes to follow the button size rules (they are too small) Done. >- when 'import all' is selected, the table should be disabled and all elements >checked so it is clear what 'all' means Disabling reduces the ability to quickly switch to selective import/export. We also have to keep in mind that when exporting 'all' is not equivalent to having all available transfers selected (it's only true when importing). >- I can click on select all / deselect all when 'import all' is selected. what >does that mean? At least we should activate selective import/export when clicking those buttons. I've done that.
>(it's only true when importing). Not even then: import 'all' might import more preferences than just selecting all the available transfers.
Do we need that "Import all" at all? The current UI unnecessarily blocks the user from importing e.g. "all, except for Installed JREs". The global checkbox should be removed and replaced by an additional option, e.g. a) entry "Uncategorized Preferences" in the table (always on top of the list, so it stays visible even if there are many categories) or b) checkbox "Other Preferences" below the table When the new checkbox is checked, all preferences should be imported, except for those in the categories that are unchecked in the table.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
