This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102221 - usability: Installed features in Plugins Manager should be collapsed by default
Summary: usability: Installed features in Plugins Manager should be collapsed by default
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Plugin Manager (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks: 102289
  Show dependency tree
 
Reported: 2007-04-23 19:50 UTC by Peter Lam
Modified: 2007-08-08 12:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lam 2007-04-23 19:50:26 UTC
With only Base IDE, Java IDE and UML installed, there are 233 items listed under
the "Installed" tab in the Plugins Manager. If more features are installed, this
number should be much bigger so the current default expanded state would be very
hard for finding the feature/module of interest for deactivating or
uninstalling. IMO, all top level features/modules should be collapsed by
default, at least this is what it was in the old Module Manager feature. I'd
call this a regression here.
Comment 1 Jiri Rechtacek 2007-04-24 10:35:50 UTC
It's not a regression, Plugin Manager UI must conform to its UI spec. not to old
Module Manager UI spec. I miss the opportunity to affect UI review what run a
month ago.
Anyway, I attach this problem as some of problems for next round of UI spec. -
issue 102289.
Comment 2 Peter Lam 2007-04-24 16:26:54 UTC
I don't disagree but if this is per ui spec, then there's problem in ui spec
that's not addressing the usability. IMO, new replacement feature should at
least address the usability of a previous feature being replaced. And this is
one of the area not being considered.
Comment 3 Jiri Rechtacek 2007-04-24 16:49:49 UTC
Yes, I see the problem it will be considered again.
But in general I don't think so all features of NB5.0 Autoupdate should be
mirroring in Plugin Manager. Some of reason to contribute new one Plugin Manager
is its simplification and to be more end-user centric as possible. This implies
some facilities from old one feature won't in new one because are out of its scope.
Comment 4 Jiri Rechtacek 2007-08-08 12:00:42 UTC
After integrating issue 110566 the module itself can control if should be visible in Plugin Manager or not (attribute
AutoUpdate-Show-In-Client: false or true in manifest.mf) This will help to hold down count of visible modules in PM.