March 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Calypso: how to see two different methods (without diff) side by side?

by Stephane Ducasse

super! On Tue, Mar 27, 2018 at 11:12 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi Stef. > > I found very simple way how to support it. So maybe next release if there > will be time. > > Best regards, > Denis > > 2018-03-27 21:15 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Hi denis >> >> I do not really use a method diff but I would love to be able to see >> two methods >> side by side. >> >> Stef >> >

March 31, 2018

Re: [Pharo-dev] Why calypso inverse the hierarchy?

by Stephane Ducasse

Hi denis having the selected class or the hiearchy in the other way is both ok for me. On Tue, Mar 27, 2018 at 11:44 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi Stef > > 2018-03-27 23:11 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Hi denis >> >> Calypso asked me where I want to install a method. > > > Normally this dialog appears when you edit a method which class is not > selected in the browser. > For example if you enable superclass method visibility and edit one of > inherited methods. > But give me your scenario. > >> >> And I do not really appreciate that I get the inheritance tree reserved. > > > There is setting for this. And I am not against to change default value or > hardcode this part. > > Originally it was simple list with selected class at the bottom. Then there > was issue The currently edited class should be the first option when > overriding methods. > Idea that first item should be the most common case which is selected class. > At the end I realized that I can easily show hierarchy which I though is > better than simple list. And I reused existing hierarchy from method > visibility list. > > So there are two points for this dialog: > - do we want selected class to be first? > - do we want hierarchical view? > > Best regards, > Denis > >> To me it will destroy students. >> On my own code which is super stupid I had to think twice. I cannot >> image students. >> >> Then when working on code that is not ours it is be super difficult to >> understand anything. >> >> How can I set that superclass should be higher than subclasses? >> >> Stef > >

March 31, 2018

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC

by Stephane Ducasse

> I will try to promote then the one of 15 march. Weâll see next week. > but then, this is part of my observation: We cannot know which VMs are > stable, and thatâs because the *process* to make them stable is very âhuman > dependentâ: We consider a version stable when it builds on CI and Eliot says > is stable. But since Eliot does not use Pharo (not a critic, a reality), > that may be not true for Pharo. And thatâs actually what happens, Pharo > crashes. Hi esteban What would be a way to fix the process and make your work easier? If you do not know what can be a release candidate then who can? We should really improve this situation. Stef > I tried to avoid a bit this problem with our fork and nightly builds that > runs the pharo tests (to knew about problems as early as possible). But to > be honest I didnât have the time (and the will) to work on it recently, then > pharo fork is in practice stalled. I will revive that eventuallyâ¦ but just > when I find the time and the spirit to do it. > > > to one more up to date than 2017 08 27 (in fact more up-to-date than > opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 > 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result > in image corruption in large images, and can occur (as it has here) at > start-up, causing one's work to be irretrievably lost. > > > Most, if not all, the VMs between 1 Jan and 15 Mar have bugs that are > triggered either by the automated test suite or the bootstrap process. > > > The blocks I can see at the moment are: > > - Multiple builds have failed with an internal compiler error on the > sista builds. > -- The earliest occurrence I could find was commit 1f0a7da, but it may > have been earlier. > - Even if the Mac builds show success in travis, they aren't making it > on to files.pharo.org. > > > latest VM copied into files.pharo.org is 16/03. > we need to see whatâs happening there. > > -- I haven't ever worked with this code. > > Not directly related, but: > - Bintray hasn't been updated since 8 March 2018. > > > I think it could also be useful for files.pharo.org to have release > candidate links available, which would help people to focus testing on > a particular VM. They would need to be manually maintained, but I > think the benefits would be worthwhile. > > > all VMs are available to test. > justâ¦ not available *directly* to general users. > nowâ¦ I could have a 70rc link in vm subdir. But since I cannot know which VM > is RC I find it pointless at this moment. > > cheers, > Esteban > > > > Cheers, > Alistair > >

March 31, 2018

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC

by Esteban Lorenzano

Hi, > On 31 Mar 2018, at 11:45, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > On 23 March 2018 at 21:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Pharo urgently needs to upgrade the VM > > I couldn't agree more, and I know Esteban wants to release a new VM. > I did quite a bit of testing on a VM from 15 March that I thought > would make a good candidate before realising that the Mac VMs aren't > available. I will try to promote then the one of 15 march. Weâll see next week. but then, this is part of my observation: We cannot know which VMs are stable, and thatâs because the *process* to make them stable is very âhuman dependentâ: We consider a version stable when it builds on CI and Eliot says is stable. But since Eliot does not use Pharo (not a critic, a reality), that may be not true for Pharo. And thatâs actually what happens, Pharo crashes. I tried to avoid a bit this problem with our fork and nightly builds that runs the pharo tests (to knew about problems as early as possible). But to be honest I didnât have the time (and the will) to work on it recently, then pharo fork is in practice stalled. I will revive that eventuallyâ¦ but just when I find the time and the spirit to do it. > >> to one more up to date than 2017 08 27 (in fact more up-to-date than opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image corruption in large images, and can occur (as it has here) at start-up, causing one's work to be irretrievably lost. > > Most, if not all, the VMs between 1 Jan and 15 Mar have bugs that are > triggered either by the automated test suite or the bootstrap process. > > > The blocks I can see at the moment are: > > - Multiple builds have failed with an internal compiler error on the > sista builds. > -- The earliest occurrence I could find was commit 1f0a7da, but it may > have been earlier. > - Even if the Mac builds show success in travis, they aren't making it > on to files.pharo.org. latest VM copied into files.pharo.org <http://files.pharo.org/> is 16/03. we need to see whatâs happening there. > -- I haven't ever worked with this code. > > Not directly related, but: > - Bintray hasn't been updated since 8 March 2018. > > > I think it could also be useful for files.pharo.org to have release > candidate links available, which would help people to focus testing on > a particular VM. They would need to be manually maintained, but I > think the benefits would be worthwhile. all VMs are available to test. justâ¦ not available *directly* to general users. nowâ¦ I could have a 70rc link in vm subdir. But since I cannot know which VM is RC I find it pointless at this moment. cheers, Esteban > > Cheers, > Alistair

March 31, 2018

[Pharo 7.0-dev] Build #747: 21668-Mark-deprecated-classes-as-deprecated

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #747 was: SUCCESS. The Pull Request #1169 was integrated: "21668-Mark-deprecated-classes-as-deprecated" Pull request url: https://github.com/pharo-project/pharo/pull/1169 Issue Url: https://pharo.fogbugz.com/f/cases/21668 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 31, 2018

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-03-19

by Juraj Kubelka

Hi Pavel, > On Mar 26, 2018, at 10:37, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > > Then I started to work on the changes metamodel for Ring with the goal > to be able to record, reproduce and revert (almost) all changes that > the user does in the model. The main goal of it is to be able to get > comparisons of two models and compute loading order of the changes so > it will be more easy to replace the Monticello metamodel and the > metamodel for code differences with a single solid solution based on > Ring. I am interested in playing with the recording-reproduce-and-revert feature. Is it possible? How do you compare it with Epicea? May your work replace Epicea (or part of it) or is it different? Cheers, Juraj

March 31, 2018

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC

by Alistair Grant

On 23 March 2018 at 21:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Pharo urgently needs to upgrade the VM I couldn't agree more, and I know Esteban wants to release a new VM. I did quite a bit of testing on a VM from 15 March that I thought would make a good candidate before realising that the Mac VMs aren't available. > to one more up to date than 2017 08 27 (in fact more up-to-date than opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image corruption in large images, and can occur (as it has here) at start-up, causing one's work to be irretrievably lost. Most, if not all, the VMs between 1 Jan and 15 Mar have bugs that are triggered either by the automated test suite or the bootstrap process. The blocks I can see at the moment are: - Multiple builds have failed with an internal compiler error on the sista builds. -- The earliest occurrence I could find was commit 1f0a7da, but it may have been earlier. - Even if the Mac builds show success in travis, they aren't making it on to files.pharo.org. -- I haven't ever worked with this code. Not directly related, but: - Bintray hasn't been updated since 8 March 2018. I think it could also be useful for files.pharo.org to have release candidate links available, which would help people to focus testing on a particular VM. They would need to be manually maintained, but I think the benefits would be worthwhile. Cheers, Alistair

March 31, 2018

Re: [Pharo-dev] Why is FileSystem's Path class private ?

by Stephane Ducasse

> The comment in Path does say: "Normally users should not use me > directly." > > So there is an out :-) I think the comment is correct though - in most > cases the user should be dealing with FileReferences and not Paths. > I guess that I wrote it when I started to write comment on this library. But it can be totally wrong. Stef

March 31, 2018

Re: [Pharo-dev] Migrator: to help you migrating to latest version of Pharo :)

by Stephane Ducasse

Hi hilaire Here the migration is even better because when a method is deprecated (when possible) it is automatically transformed. Now about LayoutFrame (it was a pain to do - we did around 260 changes and still) I could not express a nice transformation because this is mapping a given a point coordinate inside a rectangle to a given instance variables. What I did was to change the printOn: of layout frame to use the new and correct api so that I could check everything manually. As time allows I will crawl in Pharo 50, 40.... On Sat, Mar 31, 2018 at 9:46 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > This is really helpful. I remember when migrating from Pharo2 (or 1?) to > Pharo it helped a lot. > > Regarding migration to P7/P6 from P3, the most challenging part was the API > change in the LayoutFrame, it used a lot the layout of the DrGeo GUI. > > Btw, can someone with a Mac OS X 10.12.3, test if the bellow package[1] work > ?I don't have access to Mac now, the school is closed for holiday. > > Thanks > > Hilaire > > [1] https://www.dropbox.com/s/oe7hvdrmz7mstvx/DrGeo-Pharo4.0.app.zip?dl=0 > > > > Le 30/03/2018 Ã 22:30, Stephane Ducasse a Ã©crit : >> >> Today during the Pharo sprint I went over all the deprecated methods >> in Pharo 70 and Pharo 60 and I checked if I could convert the >> deprecated ones into deprecated:transformWith: so that the conversion >> is done automatically to help people migrating from one version to the >> other. >> >> I also collected all the deprecated methods as well as the new >> deprecated:transformWith: methods into a Package called Migrator >> (should still merge the Pharo 60 and Pharo 70 version). >> >> I plan to do the same for Pharo 50, 40, 30, 20. If you want to help feel >> free. >> >> At the end we will have one package containing all the deprecated >> methods of all the past versions. The way we will be able to support a >> smoother conversion to more recent version. > > > -- > Dr. Geo > http://drgeo.eu > > >

March 31, 2018

Re: [Pharo-dev] Migrator: to help you migrating to latest version of Pharo :)

by Stephane Ducasse

Sorry guy I'm not santa klaus. I just do a little thing at a time. On Sat, Mar 31, 2018 at 1:00 AM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > On 30/03/2018 22:30, Stephane Ducasse wrote: >> Hi >> >> Today during the Pharo sprint I went over all the deprecated methods >> in Pharo 70 and Pharo 60 and I checked if I could convert the >> deprecated ones into deprecated:transformWith: so that the conversion >> is done automatically to help people migrating from one version to the >> other. >> >> I also collected all the deprecated methods as well as the new >> deprecated:transformWith: methods into a Package called Migrator >> (should still merge the Pharo 60 and Pharo 70 version). >> >> I plan to do the same for Pharo 50, 40, 30, 20. If you want to help feel free. >> >> At the end we will have one package containing all the deprecated >> methods of all the past versions. The way we will be able to support a >> smoother conversion to more recent version. >> >> >> Stef >> > > This is cool! > > Maybe this package can also contains help topics explaining some bigger > changes. It could contains for example the explanations of Guille and > Sven about the new file streams? > > Also this package can be mentioned in the Welcome window of Pharo 7 I think. > > -- > Cyril Ferlicot > https://ferlicot.fr >

March 31, 2018