Community
Participate
Working Groups
Simplify update manager UI. User feedback indicates that the update manager UI is too powerful and occasionally confusing to users. It should be simplified in order to provide a clear path for the common tasks, embrace progressively disclosure, separate update search from platform configuration tasks, and make more economical use of screen real estate for properties. [Platform Update] [Theme: User experience]
Since M1, a newly redesigned UI is available in 3.0 builds. Check the description of the changes in: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update- home/doc/working/ui-redesign/ui-redesign.html
I don't know if this is the correct area to raise this but one issue I would like to bring forward is about update.ui.forms a.k.a. Manifest Editors. The point I have is why is this in the update.ui package? Shouldn't it be moved into a eclipse.ui.forms package? For example the PDE uses eclipse.update.ui.forms, this doesn't seem right! Also, I needed to patch this stuff a bit to make it work out side of a fully initialised WorkBench (wrote my own AbstractForm class and moved the eclipse code onto that because Platform wasn't initialised to get alternate hoverover colors). So maybe that work should be done as part of this Bug? I think this work should be done as part of the V3 project since it WILL BREAK other plugins. If this is not a part of this bug then can you please tell me where to add this too.
We have done a number of UI enancement in 3.0 and we consider this plan item implemented. The update manager perspective has been replaced by an installation wizard and by a configuration management tool (modal dialog). For comment #2: that is a completely different request and I will let Dejan answer it.
