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: | Feature request: Keyboard shortcuts for build targets | ||
---|---|---|---|
Product: | projects | Reporter: | John Zollinger <jzollinger> |
Component: | Ant | Assignee: | issues@projects <issues> |
Status: | CLOSED FIXED | ||
Severity: | enhancement | CC: | issues |
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 7987 | ||
Bug Blocks: |
Description
John Zollinger
2000-10-13 20:25:56 UTC
Deferred for later. I think there are some UI questions that should be resolved first. For a start, you should be able to set an Ant build file as a project main class (I think it needs to implement ExecCookie first--this is the primary bug). Then Execute Project action would run a test target of your choice. Further, it should implement CompilerCookie so that you can add a link to the Ant script to your Projects tab, and Build Project action (also Execute Project) would automatically compile it. This would provide consistency with general NetBeans UI. Assigning shortcuts to objects, rather than actions, is definitely nonstandard so I am not sure if it is a good idea. Perhaps a way to create links to individual targets, as well as whole build files, in the Projects tab would satisfy most of the need (other than easy keyboard navigability). At least you would not have to search to find the target you wanted. As for binding F9 to <target name="compile">: I think this is not the right approach. Rather, there should be an Ant compiler type which builds a file using an Ant script. This would make regular F9 (Compile action) work as desired. Now in development versions there is full compilation/execution integration, so F6/F9 does work as you would expect, plus you can assign an Ant script as your "project main class" and then the usual shortcuts like Execute Project etc. should work. So I think the main basis of this request is actually implemented. CC'ing the projects module as an FYI, both about the idea of having custom shortcuts for particular objects in the project (vs. actions)--this might be implemented e.g. by creating a special XML DTD representing a javax.swing.Action instance of a predefined class configured with a target DataObject or Node.Handle and desired shortcut name (= key), and placing instances in the Shortcuts/ folder to make a key binding; and the idea of adding links to arbitrary nodes (not data objects) to the Projects tab (in the trunk, try e.g. creating system/Projects/Default/Files/foo.ser containing a serialized version of a Node.Handle) as a different kind of quick link or shortcut. Either of these things could be useful in conjunction with the Ant module, maybe. Verified, IMO implemented, see action "Shortcut to target" in pop-up menu in Explorer for New|Ant Projects|Shortcut to target. x Was fixed in 3.3. Resolved for 3.3.x or earlier, no new info since then -> closing. Resolved for 3.3.x or earlier, no new info since then -> closing. |