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.
Here is argumentation of users: Victor Smirnov wrote: > hello! > > thank you for your replies! > > it seems to me, that i should explain, why i do want this featrue :))) > when you open too many documents in the editor the tabs in the bottom of the > editor window > go into several lines. when you select the tab it goes to the top, so the > order of the tabs changes > and it takes quite a lot time to find the previous document. it doesn't > occur when you use > window manager's frame navigation ( trully speeking i don't know about unix, > but in win it seems to be ok ) > the first document is allways the first and so on. > well opening documents in single source editor window has it's own > advantages, so i think > their should be an option and existing behavior as a default. > > thank you for help > victor -------------- John Richardson: If I understand correctly, this is a suggestion I made a while ago. What Victor describes is to use the "Multiple" part of MDI, instead of tabs. I can't seem to check now, but but there should be an entry describing this. (Although I'm glad someone else brought it up this time). A big advantage to this is that if all "editors" are considered documents, I can navigate quickly though the things that I'm changing. So, if I'm using the GUI designer with several windows open and the text editor with several windows open, I can easily switch between GUI designer windows (a) and (b) as well as text editor window (c) by using "quick open file navigation." (I submitted a proof of concept for quick open file navigation using a quasimodal command a month or two ago.) Another advantage is you can tile windows. For instance, GUI designer windows (a) and (b) above as well as text editor (c) so you can see them all at the same time. This works in both SDI and MDI mode for the editor (indeed, with SDI mode you can use your window manager's Frame navigation (usually Alt-Tab). CC: nbui, hopefully a discussion can take place about this?
http://www.netbeans.org/issues/show_bug.cgi?id=16799
also see http://www.netbeans.org/issues/show_bug.cgi?id=16799
Target milestone -> 3.3.1.
Target milestone -> 3.4
Reassigning to Marek. Marek, please evaluate these enhancements, thanks.
Reassigning back to me, I would overload you, Marek :-)
Evaluation: Enhancement seems clear to me, its implementation in basic level (editors as separate documents) needn't be hard at all. Impl hints: - enhance behaviour of editor top component, add two states - regular (as it is now) and "separate", which will dock each individual editor component to new window remaining questions: - how should View/Source Editor action behave? - should all windows have titles Source Editor [file_name] or only [file_name]? - how should this feature work when there will be no desktop space, as suggested in 11010, which seems to be of high priority? Please, ui team, elaborate on this, we need your help.
*** Issue 18656 has been marked as a duplicate of this issue. ***
We'll have to rethink this enh, as UI team requests that whole inner desktop should be killed (issue 11010). This enh doesn't make sense without inner desktop. It looks like whole inner desktop will be replaced by tabbed view. So - (questions primarily for you, John) how should tabbed view behave so that you are satisfied and don't need separate frames for editors anymore? It is possible to maintain your work as you wanted without need for separate frames in desktop area?
It is certainly possible to work without the desktop. In fact, if the result of killing it is a more usable UI (quick open file navigation, no requirement for tabs taking up space, etc...), I'd be quite happy to see it go.
Heh, John, that's the question. Without tabs? We'll see.. I look forward to see UI spec which is being prepared by UI team, pls stay tuned on nbui mailing list, we'll need your opinion and comments on usability issues. Thanks!
UI please evaluate.
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.
issue doesn't apply to new window system - verified