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.
Summary: | [50cat] branding application: apple.laf.useScreenMenuBar=true | ||
---|---|---|---|
Product: | apisupport | Reporter: | lordy <lordy> |
Component: | Harness | Assignee: | pgebauer <pgebauer> |
Status: | NEW --- | ||
Severity: | blocker | CC: | tboudreau |
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | Macintosh | ||
OS: | Mac OS X | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 64573 | ||
Bug Blocks: |
Description
lordy
2005-09-16 20:35:50 UTC
Sounds reasonable. Yarda can you try it? However since we will not do issue #64573 for 5.0 anyway, I am not sure if it is wise to turn on the Mac menu bar by default, since it would not be fully compliant with Apple guidelines. I think #64573 has nothing to do with this. apple.laf.useScreenMenuBar is on in NetBeans 5.0 IDE by default and in most other big java apps i know. Also i can't remind about any issue with apple.laf.useScreenMenuBar post in the apple mail list. So I see no reason not to trun it on. "apple.laf.useScreenMenuBar is on in NetBeans 5.0 IDE by default" - exactly: we turn it on because we have done the work in ide/applemenu to make it look decent. The question is whether a typical Mac user would be more comfortable with a frame menu that looks like it would on other platforms; or a Mac menu which mostly works but does not have conventional bindings for About, Quit, etc. If you think going halfway is acceptable, then fine - we can do that easily enough. I think a frame menu look ugly on Mac OS X. And i know more professionally application which think going halfway is acceptable then professionally application that use frame menu. So please turn it on. No way I could do this before issue 64573 is fixed. *** Bug 181341 has been marked as a duplicate of this bug. *** I would actually prefer to be able to set this to either on/off in the module suite. The reason is that, while the screen menu tools certainly look nice, the apple screen menu doesn't fire events properly back to the JDK (e.g., selection events, focus events). For many developers, this might not matter, but for our team, we use these events to fire appropriate information to blind users on Mac OS X. Our code breaks completely with the screen menu code, and as such, we have to turn it off, despite that fact that, as lordy says, it looks a little funny. I've thought about this more. I think what be nice is that, if you right click on your module suite and click properties, instead of just Sources, Libraries, Application(etc), there was another module wide option called Settings, where the developer can set flags like this, either by allowing you to directly modify what the .conf file generated would be, or otherwise by just giving you a small selection of possible options that you can set. Mac OS X stuff. |