Community
Participate
Working Groups
I20060807-2000 Project Explorer view menu > Filters...: - dialog title must be title case - dialog title should match action name: - either call dialog "Project Explorer Filters" or - call action "Preferences..." and dialog accordingly (like Synchronize view) - tabs: "Available" is unnecessary, "Filters" and "Content" is enough - message is below tree on both pages, should be above (e.g. "Select the filters to apply [..]:") - initial focus should be in filter field, not tab
*** Bug 158275 has been marked as a duplicate of this bug. ***
From bug 158275: The second tab seems unrelated to filters. I would move it to a separate action (not 'Filters...', but maybe 'Configure...'). This would avoid the tabs and avoid the border in border layout which doesn't look good.
Also from bug 158275: The dialog has resize problems. Making the dialog larger flickers in WinXP.
I would also suggest to group the filter items by their contributing content extension or by some new filter category to avoid clutter when more and more extensions contribute their filters. Filters from disabled content extensions should not be shown in the list at all.
This should be fixed for 3.3.
Updated the strings according to advice and moved the creation of the instruction label to the top of the tab. The action is still under one menu ("Customize View...") which had the "Filters" and "Content" tab. The ultimate goal is to make it possible for extensions to contribute their own tabs in the future. Each tab is fairly contained; and in the future, an extnsion might contribute 0..* of these tabs for their own custom preferences/settings. Not all filters are associated with an extension, so the filters are not "filtered" based on their associated extensions at this time. Similarly, grouping filters with their "contributing" extensions has proven hazardous in the past (an earlier version of the framework did this). Some filters also apply to other content, even if their contributing extension is disabled. Please open a separate enhancement request if you feel this is an important requirement. Fixed and released for > I20070426_0300.
