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 36268 - [2003-10-03] Define behaviour when loading userdir or modules with older version of XML layer
Summary: [2003-10-03] Define behaviour when loading userdir or modules with older vers...
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: jrojcek
URL:
Keywords:
Depends on:
Blocks: 36138
  Show dependency tree
 
Reported: 2003-09-24 16:53 UTC by mslama
Modified: 2008-12-22 18:41 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 mslama 2003-09-24 16:53:58 UTC 
1.Define what should be imported when old user dir
is loaded.
2.Define what should be done when module with old
winsys config data is installed.
Comment 1 jrojcek 2003-10-03 10:53:28 UTC 
Please note, that even if the following migration should assure a
backward compatibility of user experience by showing old windows in
the (almost) correct location, some windows might be shown in
incorrect area. By this migration we almost for sure break one of the
main characteristics of the new windowing system: "All the windows
appearing outside of the document should be accessible from the
'Window' menu". That is why if a module defined a window (mode) in the
old windowing system, the module owner should make sure that it works
with the new windowing system and make appropriate changes if needed. 

The ideal automatic migration is following:

1. From the old user dir read workspaces one by one (start with the
editing workspace). If you find a mode which is not defined in the new
layout, do the following transformation:

a) If the unknown mode is internal and defines top components (not
already known in the new layout) in:
       - the top area of the mode then create a special mode named
"top_mode" (if not already created) in the new layout and put all
unknown top components from the old mode there. Dock the "top_mode" to
the top of the document area.
       - the left area of the mode then put all unknown top components
into the Explorer mode.
       - the bottom area of the mode then put all unknown top
components into the Output mode.
       - the right area of the mode then put all unknown top
components into the Properties mode.
       - the center area of the mode then put all unknown top
components into the Explorer

b) If the unknown mode is attached to:
       - the top then dock the mode to the top of the document area
and move the unknown top components also (doesn't matter in which area
of mode the TCs were).
       - the left then dock the mode to the left of the document area
and move the unknown top components also (doesn't matter in which area
of mode the TCs were).
       - the bottom then dock the mode to the bottom of the document
area and move the unknown top components also (doesn't matter in which
area of mode the TCs were).
       - the right then dock the mode to the right of the document
area and move the unknown top components also (doesn't matter in which
area of mode the TCs were).

c) If the unknown mode is a separate window then use the same rules as
for the internal mode.

d) If a mode is already present in the new layout, we should still
look for unknown TCs inside it and follow the above transformation rules.

2. If a module with old winsys config gets installed, then follow the
same rules as for the old user dir.