BTW when we debugged the font problems with igor, we were really frustrated because the debugger
did not let us restart methods (they was no fly by help, no menus….) then we dod not know how in some cases we could get
another debugger with more items (no ideas why) and we got some problem with keybinding in the workspace.
We open an old workspace to be able to work!!!
So of course we can think that igor and me are just two little idiots not understanding what we were doing.
I do not think you are idiots, but if you cannot say what problems you had it's hard to address them.
You know if a guy like igor (with me pair programming) cannot find a restart in a debugger may be this is that it was not there.For example, you say that there were no tooltips, but all actions have tooltips that behave exactly like any other tooltip in Pharo. If they did not appear you might have run into a Pharo bug, but I doubt it.
I mean getting what we have now. and a menus with the action we have nowWhat do you mean by more items? More actions/icons? Or? What were you debugging?
You know very well that these tools are not the ultimate tools. They are built by people that typically have other things to do, too. But, I think everyone is ready to listen to things and see how to improve. Let's just keep on being concrete.
Now do not expect that people like Igor will spend their time fixing Moose problems (because this was a problem of Moose -
adding fonts without adding them to the crappy ad-hoc registration mechanism was a Moose problem).
Thanks for looking into it, but Moose did not really have a problem with this issue. I did not encounter even one case in which I had to change the fonts after they were set in the setup (the Moose image comes with this setup already done). It's good that now we have a basic in-image font registration mechanism, though.
Because some of our potential clients got the big red cross on their screen and several times.Igor was nice to help me but do not cry in the future if people do not help because if the basic tools do not work well
why people should freely spent their time helping us. Igor did it because I was forced to do it and we did it together.
I thank Igor and you. But, I still do not understand why you were forced to do it?
Both.I was also frustrated because I also have something else to do than to fight with a debugger that did not have the default functionality. but icons do not work me.
You are mixing a bit things. We started from the theme, and now you talk about the debugger. Which one is the problem? Both? Equally?
Indeed.After that experience I was thinking that I should do a new jenkins job loading my version of Moose and do not say it around.
I would imagine that everybody at RMOD would suddenly use this version of Moose because many people are getting frustrated.
I did not want to start a war but I was ****REALLLLLYYYY**** frustrated. I could not see the input field, I could not get the workspace working
and the debugger was wrong. So yes we can say that nautilus is bad but I use it daily and I have no problem to know where to type.
Feel free to ignore this message, but when I will be really mad again I will create a jenkins job and only use this version. I fully understand
Yuriy’s idea to have less Moose! And I will ask the people that wants me to help to only use this version that I can use.
This is not really helpful, but the choice is yours :)
Good night,Doru
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev