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 36487 - [2003-10-10] Provide migration guidelines for modules migrating to the new windowing system
Summary: [2003-10-10] Provide migration guidelines for modules migrating to the new wi...
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC All
: P1 blocker (vote)
Assignee: jrojcek
URL:
Keywords:
Depends on:
Blocks: 36118
  Show dependency tree
 
Reported: 2003-10-08 12:38 UTC by jrojcek
Modified: 2008-12-22 20:25 UTC (History)
0 users

See Also:
Issue Type: TASK
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 jrojcek 2003-10-08 12:38:29 UTC 
HIEs should provide guidelines for module writers
who would migrate their modules to the new
windowing system.
Comment 1 jrojcek 2003-10-08 13:20:39 UTC 
Follows the list of short guidelines describing what should be
reviewed by module owners when migrating to the new windowing system:

- If your module defines its own workspace then you should consider 
replacing it by window set.

- If your module defines an internal mode (e.g. Form Editor window), 
then you should make a decision whether the top components inside the 
mode are of view or document type. If they are of view type, then
define an appropriate place outside of document area and put the
opening menu item into the "Window" menu. If they are of document
type, then put the top components into the editor mode.

- If your module defines an attached mode (e.g. Debugger window), then
presumably all contained top components would be of view type. You
should define an appropriate position in the new layout and define
menu items in "Window" menu.

- If your module defines a separate mode outside of the main window,
or opens a top component without a mode (e.g. Options, VCS Outputs,
Web Browser), then you should make a decision whether this window
should be part of the main window or it should be a non-modal dialog.

- If your module defines a top component placed in a mode defined by a
different module, then make sure that the mode still exists and its
position is suitable for your top component.

--------

Please, look at the issue #36119, which contains the placement
definition of all NetBeans IDE top components and modes.