Bug 36277 - Better marketing of encapsulate field [code manipulation] [refactoring]
Summary: Better marketing of encapsulate field [code manipulation] [refactoring]
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2003-04-09 08:13 EDT by Oyvind Harboe CLA
Modified: 2004-08-18 06:41 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oyvind Harboe CLA 2003-04-09 08:13:35 EDT 
The "Source->Generate getter and setter method" is kinda obsolete.

If any code has been written at all, the user really should be 
considering "Refactoring->Encapsulate field".

The "Refactoring->Encapsulate field" should be better "marketed".

Possible action: retire "Source->Generate getter and setter method".



Øyvind
Comment 1 Ilja Preuss CLA 2003-06-23 05:19:12 EDT 
Downside: Generate Getter/Setter is much faster than Encapsulate Field.
Comment 2 Jason Yip CLA 2004-02-26 17:19:35 EST 
-1 on this one

I agree with Ilja that Generate getter and setter is faster in some cases which 
is why removing it just makes things less convenient.
Comment 3 Dirk Baeumer CLA 2004-08-18 06:41:38 EDT 
It is very unlikely that we can get rid of Generate Setter/Getter. Closing.