Moose-dev June 2014

moose-dev@list.inf.unibe.ch

38 participants
138 discussions

fixing Smalltalk resetTools!
by stepharo 26 Jun '14

26 Jun '14

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.

2 3

could the playground not override the old workspace?
by Stéphane Ducasse 26 Jun '14

26 Jun '14

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

4 3

can the admin remove my other accounts from the list?
by stepharo 26 Jun '14

26 Jun '14

2 2

How to kill moose in one liner: SmalltalkImage current resetTools
by stepharo 26 Jun '14

26 Jun '14

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

1 0

Unloading GT-Playground ...
by stepharo 26 Jun '14

26 Jun '14

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

1 0

test
by stepharo 26 Jun '14

26 Jun '14

2 1

Can we get playground not hidding the old workspace?
by stepharo 26 Jun '14

26 Jun '14

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

1 0

tyring to unload Playground breaks Moose :(
by Stéphane Ducasse 26 Jun '14

26 Jun '14

So now I’m stuck. I really start to hate this situation. Stef

1 0

Inti demo
by milton mamani 26 Jun '14

26 Jun '14

Hi, I've been working on Inti, you can watch a simple demo of this. https://vimeo.com/98760520 Best regards, Milton

3 5

Moose debugger/inspector error
by Juraj Kubelka 26 Jun '14

26 Jun '14

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

3 3

← Newer
1
...
6
7
8
9
10
11
12
13
14
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2014