[Pharo-dev] [GTInspector] Showing object state using a tree

phil at highoctane.be phil at highoctane.be
Sat Aug 9 05:25:12 EDT 2014


Yes, I have a local little patch for that.

Maybe Dark was updated and Dawn has to follow.

Sebastian?

Phil


On Sat, Aug 9, 2014 at 10:01 AM, Johan Brichau <johan at inceptive.be> wrote:

> I just installed the Dark Theme with the GT Tools in a Pharo3 and they
> seem to work well now. Great great!
>
> The Dawn theme has difficult contrasts in other tools as well (even
> without GT installed). Try using the merge tool with it....
>
> Johan
>
> On 08 Aug 2014, at 13:02, phil at highoctane.be wrote:
>
> > It works.
> >
> > Now, following Johan point, the debugger is hard to read in a dark
> theme.  See attached screenshot.
> >
> > Phil
> >
> >
> >
> > On Fri, Aug 8, 2014 at 11:55 AM, Andrei Chis <chisvasileandrei at gmail.com>
> wrote:
> > Use GTGenericStackDebugger instead of GTDebugger. (it was renamed some
> time ago).
> >
> >
> > Cheers,
> > Andrei
> >
> >
> > On Fri, Aug 8, 2014 at 11:51 AM, phil at highoctane.be <phil at highoctane.be>
> wrote:
> > I have been trying to install the tools in Pharo 3 (Dark/Dawn Theme).
> >
> > GTInspector loads and works pretty ok at first sight.
> >
> > Gofer new
> >      url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main';
> >      configuration;
> >      load.
> > (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. "Works
> but with a warning"
> > (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools.
> "Ok"
> > (Smalltalk globals at: #GTDebugger) registerToolsOn: Smalltalk tools.
> "Gives: KeyNotFound: key #GTDebugger not found in SystemDictionary"
> >
> > Indeed there is no GTDebugger class but a set of other things.
> >
> > What to use ?
> >
> > TIA
> >
> >
> > ​Phil
> >
> >
> > <GT08-08-14 13-00-52.png>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20140809/23906340/attachment-0002.html>


More information about the Pharo-dev mailing list