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.
| Summary: | Mount of a lot of FilleSystems needs progressbar | ||
|---|---|---|---|
| Product: | platform | Reporter: | pzajac <pzajac> |
| Component: | Dialogs&Wizards | Assignee: | Jiri Rechtacek <jrechtacek> |
| Status: | VERIFIED WONTFIX | ||
| Severity: | blocker | CC: | dpavlica, jglick, pnejedly |
| Priority: | P2 | Keywords: | PERFORMANCE |
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | TASK | Exception Reporter: | |
| Bug Depends on: | 26552, 27403 | ||
| Bug Blocks: | |||
|
Description
pzajac
2002-09-23 17:21:58 UTC
Yes, something should be done, ranging from at least progress cursor to full progress bar. Adjusting priority and ccing UI guy. Yes mentioned progress bar could be part of this global status line: http://ui.netbeans.org/docs/ui/nodedesc/ministatusbar_propo sal.html#test It only depends on agreement that this feature should be done for the next release. It depends on Progress API (issue 27403). First of all, what is the use case for mounting multiple FSes? If there's no real use case, just disable multiselection. IMHO if mounting several filesystems takes *multiple seconds* then that is a simple performance bug - there should be no need for a progress bar for doing something which consists solely of making a small change to settings. Has anyone taken the time to run a profiler on this? What exactly takes so long? There is a use case (at least in the NB 3.x projects system) - starting a project with many JAR libraries. People complained loudly about the lack of multiselection before it was implemented. No longer relevant for D. v |