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: | Cannot use 'inplace' rename on method | ||
|---|---|---|---|
| Product: | java | Reporter: | Marek Grummich <mgrummich> |
| Component: | Unsupported | Assignee: | Jan Becicka <jbecicka> |
| Status: | RESOLVED INVALID | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 4.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 53295 | ||
| Bug Blocks: | |||
|
Description
Marek Grummich
2004-06-22 14:08:52 UTC
Honzo, could you please disable inplace rename on these nodes the same way it is done for package nodes in project view? Is really disabling of a broken feature the correct way of fixing it? Please append comment from HIE person approving disabling of the feature. Thanks. disabling of a broken feature? What is broken? Plain rename was replaced with refactoring rename. fixed in /cvs/java/src/org/netbeans/modules/java/ui/nodes/elements/MethodNode.java,v <-- MethodNode.java new revision: 1.5; previous revision: 1.4 Well, we need to start a discussion here. I don't consider disabling the feature as fix. Please point me to some UI specification that says that there will be no other rename gesture than context menu Refactor | Rename. Inplace rename is well-known wide-spread rename gesture and it's being disabled. The broken feature is 'inplace rename'. Please Dusane, could you comment on this? Thanks. Just a note - the same approach is taken for the package nodes. In-place rename is common when it really means just rename - a simple operation. Refactoring should not be a simple action (like in-place editing) since it potentially affects a lot of other sources. AFAIK, the UI team wants to remove the nodes below the file node anyway and outline views are usually read-only. Of course that refactoring is complex process affecting other sources, but does user care about it if he wants just rename simple java file the way he was used to in previous release? UI team wants to have outline view in promo D? Nobody talks about renaming a single java file - that still works. Anyway, let me lower the priority to P3, now that the IDE does not behave erroneously and let's keep this issue open to discuss whether the original decision to disable in-place rename was correct or not. Well, I meant method rename, of course. It is impossible to reduce Rename Refactoring UI into inplace rename of method IMO. I don't know any IDE allowing that. But this is my personal opinion. Dusane, can answer Milan? Thanks Inplace renaming works for package and java file currently. Logically it should work for methods, fields and constructors too in my opinion. Behavior of inplace refactoring in not specified. Please add it to a refactoring ui spec. Issues: Regular refactoring does prechecks, before user is allowed to set new parameters. When should be these prechecks done? Where should be result of prechecks displayed? Should inplace rename invoke any dialog? Note: Rename of file and package is already specified. Inplace Rename of file, methods, fields is mentioned in this spec (Rename chapter and figure 4 for file): http://ui.netbeans.org/docs/hi/javamdr/refactoring_design.html Only one detail will be changed against figure 4...Use "Method" string instead of "File" text in the title of dialog. Does it have sense for you? Yes you are right, it is mentioned there. Sorry, I didn't see it. We are unable to implement it with current API. Method nodes removed from explorer. This issue is not valid any more. |