[Pharo-dev] [update 3.0] #30449

Martin Dias tinchodias at gmail.com
Fri Oct 4 09:44:45 EDT 2013


Excellent!!!!!!!!!!!!!!!!!!!!!!!!!!

On Fri, Oct 4, 2013 at 3:21 PM, Andrei Chis <chisvasileandrei at gmail.com> wrote:
> Now it would be nice to see what other actions do we need in the debugger
> for creating methods
> https://pharo.fogbugz.com/f/cases/5338/Create-button-in-debugger-for-subclassResponsibility-shouldBeImplemented-etc
>
>
> On Fri, Oct 4, 2013 at 2:57 PM, Marcus Denker <marcus.denker at inria.fr>
> wrote:
>>
>> 30449
>> -----
>>
>> 11777 Fix SpecTests
>>         https://pharo.fogbugz.com/f/cases/11777
>>
>> 11776 Fix Create action on #subclassResponsibility
>>         https://pharo.fogbugz.com/f/cases/11776
>>
>>
>> The debugger now displays the create button when an exception of type
>> #subclassResponsibility is shown. However this action should only be shown
>> if we are not working with an object of the abstract class (yes, normally it
>> should not happen). Also all possible superclasses in which the method can
>> be added should be displayed:
>> for example consider this hierarchy:
>> Parent
>>   -> Child1
>>     -> Child11
>>         -> Child111
>> and
>> Parent>>doSomething
>>   self subclassResponsibility
>>
>> In this case 'Parent new doSomething' should not add a create action in
>> the debugger.
>> 'Child1 new doSomething' should automatically implement the method in the
>> class Child1
>> 'Child3 new doSomething' should allow the user to select if he wants to
>> add the method in classes Child1, Child2 or Child3.
>> In all cases traits should be taken into account.
>>
>>
>>
>>
>> Diff information:
>>
>> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Tests-MarcusDenker.37.diff
>>
>> http://smalltalkhub.com/mc/Pharo/Pharo30/main/DebuggerActions-MarcusDenker.62.diff
>>
>




More information about the Pharo-dev mailing list