- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bug in protocol and method selection

by Yuriy Tymchuk

Stef, I cannot see the issue, moreover there were no changes in QA that touch Nautilus. Maybe this is because of FastTable highlighting: when you hover over a selected list item, it changes color to the hover color, so when you select an item you cannot see the you selected it because you see the tower color. This was already fixed, but not yes integrated. Uko > On 14 Jan 2016, at 13:33, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > I will take a look. Just to make sure: this is not the FT coloring thing, right? > > Uko > >> On 14 Jan 2016, at 13:06, stepharo <stepharo(a)free.fr> wrote: >> >> Hi >> >> There is a problem in latest Pharo. I cannot select (and keep the selection selected) >> of a method and method protocol. >> To me it looks like QA is interferring but I do not know. >> This is the kind of glitches that can kill our effort doing videos. We have a strong deadline >> for producing such videos. beginning of march but we want to get done before >> any help is welcome. >> >> Stef >> > >

Jan. 14, 2016

Re: [Pharo-dev] Bad layoutFrame>>#hash

by David Allouche

> On 14 Jan 2016, at 13:31, David Allouche <david(a)allouche.net> wrote: > >> >> On 14 Jan 2016, at 01:55, Ben Coman <btc(a)openinworld.com> wrote: >> >> On Thu, Jan 14, 2016 at 5:45 AM, David Allouche <david(a)allouche.net> wrote: >>> >>>> On 13 Jan 2016, at 20:32, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> Hi david >>>> >>>> I would like to turn your post into a chapter for a forthcoming book so that people can read and get the idea. >>> >>> Yes I would be glad :-) Please just remember to credit the author. >>> >>> Is there a recommended license for Pharo documentation? If not, I am happy to release that text under the MIT License. >>> >>> I would also like to review your derived work. But that is not a requirement. >>> >>>> I did not think about the same object. Is it ok for you? >>>> >>>> Stef >>>> >>>> PS: May be this was obvious for you that we should all get this out of your previous mail but it was not my case >>>> and not after 8 hours on intense work. >>> >>> Sorry, I do not understand what you are saying here. I do not want to read between the lines, because I would probably misunderstand your intention. >>> >>> Regards. >> >> I hope its okay if I jump in and read between the lines when I see to >> two French people trying to sort out the subtle meanings of english >> over email. >> >> On any given day anyone can be overworked/stressed/worn out, and they >> don't have much time to reason deeply on things. I read "obvious" as >> an acknowledgement that there was further implicit background >> knowledge you likely had to "apply" the info from wikipedia. I notice >> lately Stef's posts have been much shorter than usual, even terse - >> from which I infer he is flat out. I think Stef's english suffers >> when he is in a hurry - only a tiny bit, but email amplifies this. >> >> Don't worry David. When our fiery Stef is upset at you, you won't miss it ;) > > Thank you for the reassurance. > > But that was fine. Stubbing some toes on the rougher personalities in a community, that is part of the process of figuring out the social context of any project :-) > > In any case, his initial reaction did prompt me to include a couple of passive aggressive sentence in my reply. I did remove some :-) but temptation was too strong and I left some in. And he picked them up. Combative temperament. > > When you say "upset", you mean like in the thread that announced the integration of GTDebugger, or was that an example of his baseline? That's an honest question... Hm. Oops. That was not supposed to go to the mailing list. :-( I hope that will not upset Stef too much ;-)

Jan. 14, 2016

Re: [Pharo-dev] Bug in protocol and method selection

by Yuriy Tymchuk

I will take a look. Just to make sure: this is not the FT coloring thing, right? Uko > On 14 Jan 2016, at 13:06, stepharo <stepharo(a)free.fr> wrote: > > Hi > > There is a problem in latest Pharo. I cannot select (and keep the selection selected) > of a method and method protocol. > To me it looks like QA is interferring but I do not know. > This is the kind of glitches that can kill our effort doing videos. We have a strong deadline > for producing such videos. beginning of march but we want to get done before > any help is welcome. > > Stef >

Jan. 14, 2016

Re: [Pharo-dev] Bad layoutFrame>>#hash

by David Allouche

> On 14 Jan 2016, at 01:55, Ben Coman <btc(a)openinworld.com> wrote: > > On Thu, Jan 14, 2016 at 5:45 AM, David Allouche <david(a)allouche.net> wrote: >> >>> On 13 Jan 2016, at 20:32, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi david >>> >>> I would like to turn your post into a chapter for a forthcoming book so that people can read and get the idea. >> >> Yes I would be glad :-) Please just remember to credit the author. >> >> Is there a recommended license for Pharo documentation? If not, I am happy to release that text under the MIT License. >> >> I would also like to review your derived work. But that is not a requirement. >> >>> I did not think about the same object. Is it ok for you? >>> >>> Stef >>> >>> PS: May be this was obvious for you that we should all get this out of your previous mail but it was not my case >>> and not after 8 hours on intense work. >> >> Sorry, I do not understand what you are saying here. I do not want to read between the lines, because I would probably misunderstand your intention. >> >> Regards. > > I hope its okay if I jump in and read between the lines when I see to > two French people trying to sort out the subtle meanings of english > over email. > > On any given day anyone can be overworked/stressed/worn out, and they > don't have much time to reason deeply on things. I read "obvious" as > an acknowledgement that there was further implicit background > knowledge you likely had to "apply" the info from wikipedia. I notice > lately Stef's posts have been much shorter than usual, even terse - > from which I infer he is flat out. I think Stef's english suffers > when he is in a hurry - only a tiny bit, but email amplifies this. > > Don't worry David. When our fiery Stef is upset at you, you won't miss it ;) Thank you for the reassurance. But that was fine. Stubbing some toes on the rougher personalities in a community, that is part of the process of figuring out the social context of any project :-) In any case, his initial reaction did prompt me to include a couple of passive aggressive sentence in my reply. I did remove some :-) but temptation was too strong and I left some in. And he picked them up. Combative temperament. When you say "upset", you mean like in the thread that announced the integration of GTDebugger, or was that an example of his baseline? That's an honest question...

Jan. 14, 2016

Bug in protocol and method selection

by stepharo

Hi There is a problem in latest Pharo. I cannot select (and keep the selection selected) of a method and method protocol. To me it looks like QA is interferring but I do not know. This is the kind of glitches that can kill our effort doing videos. We have a strong deadline for producing such videos. beginning of march but we want to get done before any help is welcome. Stef

Jan. 14, 2016

Re: [Pharo-dev] Menus are broken in diff tools pane

by Nicolai Hess

menus are broken almost everywhere: I thnk, responsible for these issues are only two changes for Rubric and the Suggestions-Menu http://forum.world.st/fixing-our-tools-tp4864859.html 2016-01-14 12:54 GMT+01:00 stepharo <stepharo(a)free.fr>: > > >

Jan. 14, 2016

Re: [Pharo-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

by Andrei Chis

Hi Nicolai, Thanks for reporting these issues. They are indeed bugs and we are working on fixing them. Cheers, Andrei On Tue, Jan 12, 2016 at 11:24 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-01-08 11:24 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi, >> >> We are about to integrate in Pharo a new member of the Glamorous Toolkit: >> the GTDebugger. As this is a significant change that might affect your >> workflow, here is some background information to help you deal with the >> change. >> >> First, you should know that the change is not irreversible and it is >> easily possible to disabled the new debugger through a setting. However, >> please do take the time to provide us feedback if something does not work >> out for you. We want to know what can be improved and we try to react as >> fast as we can. >> >> A practical change comes from the fact that the variables are manipulated >> through a GTInspector, which makes it cheaper to maintain in the longer run. >> > > Accept and Cancel buttons shouldn't be there > or should not act on if the codepane hasn't changed. > (every press on "accept" writes a new method version, although the > contents didn't changed - tested on > Latest update: #50524 ) > > Most (all?) other tools don't have Accept/Cancel buttons. > > - I really miss the "List Methods using 'varname'/List Methods storing > into 'varname' > - is "stackTop" now gone ? I thought you wanted to add it to the stack ? > - thisContext is gone as well ? > - the Bytecode/GT button is badly placed, it looks like the "downarrow" > window menu icon > is a dropdown menu with label "Bytecode" (since when do we put buttons > in the title pane? > - the evaluator pane is shown as "dirty", as it does not make a difference > if we > accept the text in this pane, there shouldn't be a dirty indicator. > - you can not use the inspector pane to change inst var values > - there is no way to refresh the inspector pane > > I don't open bugtracker entries now, I 'll wait maybe this issues aren't > bugs but > features. > > > nicolai > > >

Jan. 14, 2016

Re: [Pharo-dev] PluggableButtonMorph does not respect font size :(

by stepharo

Thanks nicolai I changed the font right now. I will check because after we will do around 20 videos showing pharo tools. Le 14/1/16 11:33, Nicolai Hess a Ã©crit : > > > 2016-01-14 11:19 GMT+01:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > For the Pharo Mooc we need to use large font and we end up with > this visual glitch :( > I tried to dive into PluggableButtonMorph and I failed to found > how to make sure it computes the bound correctly. > Any help is welcome. > > > > I think this issue is related: > 13376 > <https://pharo.fogbugz.com/f/cases/13376/Wrong-TextMorph-extent-for-ButtonMo…> > Wrong TextMorph extent for ButtonMorphs > The problem: > UITheme buttonLabelFor: creates a TextMorph with an extent > computed by TextMorph>>optimalExtent (in buttonLabelForText:), > which relies on its TextStyle (from the default font). > After that, the TextMorphs font is changed to the buttons > default font: > > > > label :=selfbuttonLabelForText:aButton label. label enabled:aButton > enabled. label font:selfbuttonFont. > > > but the "label font:" does not recomputed the extent. > > > > I really think that in Brick we should really be picky on such > problems. > > Stef > > >

Jan. 14, 2016

Re: [Pharo-dev] Add a package to Manifest?

by stepharo

Sure! Le 14/1/16 12:03, Yuriy Tymchuk a Ã©crit : > Hi, > > is it possible to add a package into CodeCritics manifest? > > > Cheers. > Uko > >

Jan. 14, 2016

Menus are broken in diff tools pane

by stepharo

Jan. 14, 2016