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 26212 - Do not block AWT event queue when initializing workspaces
Summary: Do not block AWT event queue when initializing workspaces
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords: PERFORMANCE
Depends on:
Blocks: 26581
  Show dependency tree
 
Reported: 2002-08-02 09:05 UTC by Jaroslav Tulach
Modified: 2008-12-23 09:35 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2002-08-02 09:05:15 UTC 
Due to lazy loading of workspaces the first change
takes very long time and moreover it blocks AWT
thread causing user to believe that something is
wrong.

Let's move the initialization of the workspace out
of AWT thread - somehow signal that the switch is
in progress, load the components in separate
thread(s) and show them only when they are
initialized.

This could be taken a step further by loading just
positions and names of the components (that is
probably fast) and instead of the component itself
show placeholder saying that the component is
being initialized till it is deserialized and
replaces the placeholder.
Comment 1 Petr Nejedly 2003-07-09 13:07:36 UTC 
Peter, this was implemented in 3.5 release cycle, wasn't it?
Comment 2 Peter Zavadsky 2003-07-11 15:09:30 UTC 
Well, I can't remember now if it was.. Marek do you know about it?
Comment 3 Marian Mirilovic 2003-11-26 12:56:30 UTC 
Because Window System v1 will not be supported from now by our team, all old
winsys issues (now "core/window system v1" issues) are going to be closed as
WONTFIX. 

Changes in API which emerged both from UI spec 
and problems with adjusting to the older API are described in the document
http://core.netbeans.org/windowsystem/changes.html.
 It shows also recommends how the client code should be adjusted to the new
window system.

If you think this issue apply also to the new winsys then change the
subcomponent (to "core/window system") and REOPEN it.
Comment 4 Marian Mirilovic 2004-02-27 14:09:07 UTC 
issue doesn't apply to new window system - verified