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.
... in the first use. It takes around 600ms on my machine (P3 733, 512 MB RAM, W2K). Running in profiler, it looks like over 70% of time is spent in ToolsAction.Popup.run(). Is it necessary to have ToolsAction on FS node? It loads really large number of classes from different places.
Implementing warm-up in issue 27769 helped to reduce the time to cca 450ms (build dev 20030128).
dpavlica: what do you think about removing Tools submenu from Filesystems node's context menu as Tomas suggested. It doesn't make much sense to me either.
That text "Empty" in the submenu looks really strange and isn't logic. So...Let's remove Tools item from Filesystems node's context menu...
It's a bit more complicated. The "Tools" menu does not appear in the context menu on FS node now (it appeared - empty - due to another bug). But the ToolsAction *is* on the FS node, it is not displayed as there is no individual subaction enabled for this node. Evaluating all the actions during context menu invocation is the performance problem. Removing the ToolsAction from the node would eliminate it, but what if some tools action for FS node appears in the future? Or some external module provides some already now? So just removing it is not that easy. The second way is to cancel the evaluating of the actions and show "Tools" menu always when ToolsAction is present, but then we would get again the "Tools" > "Empty" menu... Is there a solution for this?
I see...Then we got back and we are marking time. Empty text in sub menu is really strange and I don't vote for it. So does exist another solution ? Unless improvement of implementation ;) I am thinking about UI hack way. It means: Showing Context menu with disabled and italic text "Resolving..." instead Tools text first. Then display right result (Enabled or Disabled Menu Item "Tools") on that place after evaluating of the actions. But it's hack and maybe worse then Empty text, maybe not ;)
Some notes after discussion with performance team and HIE team: It's reasonable to taking away Tools from Filesystems from HIE point of view. It isn't not correct compatible change on the other hand (says on nbdev) and Proposed solution is here: http://www.netbeans.org/servlets/ReadMsg? msgId=462005&listName=nbdev 1a. showing the action with empty submenu, if there is no enabled action: Tools->Empty 1b. doing 1a only for the first time, as soon as ToolsActions are loaded, one can hide the action quickly 2. warming up all ToolsActions, as it is something every user will need one day. 3. Replacing the submenu with a dialog to select the right action. Something that happened to New... action. I have not agreed with 1a) 1b) yet and 3) isn't ok because user would like to use Tools action quick without another dialog. So it looks that 2) could help, but I don't know if so much...
Filesystems node is no more present in promo-D