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

Re: [Pharo-dev] Help needed with case 19236

by Denis Kudriashov

2016-11-02 20:03 GMT+01:00 stepharo <stepharo(a)free.fr>: > But it leads to incompatibility for old images. > > If people use Spec and we update spec = no problem :) Yes Spec is updated by this. And now it is fix to include

Nov. 3, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60276 Home: https://github.com/pharo-project/pharo-core

Nov. 3, 2016

[pharo-project/pharo-core] ee46f2: 60276

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ee46f25acb523db0d525ba3c4385725428b227ee https://github.com/pharo-project/pharo-core/commit/ee46f25acb523db0d525ba3c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-11-03 (Thu, 03 Nov 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version425_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version426_.st A Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/as yet unclassified/handleKeyStroke_.st R Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/event handling/handlesKeyStroke_.st R Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/event handling/keyStroke_.st M Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/initialization/initialize.st A Kernel-Tests.package/BehaviorTest.class/instance/as yet unclassified/testIsRootInEnvironment.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60275.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60276.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60275.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60276.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tests.package/TraitTest.class/instance/testing/testIsRootInEnvironment.st M Tool-Catalog.package/CatalogBrowser.class/instance/Nautilus groups support/installAndCreateGroupButton_.st M Tool-Catalog.package/CatalogBrowser.class/instance/building/refreshButton_.st M Tool-Catalog.package/CatalogBrowser.class/instance/menu/defineAllRepositoriesInMCBrowserButton_.st M Tool-Catalog.package/CatalogBrowser.class/instance/menu/defineCurrentVersionRepositoryButton_.st M Tool-Catalog.package/CatalogBrowser.class/instance/menu/installStableVersionButton_.st M Tool-Catalog.package/CatalogBrowser.class/instance/menu/loadConfigurationButton_.st M Tool-Catalog.package/CatalogBrowser.class/instance/private - utilities/buildMenuOn_.st A Traits.package/TBehavior.class/instance/testing class hierarchy/isRootInEnvironment.st Log Message: ----------- 60276 19273 Icons of Catalog are not sorted by function https://pharo.fogbugz.com/f/cases/19273 19270 Fix broken keyboard navigation https://pharo.fogbugz.com/f/cases/19270 19246 New method to detect if class is root in own environment https://pharo.fogbugz.com/f/cases/19246 http://files.pharo.org/image/60/60276.zip

Nov. 3, 2016

Re: [Pharo-dev] Help needed with case 19236

by Dimitris Chloupis

well Tab is a terrible name for a class anyway. Says nothing about the class itself.

Nov. 2, 2016

Re: [Pharo-dev] Help needed with case 19236

by Nicolas Cellier

2016-11-02 20:03 GMT+01:00 stepharo <stepharo(a)free.fr>: > > Hi all. > > We need help how to better manage issue 19236 > <https://pharo.fogbugz.com/f/cases/19236/Append-Morph-to-Tab-widgets-classes…> > . > > Generally: we have class Tab which is morph related to tabs widget. It > conflicts with key mapping class variable and some similar stuff from > Xtreams. > > So this issue made rename of morph classes from tabs widget to add them > ~Morph suffix. > I think it is good change. > > > +1 > > But it leads to incompatibility for old images. > > If people use Spec and we update spec = no problem :) > > So any tools which use tabs will be not working in Pharo6. > > How to better manage this problem? Could we integrate this change? > > > Class renaming without keeping the old name is difficult. > What we did with gustavos was more for deprecating. > > stef > Undeclared at: #Tab put: TabMorph ? Just for a transition period...

Nov. 2, 2016

Re: [Pharo-dev] Help needed with case 19236

by stepharo

> Hi all. > > We need help how to better manage issue 19236 > <https://pharo.fogbugz.com/f/cases/19236/Append-Morph-to-Tab-widgets-classes…>. > > Generally: we have class Tab which is morph related to tabs widget. It > conflicts with key mapping class variable and some similar stuff from > Xtreams. > > So this issue made rename of morph classes from tabs widget to add > them ~Morph suffix. > I think it is good change. +1 > But it leads to incompatibility for old images. If people use Spec and we update spec = no problem :) > So any tools which use tabs will be not working in Pharo6. > > How to better manage this problem? Could we integrate this change? Class renaming without keeping the old name is difficult. What we did with gustavos was more for deprecating. stef

Nov. 2, 2016

Re: [Pharo-dev] roundTo: strange behavior

by Nicolas Cellier

Last thing, I'm not sure it's a good idea to deprecate round: round: has been added to overcome the rounding problems of roundTo: If we deprecate round:, then users will fallback to roundTo: and won't get correctly rounded Floats... Thus my original question: why is there a round in python, ruby etc... There must be other applications than just printing (we said financial is one). 2016-11-02 14:40 GMT+01:00 werner kassens <wkassens(a)libello.com>: > yes Martin, i get that point and i already reacted to it, i occasionally > want to calculate something with a rounded float, not print it: apart from > my harley i normally use _metric screws which come in decimal steps. > <friendly grin> let's end that discussion, we are going around in circles. > werner > > > On 11/02/2016 02:48 AM, Martin McClure wrote: > >> Hi Werner, >> Thanks for your comments. I posted the analysis because I did the >> analysis (and thought some others might want to see it), and I did the >> analysis because I wanted to find out whether that answer was right. >> Some Smalltalks are pretty bad in similar areas of Float handling. >> >> >> But aside from all the fine points, if you want a floating-point number >> to "look" nice and human-readable, >> (x asFraction roundTo:(1/10))asFloat >> will work, but I still recommend not rounding the number itself, but >> rounding the printing of the number. This is not a Pharo thing, it's an >> any-language-with-floats thing. In C you have printf, etc. In Pharo, you >> can use for instance: >> >> 1.19 printShowingDecimalPlaces: 1 ==> '1.2' >> >> This makes it easier for someone reading the code to see the intent. >> >> Regards, >> >> -Martin >> >> >> > >

Nov. 2, 2016

Re: [Pharo-dev] roundTo: strange behavior

by werner kassens

yes Martin, i get that point and i already reacted to it, i occasionally want to calculate something with a rounded float, not print it: apart from my harley i normally use _metric screws which come in decimal steps. <friendly grin> let's end that discussion, we are going around in circles. werner On 11/02/2016 02:48 AM, Martin McClure wrote: > Hi Werner, > Thanks for your comments. I posted the analysis because I did the > analysis (and thought some others might want to see it), and I did the > analysis because I wanted to find out whether that answer was right. > Some Smalltalks are pretty bad in similar areas of Float handling. > > > But aside from all the fine points, if you want a floating-point number > to "look" nice and human-readable, > (x asFraction roundTo:(1/10))asFloat > will work, but I still recommend not rounding the number itself, but > rounding the printing of the number. This is not a Pharo thing, it's an > any-language-with-floats thing. In C you have printf, etc. In Pharo, you > can use for instance: > > 1.19 printShowingDecimalPlaces: 1 ==> '1.2' > > This makes it easier for someone reading the code to see the intent. > > Regards, > > -Martin > >

Nov. 2, 2016

Help needed with case 19236

by Denis Kudriashov

Hi all. We need help how to better manage issue 19236 <https://pharo.fogbugz.com/f/cases/19236/Append-Morph-to-Tab-widgets-classes…> . Generally: we have class Tab which is morph related to tabs widget. It conflicts with key mapping class variable and some similar stuff from Xtreams. So this issue made rename of morph classes from tabs widget to add them ~Morph suffix. I think it is good change. But it leads to incompatibility for old images. So any tools which use tabs will be not working in Pharo6. How to better manage this problem? Could we integrate this change?

Nov. 2, 2016

[IMPORTANT] Code freeze for Pharo 6 starts YESTERDAY

by Esteban Lorenzano

Hi guys, As announced last week with the mail about our super-duper plans for Pharo 7, yesterday we entered code freeze. That means: - Just bugfixes - Just 64bits vm to be finished - Just Clementâs changes to be activated. FAQ: - Can my cool new framework enter the image now? NO! - Can my API changing SLICE be submitted now? NO! - Can I submit a bugfix, and stabilisation fix and a small UI improvement fix - YES! cheers, Esteban

Nov. 2, 2016