That is the whole point of the GT: to replace the existing tools. The points you mention below are really tiny (at least from my point of view).

Ok so I will do a new version of Moose without it. This idea of not letting the choice to people is really bad but you will not change it so I will adapt myself and create something else. Because if I have to choose between tools where I'm efficient and experimental tools. I decided. I asked the questions but I knew your answers. You do not want to listen to people and I'm sad but I cannot do much.

I want to control the energy I spent and how I spend it. So now I know that I should invest in a Moose-less solution. I knew it before too but I was trying another time but I'm stupid to have thought that you could understand that other people can think differently.

The textselection is awfull.

It should not be. Besides the click-pause-click (instead of double-click) to select, is there anything else that is missing?

I cannot test it anymore because I do not have playground around in my image.

Why do we sacrifice what is working in Pharo?

We do not. But, please keep in mind that we are still developing it. 's just that we moved all tools to Rubric since recently because PluggableTextMorph cannot be used for future developments. And in the process, we are refactoring a bit Rubric to be more malleable and use keymapping and allow for more flexible syntax highlighting.

Good for you. But again you do not respect/listen people using Moose for real. Else you would behave differently. Now I do not accept that people cut my fingers when I need to type fast.

Some keybindings are not working

Which ones? I am working specifically on this since a week to get it to work properly on Windows as well.

No idea. I lost my text and realize that this not happening in default Pharo. I cannot stop to work find a complex bugs to think about all the glitches

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!

Sorry for that. I never used resetTools. We should add a test for this.

Btw, now that I look at resetTools, it does not even work properly even if you use it outside of Moose. The world menu is messed up. The Nautilus is the simpler one. Essentially, the outcome of using that one is kind of random (look at the implementation). So, it's good you bring it up because we should talk about it in the Pharo mailing list.

I fixed nautilus in Pharo too.

Workspace registerToolsOn: SmalltalkImage current tools

Yes. This is the way things are meant to be used, is it not? Why is this an issue?! You can just do this without the resetTools and it should work out of the box.

Then why the theme does not support correctly the display of
incomplete class names and selector?

It does! It shows them in gray. What is wrong there?

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).

I hope you don't. I believe that every time people had problems we could react quite fast and we focused on fixing the problems. Please keep the game fair.

Cheers, Doru

Stef
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com http://www.tudorgirba.com

"Every thing has its own flow"

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev