Ok, then we will integrate it together when you come to Lille in 2 weeks.

Good news.

Cheers,


2013/7/12 Andrei Vasile Chis <[email protected]>

> Hi Clément, Hi Clara,
>
>
>  What about integrating the new debugger by default now ? I mean the new
>>> debugger is now in Pharo 3.0 alpha but the old debugger is still triggered
>>> by default, for example when you do Cmd+Maj+d or when you set the setting
>>> 'Always open full debugger'. We (Marcus and I) would like to integrate it
>>> now by default in Pharo 3.0 alpha, so we have enough time to stabilize it
>>> (in case of problems) and we can then remove the old debugger and old
>>> inspectors from Pharo.
>>>
>>> Now I want your point of view:
>>> - What do you think about integrating the spec debugger by default next
>>> week ?
>>>
>>
> In two weeks (22 July) I would visit you in Lille. That would be a good
> time to integrate.
>
>
>
>>  - Is it currently stable enough ?
>>>
>>
> All the features that are present at the moment are quite stable.
>
>
>
>>  - Should I wait a little more so you can add extra features ?
>>>
>>
>> I've talked with Andrei and we've set a "milestone". By next week, we
>> would like to have done issues
>> 10956
>> 10952
>> 10954
>> 10953
>> 10955
>>
>
> If at least the first three issues are done, then the new debugger will
> have most of the necessary features.
> I'd also help with these and I hope we'll be done by the end of this month.
>
>
>
>> By next week I will have more time, since the semester will be finished.
>>
>>>
>>>
>> Having Andrei's debugger by default requires that it has the full stack
>>> menu ready before the Pharo 3.0 release (next spring), because if not
>>> people will blame all the Pharo team.
>>> - Are you working on it ?
>>>
>> That's what I plan to do next week :) I'm working on it, but not full
>> time.
>>
>>
>>>  - Will it be ready before the next Pharo release ?
>>>
>>
>>> If you think you need to improve the debugger before we integrate it by
>>> default, for example with Clara's GSoC work, please tell me when it will be
>>> ready so we can add it into the Pharo 3.0 integration planning. Then I
>>> guess you can add a slice with your improvements in the Pharo bug tracker,
>>> and I will add an extra slice with smalltalk tools change so the new
>>> debugger will be triggered by default. It would be nice if we can integrate
>>> it before the end of september.
>>>
>>
> We'll surely be able to have all the missing features by the end of
> September.
> They do not require so much work.
>
>
>>
>> In any case I will be in case with both Andrei and you (if you don't
>> mind) to get this done...
>>
>> Please do :)
>
> Cheers,
> Andrei
>
>
>

Reply via email to