There is:
Nautilus class context menu
1. - Analyze -> Create inst var accessors (which allows you to multiple inst
vars, but not omit setters/getters)
- Refactoring
2.   -> Class refactoring -> Generate accessors (which generates all by
default, but allows you to omit whichever methods you want)
3.   -> Inst Var Refactoring -> Accessors (which operates on a single inst
var, and allows you to omit getter or setter)

#1 seems to add nothing to the party. It's the least flexible and is covered
by #2.

My confusion: I was always using #3 and didn't even realize #1 and #2
existed. I started to write code to select multiple inst vars at once in #3
and stumbled upon #1 and #2. Maybe #2 could be duplicated next to #3 with a
more-differentiated name.

Slightly OT, it seems that listing the inst var "refactorings" (is adding an
inst var really a refactoring?) is kind of a hack. For me, it'd make more
sense and be more OO if the browser knew how to deal with inst vars
explicitly, maybe as a sidebar to the class definition, or maybe the class
definition should be abstracted behind a real UI. i.e. inst var widgets
instead of a string...



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Nautilus-accessor-over-generation-tp4679480.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.