Bugzilla – Full Text Bug Listing
| Summary: | [ui] Available IU view enhancements | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Susan McCourt <susan> |
| Component: | p2 | Assignee: | Susan McCourt <susan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | b.muskalla, ekuleshov, irbull, john.arthorne, leberre, leo.dos.santos, max.gilead, mik.kersten, nboldt, Olivier_Thomann, steffen.pingel |
| Version: | 3.4 | ||
| Target Milestone: | 3.4 M7 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Susan McCourt
Might be nice also to have a spatial distinction between the buttons that act on the selected items (properties, install) and ones that are more generic (manage sites). Consider putting the latter near the bottom of the vertical button bar. >- let user toggle the views locally, not in prefs
Clarification: this means toggling local values that affect the views such as:
- show flat, by category, by repo
- show latest version only
- don't show what I already have
The local value default is driven by the pref, but the user can change it in-line, and that local change is remembered in the dialog settings.
*** Bug 222509 has been marked as a duplicate of this bug. *** *** Bug 222812 has been marked as a duplicate of this bug. *** >- possibly an affordance for something newer that they have installed (update
>is available)
implied by this is an affordance for what is already installed (current).
*** Bug 224006 has been marked as a duplicate of this bug. *** Daniel, I'm cc'ing you on this bug so you can follow/contribute user point of view as we work on this Linux users are used to update regularly their computers. In Mandriva for instance, there are color codes for each package: - green means package that can be installed - blue means an update of an already installed package - red means a package conflicting with installed packages Maybe a similar idea could be used in Eclipse Manager. Thanks for the example. I don't know that we will rely too heavily on colors due to accessibility issues, but some additional affordance will be investigated, and color may be part of this. I plan to update this bug with questions/proposals as I work on this issue to get feedback on the various alternatives. *** Bug 225004 has been marked as a duplicate of this bug. *** *** Bug 225123 has been marked as a duplicate of this bug. *** Few more improvements that would be useful: - allow ability to name update sites - allow to see list of plugins/versions for each feature Eugene, I really like to see the naming of sites too. But I think this is already covered by bug 194224. suggestions from zx: - install before properties - common actions on a context menu (I've actually tried to bring up a menu when I forget that it's not implemented!) (idea from bug #225326) when a site is added, is there any reasonable way we could know what to expand? Users who add a site want to see what's there, not click again to open a category. In site view, we could expand that site. Easy. In category/flat view? (In reply to comment #15) > In category/flat view? My suggestion from the user's point of view: - select everything that the newly-added site contributed to the view - mark newly-added items in some obvious way (bold font, separate icon/marker) -- in case user wants to select only a few items A first cut at the ability to filter and switch views has been released for this week's I-Build. The changes that had the most impact on our provisional API's are where I focused my efforts. The remaining ideas can be handled a lot more incrementally. The changes you'll see are: - a view menu that allows the user to switch between category, flat, or repo view - the add/remove site buttons appear on the main page if a repo view is used (reduce click count). If viewing by category or flat, you still need to go to the manage sites button to manipulate the sites - filter is available for filtering what is shown from any view (see bug #204826 for more discussion of problems/caveats). There's been no work on filtering out already installed items, groovy affordances for available updates, etc. Many other ideas in here are being considered. I'll probably take a pass at the easy ones and open separate bugs for those that can't be done due to time constraints, complexities, etc. This bug will stay open until I've done that. I added context menus for the common actions in both pages while adding the refresh support. Remaining items left to consider are listed here. Comments are welcome/appreciated on some of the options to consider: 1. How to show what's installed, what updates are available - local options to filter out what's installed and show latest version only AND/OR - column-based affordances for what's already installed, update available, etc. AND/OR - consider not showing version if only latest version is showing (this would require a details area that should show version, description) 2. How to highlight what user has just added to let them get to the task at hand faster - navigate to newly added content (makes most sense when in repo view) OR - select newly added content (might be spread out over other views, potentially confusing) OR - reset the filter so that only newly added content is shown. This would highlight it in the (view by site, by category) view and show only the new content in (by name) view. The filter text could say something like "newly added content" or something... I opened bug #226577 for Eugene's suggestion in comment #12 >- allow to see list of plugins/versions for each feature as this is really outside of the scope of the first release. See that bug for details. Susan, I just installed 3.4M6a and I noticed one annoying UI issue: - The installed features tab shows installed features and their versions: that's fine. - The Available features tab shows again those features: that's bad. From a user point of view, it looks like the feature has not been installed properly since it is still available. So I would suggest you hide installed features from the available tab. Another idea: allow the user to easily cut-and-paste features details for bug reporting. Under Linux, I cannot select the build id for instance to fill in bug reports :) >So I would suggest you hide installed features from the available tab. Ok, I'll interpret that as a vote for >- local options to filter out what's installed and show latest version only rather than using affordances to indicate what's installed and what's not. This is where I'm leaning....less clutter. (Unless of course it's a newer version of what's installed). Do you mind opening a bug for the second suggestion? (cut/paste from feature details). I'm trying now to focus this bug on the remaining items in comment #18, and that code happens to live in the old update. Thanks for the suggestions... Susan, I created Bug #227114 for the second sugestion. thanks, Daniel. >2. How to highlight what user has just added to let them get to the task at
>hand faster
When a repository gets added, the UI will now pre-load the site in the background and then expand/highlight the site when in "view by site" mode. I didn't do anything for the flat/category views because:
- IU's for a repo are spread out in the flat and category views, and not all selections would be visible
- filtering by site would require too much new work right now and open up some more timing problems between background fetch and filtering.
Remaining issue is filtering out installed items and a dialog local option to show latest/show all versions rather than relying only on the preference.
>Remaining issue is filtering out installed items and a dialog local option to >show latest/show all versions rather than relying only on the preference. Fixed in HEAD >20080418. I've also fixed up some of the refreshing so that filtering is maintained when you switch between views. There are certainly still some improvements that could be made in this view, but I'm closing this bug as it's addressed the major functional improvements, and these are all the major changes planned for this view for 3.4. Bug #216032 is collecting the ideas for better affordances for IU's. For example, if you are filtering out installed content and also showing latest versions, then if an IU you have installed is in the available list, it is an update to what you have. Would be nice to show that. The fact that we don't is simply a matter of time. Thanks everyone for your ideas and input. Please open new bugs for things you still want to see. |