Name: GT-Debugger-StephaneDucasse.200
Author: StephaneDucasse
Time: 26 June 2014, 9:10:31.768055 am
UUID: 4e20dcfb-724e-4293-a6dd-4452bf73b3c4
Ancestors: GT-Debugger-TudorGirba.199
remove register assubclassresponsibility because it breaks completely
the toolRegistry.
Hi guys
Can we get playground not hidding the old workspace?
The textselection is awfull.
Why do we sacrifice what is working in Pharo?
Some keybindings are not working,
registerToolsOn: registry
"Add ourselves to registry. See [Smalltalk tools]"
"self registerToolsOn: Smalltalk tools"
registry register: self as: #playground
SmalltalkImage current resetTools is broken on Moose :(
Great!
Workspace registerToolsOn: SmalltalkImage current tools
Then why the theme does not support correctly the display of incomplete class names and selector?
I will really consider to ask the rmod team to make its own Moose build with decent default
because this is each time the same story instead of having the time to fix a problem (snapshotcello is not working with latest moose
then I lose times to fix the system to work as good as the default pharo).
Stef
In Pharo 30 it is fully working. In Moose well you can trash your image.
So to get a chance to be productive in moose we have a special quizz to
solve first.
Stef
So I'm trying to unload GT-Playground from moose and
I love it
SmalltalkImage current resetTools freezes my image.
And after you want that people like Igor spend time fixing problems in
the Moose image.....
In fact
SmalltalkImage current resetTools freezes my image even without
underloading GT-Playground.
I think that Moose is decaying sadly.
How can I get the old debugger interface? Because I go much faster with it?
Stef
Hi guys
Can we get playground not hidding the old workspace?
The textselection is awfull.
Why do we sacrifice what is working in Pharo?
Some keybindings are not working,
registerToolsOn: registry
"Add ourselves to registry. See [Smalltalk tools]"
"self registerToolsOn: Smalltalk tools"
registry register: self as: #playground
SmalltalkImage current resetTools is broken on Moose :(
Great!
Then why the syntax highlithging does not support correctly the display
of incomplete class names and selector?
I will really consider to ask the rmod team to make its own Moose build
with decent default
because this is each time the same story instead of having the time to
fix a problem (snapshotcello is not working with latest moose
then I lose times to fix the system to work as good as the default pharo).
Stef
Hi,
I have regularly a problem when exploring things in debugger/inspector. It raise an error. Here is the captured video: https://dl.dropboxusercontent.com/u/710942/pharo/moose-debugger-error.mov
It says errorSubscriptBounds: for MethodContext>>tempAt:
Is it known error? Can I avoid it?
Thanks,
Juraj
