Hi Ben. I think this was fixed in Pharo 1.4. Can you try and if true, close the issue?<br>Thanks<br><br><div class="gmail_quote">On Thu, Feb 9, 2012 at 1:47 AM, Ben Coman <span dir="ltr">&lt;<a href="mailto:btc@openinworld.com">btc@openinworld.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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:<br>

<br>
Have the right-pane of the Monticello Repositoy Inspector be a tree view, such that dependencies are the children which can then be &lt;Browsed&gt; together from the one place, rather than having to chase them manually. <br>

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)<br>
What do you think?<br>
<br>
cheers, -ben<br>
<br>
[1] �<a href="http://code.google.com/p/pharo/issues/detail?id=1606" target="_blank">http://code.google.com/p/<u></u>pharo/issues/detail?id=1606</a><br>
says &quot; &lt;Browse&gt; 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.&quot;<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>