DeprecationHistory

> Hi all,
> One of my recents slice for preferences migration has made pharo nearly
> unusable
> because a lot of  deprecation dialogs was opened for a single browser.
> Then, the user had to forbid the deprecation warnings in order to avoid
> these popups.
>
> Now, what about a non blocking window which is opened automatically when a
> deprecated method is run,
> but showing the list of recents deprecations ?
> A double click on a list item, et hop!,  a browser is opened on the
> deprecated method.
> I've tried it on the last pharo image and it seems ok. With it, it is still
> always possible to let deprecation warning
> without having to close any dialog window.
> What do you think ?
>
> A screenshot is attached.
> Cheers
> Alain
>

> 2009/12/8 Alain Plantec<[hidden email]>:
>    
>> Hi all,
>> One of my recents slice for preferences migration has made pharo nearly
>> unusable
>> because a lot of  deprecation dialogs was opened for a single browser.
>> Then, the user had to forbid the deprecation warnings in order to avoid
>> these popups.
>>
>> Now, what about a non blocking window which is opened automatically when a
>> deprecated method is run,
>> but showing the list of recents deprecations ?
>> A double click on a list item, et hop!,  a browser is opened on the
>> deprecated method.
>> I've tried it on the last pharo image and it seems ok. With it, it is still
>> always possible to let deprecation warning
>> without having to close any dialog window.
>> What do you think ?
>>
>> A screenshot is attached.
>> Cheers
>> Alain
>>
>>      
> +1 I like the idea...
>
> Nicolas
>    

> Hi all,
> One of my recents slice for preferences migration has made pharo nearly
> unusable
> because a lot of  deprecation dialogs was opened for a single browser.
> Then, the user had to forbid the deprecation warnings in order to avoid
> these popups.
>
> Now, what about a non blocking window which is opened automatically when a
> deprecated method is run,
> but showing the list of recents deprecations ?
> A double click on a list item, et hop!,  a browser is opened on the
> deprecated method.
> I've tried it on the last pharo image and it seems ok. With it, it is still
> always possible to let deprecation warning
> without having to close any dialog window.
> What do you think ?
>
> A screenshot is attached.
> Cheers
> Alain
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> Henrik Sperre Johansen a écrit :
>> +2
>> Even better if there's a button in each row to open a list of the methods that have been recorded as calling the deprecated version :D
>>
>> Henry
>>  
> Hi Henry,
> Maybe something like that (see screenshot):
>
> Each root shows a deprecated method call.
> Here, 3 calls to the same deprecated method but from different paths.
> The occurence show how many time the deprecated method has been called with the same caller chain.
> 23 times for Try1>>call -> Try2>>call
> 2 times for Try2>>call
> 3 times for Try3>>call -> Try1>>call -> Try2>>call
>
> So, you see exactly which deprecated methods were called, from where and how many times.
>
> Alain
>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>  
>
> <DeprecationsTree.png>_______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Hi all,
> One of my recents slice for preferences migration has made pharo  
> nearly
> unusable
> because a lot of  deprecation dialogs was opened for a single browser.
> Then, the user had to forbid the deprecation warnings in order to  
> avoid
> these popups.
>
> Now, what about a non blocking window which is opened automatically  
> when
> a deprecated method is run,
> but showing the list of recents deprecations ?
> A double click on a list item, et hop!,  a browser is opened on the
> deprecated method.
> I've tried it on the last pharo image and it seems ok. With it, it is
> still always possible to let deprecation warning
> without having to close any dialog window.
> What do you think ?
>
> A screenshot is attached.
> Cheers
> Alain
>
>
> <DeprecationHistory.png><ATT00001..txt>