[Pharo-project] Enhancement: Browsing SLICE dependencies with tree view in Monticello Repository Inspector
I originally thought something was wrong when I could not browse the code of a SLICE using Monticello. After hunting around I found [1] saying this is expected behaviour. However I then suggest the following enhancement: Have the right-pane of the Monticello Repositoy Inspector be a tree view, such that dependencies are the children which can then be <Browsed> together from the one place, rather than having to chase them manually. This seems more intuitive usage, especially for those not familiar with what slices are. (I had to hunt around for 5 minutes to find out) What do you think? cheers, -ben [1] http://code.google.com/p/pharo/issues/detail?id=1606 says " <Browse> in MC only browses the contents of the *selected* package - not of dependent packages. Therefore the slice package always looks empty, because it actually is empty."
Hi Ben. I think this was fixed in Pharo 1.4. Can you try and if true, close the issue? Thanks On Thu, Feb 9, 2012 at 1:47 AM, Ben Coman <btc@openinworld.com> wrote:
I originally thought something was wrong when I could not browse the code of a SLICE using Monticello. After hunting around I found [1] saying this is expected behaviour. However I then suggest the following enhancement:
Have the right-pane of the Monticello Repositoy Inspector be a tree view, such that dependencies are the children which can then be <Browsed> together from the one place, rather than having to chase them manually. This seems more intuitive usage, especially for those not familiar with what slices are. (I had to hunt around for 5 minutes to find out) What do you think?
cheers, -ben
[1] http://code.google.com/p/**pharo/issues/detail?id=1606<http://code.google.com/p/pharo/issues/detail?id=1606> says " <Browse> in MC only browses the contents of the *selected* package - not of dependent packages. Therefore the slice package always looks empty, because it actually is empty."
-- Mariano http://marianopeck.wordpress.com
Mariano, After getting distracted by a few other things in Pharo-1.4, I just got a chance to try this and it now works "as expected" to (I assume) browse the combined code of dependents. Thanks for the tip and also to those responsible for the change. Mariano Martinez Peck wrote:
Hi Ben. I think this was fixed in Pharo 1.4. Can you try and if true, close the issue? Thanks
On Thu, Feb 9, 2012 at 1:47 AM, Ben Coman <btc@openinworld.com> wrote:
I originally thought something was wrong when I could not browse the code of a SLICE using Monticello. After hunting around I found [1] saying this is expected behaviour. However I then suggest the following enhancement:
Have the right-pane of the Monticello Repositoy Inspector be a tree view, such that dependencies are the children which can then be <Browsed> together from the one place, rather than having to chase them manually. This seems more intuitive usage, especially for those not familiar with what slices are. (I had to hunt around for 5 minutes to find out) What do you think?
cheers, -ben
[1] http://code.google.com/p/**pharo/issues/detail?id=1606<http://code.google.com/p/pharo/issues/detail?id=1606> says " <Browse> in MC only browses the contents of the *selected* package - not of dependent packages. Therefore the slice package always looks empty, because it actually is empty."
participants (2)
-
Ben Coman -
Mariano Martinez Peck