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 43935 - Move main window listening code out of masterfs
Summary: Move main window listening code out of masterfs
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: rmatous
URL:
Keywords: ARCH, T9Y
Depends on:
Blocks:
 
Reported: 2004-05-27 15:50 UTC by Jesse Glick
Modified: 2008-12-22 22:40 UTC (History)
2 users (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 Jesse Glick 2004-05-27 15:50:54 UTC
Does not belong here, and may in fact cause
problems for unit tests and headless mode in general.

Suggest core/windows instead.
Comment 1 rmatous 2004-05-27 16:10:51 UTC
I agree. I wanted just test it, find possible problems and let people
complain about performance or other possible problems. 

Dafe might have some comments about it.
Comment 2 David Simonek 2004-05-28 14:03:46 UTC
Jesse, core/windows? I'm not strongly against, but how does the code
relate to winsys as such? I think that there is *no* relation except
from listening to main window (which is a hack anyway, will probably
not work totally OK in separate window mode and could be done by
listening on getAllFrames() instead).
I can think of other possibilities - explorer code or utilities perhaps.

Just clarification - in perfect world, fs should get notified from OS
fs layer, update its model and fire changes to asociated listeners, is
that right?
Comment 3 Jesse Glick 2004-05-28 14:10:36 UTC
Not attached to core/windows as such; but it absolutely should not be
in openide/masterfs, or anywhere in openide for that matter. Maybe
core/ui would be appropriate.

Re. push vs. pull model - yes, if Java supported that we would use it
of course.
Comment 4 rmatous 2004-06-10 10:54:55 UTC
core/ui - why not ? Could I hook on main frame in some warmUp task ?
Is there any problem with it ? Or is there better trigger ?
Comment 5 rmatous 2004-06-23 10:51:18 UTC
/cvs/core/ui/src/org/netbeans/core/ui/MenuWarmUpTask.javarevision:
1.6; previous revision: 1.5

/cvs/openide/masterfs/src/org/netbeans/modules/masterfs/MasterFileSystem.java
new revision: 1.13; previous revision: 1.12

/cvs/openide/masterfs/src/org/netbeans/modules/masterfs/WindowsActivatedHandler.java
new revision: delete; previous revision: 1.2