January 2016 - Pharo-dev - lists.pharo.org

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

Add a package to Manifest?

by Yuriy Tymchuk

Hi, is it possible to add a package into CodeCritics manifest? Cheers. Uko

Jan. 14, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Stephan Eggermont

On 14-01-16 10:57, Blondeau Vincent wrote: > I just solved the bug that appears on Pharo 5, updated the configuration > and uploaded it to the catalogs. > > It should work now. Thanks Vincent. It would be better if the problem were fixed in ConfigurationOfXMLParser. It misses the #'pharo4.x' and #common parts (or possibly #'pharo5.x') and the #release based versioning is not up to date. I would expect to be able to depend on #'release-2' in ConfigurationOfPharoLauncher. I would expect #'release-2' to point to #'release-2.5' which would point to 2.5.6 for #'pharo4.x' and 2.5.7 for #'pharo5.x' The dependency on Ston, JSON and OSProcess would be safe to be on #stable Stephan

Jan. 14, 2016

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

by Nicolai Hess

2016-01-14 11:19 GMT+01:00 stepharo <stepharo(a)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 := self buttonLabelForText: aButton label. label enabled: aButton enabled. label font: self buttonFont. 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

PluggableButtonMorph does not respect font size :(

by stepharo

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 really think that in Brick we should really be picky on such problems. Stef

Jan. 14, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by stepharo

Thanks vincent!!! I will try later! Le 14/1/16 10:57, Blondeau Vincent a Ã©crit : > > I just solved the bug that appears on Pharo 5, updated the > configuration and uploaded it to the catalogs. > > It should work now. > > Vincent > > Ps: I was using a Pharo 4.0 image > > *De :*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part > de* stepharo > *EnvoyÃ© :* jeudi 14 janvier 2016 10:44 > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] How to get launcher launching Spur images? > > I got it. > I was trying to use Launcher in Pharo 50. > I do not why I was trying it. > Now it works in Pharo 40. > > Le 10/1/16 18:49, stepharo a Ã©crit : > > Hi > > I changed the setting to be the following but I cannot get a spur > image started on mac. > Does anybody succeed? > > Stef > > > > ------------------------------------------------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã > l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© > par le secret professionnel. Si vous recevez ce message par erreur, > merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. > L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la > responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu > de ce message. Bien que les meilleurs efforts soient faits pour > maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne > donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre > recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately and destroy > it. As its integrity cannot be secured on the Internet, the Worldline > liability cannot be triggered for the message content. Although the > sender endeavours to maintain a computer virus-free network, the > sender does not warrant that this transmission is virus-free and will > not be liable for any damages resulting from any virus transmitted.

Jan. 14, 2016