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 32403 - Separate window system implementation to core/windows module
Summary: Separate window system implementation to core/windows module
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Peter Zavadsky
Depends on:
Blocks: 24888 29836
  Show dependency tree
Reported: 2003-03-27 14:52 UTC by Peter Zavadsky
Modified: 2008-12-23 12:30 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zavadsky 2003-03-27 14:52:14 UTC
The implementation has to reside in core/windows
module purely. Only exposed API will be some
methods from WindowManagerImpl (should be
specified by some interface), basically just load
& save (btw. setVisible).

The core/windows module may not be dependant from
core module.

It means there will be moved all classes from package (and
subpackages) except MiniStatusBar (it is
NbMainExplorer implementation doesn't have to do
with winsys anythin). 
Plus also classes NbPresenter, NbDialog, i.e.
DialogDisplayer impl.
Comment 1 Peter Zavadsky 2003-03-30 07:48:40 UTC
Now it seems (as I looked into core/output) vice versa. I.e. the core
has to be independent. 
So there is necessary to have some kind of callback which will start
and finish window system.
Comment 2 Peter Zavadsky 2003-03-30 14:42:44 UTC
I just separated the new winsys in the branch [winsys_29836]

I'm not sure about all changes.
I moved there also NbPresenter, NbDialog, also NbNodeOperation
(renamed). All those things seem to be dependant on window system. 

(Here I separated Sheet (named NbSheet) from NbNodeOperation. which is
properties component implementation and has nothing to do with winsys.

Also toolbars, which are kind of individual, and needs to be
redesigned (their creation - showing are too tight to fs changes).

The bridge between core and core/windows are now designated by
NbTopManager.WindowSystem interface which offers basic control over
window system.
Comment 3 Peter Zavadsky 2003-03-30 14:46:08 UTC
Forgot to mention, I also repackaged window system classes (in that
Comment 4 Jesse Glick 2003-03-31 17:49:35 UTC
Sounds basically right.

IMHO things like default explorer & property sheet components should
be in core-ui.jar.

Toolbars should be in core-windows.jar; don't worry about persistence
of these at the moment - David K. can talk about how they should be
stored in the future.

I think NbDialog was used from NbErrorManager directly, make sure that
is still working sensibly.
Comment 5 Peter Zavadsky 2003-04-02 06:55:33 UTC
Fixed in [winsys_29836] branch.

It is now in modules/core-windows.jar

Note: There will be later probably separated the DialogDisplayer etc.
from it.