[Pharo-dev] Copy class needs more information to do a good job

2014-09-26 Thread Stephan Eggermont
Copy class needs more information to do a good job At the moment, the copy class command only asks for the name of the new class. That is not enough information. There have been a number of issues posted about copying (or not) of the class comment, Issue 13247, 10039, 12294 and 12265. Other in

Re: [Pharo-dev] Copy class needs more information to do a good job

2014-09-26 Thread Camille Teruel
Another annoying thing is that when you copy a hierarchy you have to change the subclass relationships manually. For example, if you select two classes -- Superclass Subclass -- and copy them you end up with NewSubclass as a subclass of Superclass instead of NewSuperclass. When copying a big hie

Re: [Pharo-dev] Copy class needs more information to do a good job

2014-09-27 Thread Marcus Denker
On 26 Sep 2014, at 16:10, Camille Teruel wrote: > Another annoying thing is that when you copy a hierarchy you have to change > the subclass relationships manually. > For example, if you select two classes -- Superclass Subclass -- and copy > them you end up with NewSubclass as a subclass of S