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.
[ JDK VERSION : 1.5.0_02 ] I more like the navigator placed in editor's window tool bar as it was in version 4.1, because an additional window robs space on the screen.
I think as design, but we'll see ...
Correction: ...as it was in version 4.0. Also I think, there should be a link to editor component too.
There are two solutions I see: 1) Use navigator as sliding window, that means that navigator is visible only on request and doesn't take space. 2) When enh 54958 eventually gets implemented, "popup" version of navigator will be available. Again that means no takes space. Btw I don't understand the sentence "there should be a link to editor component too" Which link? How should it look like? Generally speaking, navigator as a window or as a popup offers lot more functionality (fast search, sorting, filters, inheritance view etc.). And navigator will support html files, xml files, ejbs, property files in future. Given that, we don't plan to place navigator back in editor's toolbar, as suggested other solutions should be enough, thanks.
"Which link?" I mean, when a user is focused on a line in source editor, the appropriate member should be selected in Navigator window. There is no longer any indication of which method is currently being edited (the old dropdown used to update as you moved from method to method). "Use navigator as sliding window" Isn't this only possible in MDI mode ? I use SDI mode. Why can't you give an option to choose between Navigator window and dropdown in the Editor's window ? Also why isn't Editor's toolbar customizable ?
re to first part - yes I fully agree with this use case, will be tracked and fixed in issue 57129. second part - unfortunately, yes, only in MDI. third part - Because we believe (based on users comments, looking at competitors) that editor's toolbar combo was not powerful enough and only minority of users actually used it. Also code was a bit hard to maintain, so there was a chance to get rid of buggy code as well. Generally, if 54958 and 57129 will be implemented, would it be enough? Last question I can't answer, co I'm ccing editor guru mmetelka to answer. Thx.
> Generally, if 54958 and 57129 will be implemented, would it be enough? Yes, I think so, but let us wait, until it is implemented, and editor's toolbar is customizable. Please note, that I don't understand Issue 54958 in detail anyway.
Regarding editor's toolbar customizability: the editor's toolbar implementation merges contents of two folders (target-mimetype-toolbar-actions plus base-toolbar-actions) from the xml layer so the global toolbar support of the IDE could not handle this (we do not use it at all). It is somewhat difficult to write customization GUI support for this case when the contents are merged from two layer folders. Also we lack icons for many of the editor actions. At this time we do not plan to support editor toolbar customizability in a near future.