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.
HTTP Monitor menu item is first one in Debug menu. This is probably wrong.
Ah, that's because I place it relative to the other menu items. I guess they've changed the name of the action that I try to go underneath. I try to put it on the bottom of the menu normally :) David-John Burrowes has said that they would like to reserve the debugging menu for "while debugging" type actions only, and that he would prefer it if the monitor was a part of the output bar instead. So I'm not sure whether it's worth fixing this right now or not? I'm CC'ing David John on this so that he can give his opinion... a
Yes, many of the debugger menu items are being moved and changed in 3.4. It is true that I'm not sure the monitor should go in the debug menu. At the moment, one doesn't access any of the debugging views from here or from the debug toolbar. In the short term, I'd prefer that this just be available in the View menu and that the monitor appear in all the output windows. I don't understand what the impact of not fixing this right now is. (Our hope is, in the 4.0 timeframe, to find a better way to manage all the various debugger-related views).
IMO it is OK to have Monitor in Debug menu. But it is not the most important function here so I think it is bad if it is first item.
I don't think that this should go anywhere in the Debug menu at this time. The reason for this is that none of the many other debugging views (sessions, threads, watches, stack, breakpoints, console, IO, etc.) are available from the Debug menu currently. Why should the HTTP monitor be treated so specially?
Let's take the two issues separately. The issue originally filed is only about the placement in the View menu. Another issue about the placement in the Debug menu is captured in issue 31236. As for the original issue, here is Jiri Mzourek's stance on where it should be placed: between "Form Editor" and "Scripting Module". It would be good to have this addressed for Nevada/3.5, since this is a UI regression.
I will fix this for Tegal. I note that I have the exact same statement in the layer.xml file re the actions, but it places it last on one menu and first on the other... Go figure.
Any chance this can be addressed for Nevada as well? I consider it a UI regression.
It should be easy - just need to declare order of files in XML layer (and find the declaration of other items for their names before of course)
Fixed as requested.
Verified in Nevada build 030401.