On Fri, Mar 20, 2015 at 11:42 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:

GitHub wrote

...

14890 Browsing a different class should select by default the previously browsed method https://pharo.fogbugz.com/f/cases/14890

Ugh. This breaks my workflow. I often click the "Class-side" checkbox to get to the class template, but now it keeps the method selected. At first, I sat there like a monkey (no offense Ulysses ;)) and kept hitting it repeatedly with a perplexed look on my face. Later I saw this issue and connected the dots. I'm not saying its a bad change (I'm not entirely clear on the use case), but...

Policy Suggestion: Tool UI changes /must/ be discussed on the list prior to integration.

I've actually been wanting this for a long time (thank you). The use case is to make it easier to observe differences between super/subclasses and sibling classes for the same method. For example, click on DelayScheduler>>shutDown, then click on its two subclasses to observe the different implementations. However the current implementation makes it difficult to view class definitions. Continuing the previous example, after selecting #shutDown, try view the class definitions of DelayScheduler and subclasses. Useful additional behaviour would be that clicking on a class that is already selected would change to class-definition-mode . Clicking on the class again would toggle back to previous-method-mode. Ideally modes would hold between change in class selection, however its a bit late to be experimenting with this. It would probably be simplest to just reset the previous-method when a selected class is clicked on again, and also when class-side button is clicked - or otherwise roll back and leave it for Pharo 5. cheers -ben

I'd like to see it in Pharo 5. cheers -ben On Sat, Mar 21, 2015 at 1:23 AM, stepharo <stepharo@free.fr> wrote:

We should rollback this change. I did it and I will keep it for me.

Stef

Le 20/3/15 17:40, Ben Coman a écrit :

On Fri, Mar 20, 2015 at 11:42 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:

...

GitHub wrote

...

14890 Browsing a different class should select by default the previously browsed method https://pharo.fogbugz.com/f/cases/14890

Ugh. This breaks my workflow. I often click the "Class-side" checkbox to get to the class template, but now it keeps the method selected. At first, I sat there like a monkey (no offense Ulysses ;)) and kept hitting it repeatedly with a perplexed look on my face. Later I saw this issue and connected the dots. I'm not saying its a bad change (I'm not entirely clear on the use case), but...

Policy Suggestion: Tool UI changes /must/ be discussed on the list prior to integration.

I've actually been wanting this for a long time (thank you). The use case is to make it easier to observe differences between super/subclasses and sibling classes for the same method. For example, click on DelayScheduler>>shutDown, then click on its two subclasses to observe the different implementations.

However the current implementation makes it difficult to view class definitions. Continuing the previous example, after selecting #shutDown, try view the class definitions of DelayScheduler and subclasses.

Useful additional behaviour would be that clicking on a class that is already selected would change to class-definition-mode . Clicking on the class again would toggle back to previous-method-mode. Ideally modes would hold between change in class selection, however its a bit late to be experimenting with this. It would probably be simplest to just reset the previous-method when a selected class is clicked on again, and also when class-side button is clicked - or otherwise roll back and leave it for Pharo 5.

cheers -ben