Issue 1005 in moose-technology: GTInspector should become the main inspector

Status: New
Owner: ----
CC: [hidden email]
Labels: Type-Enhancement Priority-Medium Component-GlamorousToolkit  
Milestone-5.0

New issue 1005 by [hidden email]: GTInspector should become the main  
inspector
http://code.google.com/p/moose-technology/issues/detail?id=1005

Right now, we cannot install the GTInspector because the SpecDebugger from  
Pharo 3.0 depends on the inspector being implemented in Spec.

The issue is reported on the Pharo tracker:
https://pharo.fogbugz.com/f/cases/12055/The-Spec-Debugger-should-not-require-the-registered-inspector-to-be-built-on-Spec

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Status: Fixed

Comment #1 on issue 1005 by [hidden email]: GTInspector should become  
the main inspector
http://code.google.com/p/moose-technology/issues/detail?id=1005

The latest image now contains the GTInspector. To make this happen, Andrei  
made the GTDebugger to work and now it is installed in the image as the  
default debugger. We can rethink the situation once the SpecDebugger is  
back on track.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev