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.
The real order that is inside the editor might work better than alphabetical sorting.
Not if the user intends to use the toolbar as a quick navigation. Searching for a symbol name in an alphabetically ordered list seems much easier than in (seemingly) unordered one. If the combo accepts keystrokes, trying to find the identifier fragments, it could be possible to use an ordering different from that one used to searches. Anyway, could you better explain your use case ? It seems somehow different from those solved by the quickbrowse combo.
Well, take it as suggestion. Since we do not have the target usecases on the quick browse very well specified either, it is hard to compare. The thinking behing using the order as in text is that it might be natural for the user to look at the combo content as a mental model or outline of the editor content. To say the truth, I am also not all that convinced that it would be better, it might make sense to try to live with it for a while to get a first hand experience.
Sure. What I am trying to find out, asking you for the usecase description is whether making the combo display configurable is enough. It may happen that the user needs to see/use textually ordered outline of the text and navigation UI (which uses the navigation key (== item name) ordering) at the same time. That would require another view to pop up/dock into the editor for the other task. IMHO making the display configurable is good anyway.
Set target milestone to TBD
Dusan, do you know if there is any need for this to be configurable (based on the usability studies)?
Rudolfe, please evaluate. Thanks
Just be aware that the quick browser is most probably going to be replaced with the code navigator in 4.1.
Quick browser was replaced by Navigator module
Reorganization of java component