[Pharo-users] Nautilus>>openOnClass: gives back a debugger

Marcus Denker marcus.denker at inria.fr
Tue Oct 6 02:44:33 EDT 2015


> On 06 Oct 2015, at 08:31, Nicolai Hess <nicolaihess at web.de> wrote:
> 
> 
> 
> 2015-10-06 8:06 GMT+02:00 stepharo <stepharo at free.fr <mailto:stepharo at free.fr>>:
> Hi federico
> 
> in which version because we cleaned a lot of bad code in nautilus in 5.0 alpha
> 
> 
> Le 6/10/15 01:10, Federico.Balaguer a écrit :
> 
> Hello,
> 
> I found a problem when evaluating something like:
> 
> Nautilus openOnClass: Object
> 
> The result is a new Nautilus on Object but the package tree list is empty
> and a debugger pops up with a back trace with this:
> NautilusUI(Object)>>doesNotUnderstand: #useLastPackagePatternStringForClass:
> Nautilus class>>openOnClass:inEnvironment:
> Nautilus class>>openOnClass:
> 
> is there other way to open Nautilus programatically.
> 
> Thanks!! Federico
> 
> 
> 
> And is it important whether Nautilus opens or any other installed browser?
> You can programatically open the browser with
> 
> Object browse.

Or 

Smalltalk tools browser fullOnClass: Object

The reason is that it is actually PackageTreeNautilus that is used…
Yes, in need to be cleaned up. We did already a huge step in Pharo5.

If someone wants to do a minimal fix for Pharo4, this would be nice…

	Marcus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20151006/e4e67c81/attachment.html>


More information about the Pharo-users mailing list