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: | MainMenuAction$ShowToolBarAction initializes Settings | ||
---|---|---|---|
Product: | editor | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Settings | Assignee: | issues@editor <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | Keywords: | PERFORMANCE |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 90403 | ||
Bug Blocks: |
Description
Jaroslav Tulach
2008-02-15 12:13:30 UTC
Imho it is unfortunate that an action, actually not visible action causes load for client code that builds on top of editor, but is not really useful. The action is fine, it does what it needs to do - it reads its own setting. The problem is in the design of the old settings infra, which in order to access one settings (a simple boolean setting) loads all the other settings as well. Once we (1) fix #90403 and deprecate BaseOptions and Settings and (2) rewrite the modules to actually stop using these classes we won't have problems like this one anymore. I'd like to stress out that we will have to do both (1) and (2) to actually improve current situation. Big solution is indeed desirable, however there may be simpler one: Just do not update the state of the action, until it is really needed, until it is visible. This should not happen anymore. You may also be pleased to know that I added a handful of editor kit classes on the blacklist. This is probably maximum where we can get without fixing #90403. Please let me know if you can see any measurable effect. changeset 5a39d12eecf4 in main details: http://hg.netbeans.org/main?cmd=changeset;node=5a39d12eecf4 |