On 26 Sep 2014, at 16:10, Camille Teruel <[email protected]> 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 Superclass instead of
> NewSuperclass.
> When copying a big hierarchy it's tiresome.
>
We need to distinguish between #copy: low level copy of classes, as opposed to
the tool, which should provide a nice dialog (copy comment yes, no, copy
superclass hierarchy, where to put
the copy…)
Marcus
> On 26 sept. 2014, at 14:08, Stephan Eggermont <[email protected]> wrote:
>
>> 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 information that can be helpful is the package where the new class
>> should be. I nearly never need a copy in the package where the original was.
>>
>> Cheers,
>> Stephan
>>
>> https://pharo.fogbugz.com/default.asp?14084
>
>
signature.asc
Description: Message signed with OpenPGP using GPGMail
