- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo 7.0.2 released!

by Esteban Lorenzano

> On 6 Mar 2019, at 12:38, Norbert Hartl <norbert(a)hartl.name> wrote: > > How wonderful is that? How much effort it was compared to the old process? zero. Bah, I needed to restart the CI because of the freetype random welcome problem. Esteban > > Norbert > > >> Am 06.03.2019 um 11:32 schrieb Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> >> Hi, >> >> I just made a bugfix release of Pharo: >> >> v7.0.2 <https://github.com/pharo-project/pharo/releases/tag/v7.0.2> >> <513630.jpeg> <https://github.com/estebanlm> estebanlm <https://github.com/estebanlm> released this 22 hours ago >> >> Bugfix release >> >> #2303 <https://github.com/pharo-project/pharo/issues/2303> Deprecation fixes in TEasilyThemed >> #2120 <https://github.com/pharo-project/pharo/pull/2120> Object-centric MetaLink integration >> #2376 <https://github.com/pharo-project/pharo/pull/2376> Ensure subMenu is opened (backport) >> #2428 <https://github.com/pharo-project/pharo/pull/2428> Add scrollSelectionIntoView >> #2700 <https://github.com/pharo-project/pharo/pull/2700> Tonel test is failing (backport) >> >> Enjoy :) >> >> Esteban >

March 6, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.2 released!

by Norbert Hartl

How wonderful is that? How much effort it was compared to the old process? Norbert > Am 06.03.2019 um 11:32 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > I just made a bugfix release of Pharo: > > v7.0.2 <https://github.com/pharo-project/pharo/releases/tag/v7.0.2> > <513630.jpeg> <https://github.com/estebanlm> estebanlm <https://github.com/estebanlm> released this 22 hours ago > > Bugfix release > > #2303 <https://github.com/pharo-project/pharo/issues/2303> Deprecation fixes in TEasilyThemed > #2120 <https://github.com/pharo-project/pharo/pull/2120> Object-centric MetaLink integration > #2376 <https://github.com/pharo-project/pharo/pull/2376> Ensure subMenu is opened (backport) > #2428 <https://github.com/pharo-project/pharo/pull/2428> Add scrollSelectionIntoView > #2700 <https://github.com/pharo-project/pharo/pull/2700> Tonel test is failing (backport) > > Enjoy :) > > Esteban

March 6, 2019

[ANN] Pharo 7.0.2 released!

by Esteban Lorenzano

Hi, I just made a bugfix release of Pharo: v7.0.2 <https://github.com/pharo-project/pharo/releases/tag/v7.0.2> <https://github.com/estebanlm> estebanlm <https://github.com/estebanlm> released this 22 hours ago Bugfix release #2303 <https://github.com/pharo-project/pharo/issues/2303> Deprecation fixes in TEasilyThemed #2120 <https://github.com/pharo-project/pharo/pull/2120> Object-centric MetaLink integration #2376 <https://github.com/pharo-project/pharo/pull/2376> Ensure subMenu is opened (backport) #2428 <https://github.com/pharo-project/pharo/pull/2428> Add scrollSelectionIntoView #2700 <https://github.com/pharo-project/pharo/pull/2700> Tonel test is failing (backport) Enjoy :) Esteban

March 6, 2019

[ANN] Pharo Consortium New Academic Member: CIRAD

by Marcus Denker

The Pharo Consortium is very happy to announce that CIRAD has joined the Consortium as an Academic Member. About - CIRAD, the French Agricultural Research Centre for International Development: https://www.cirad.fr/en/home-page - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

March 6, 2019

Final Reminder: Only 5 spots left for Camp Smalltalk! Raspberry PI kits to all who attend!

by Mariano Martinez Peck

Hello All, There are 5 slots left for Camp Smalltalk Charlotte 2019 taking place at the end of this month. Now is the time to sign up if you are thinking of attending (see bottom for registration link). Camp Smalltalk is about community engagement and collaboration. There are a number of fantastic talks already lined up such as: Developing Smalltalk solutions running directly on ios / android mobile platforms (along with tooling) Live demo of @1MB remote-debuggable smalltalk images controlling peripherals attached to a Raspberry PI (ARM) In-depth look at large scale use of CMake/CTest/CDash for use with Smalltalk systems Smalltalk dialect portability solutions for the Smalltalk community (for use with GIT) We also have a fantastic Saturday evening social dinner planned on the boardwalk near the hotel. *As a special gift to attendees*, Instantiations will be providing everyone with their own Raspberry PI Zero Wifi devices with 8GB mini-sd card and power supply. Raspbian Linux with VA Smalltalk for ARM will be pre-installed. And if that isn't enough, each attendee will be receiving an open-source license for VA Smalltalk. This event is happening *March 29th â March 31st 2019* in Charlotte, North Carolina. Event details and registration info are available at the following link: Camp Smalltalk Charlotte 2019 <https://www.eventbrite.com/e/camp-smalltalk-charlotte-2019-tickets-52380940…> Hope to see you there! [image: IMG_0912.jpg] -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

March 5, 2019

[Pharo 8.0] Build #114: 2736-Update-Epicea-to-Spec-changes

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

There is a new Pharo build available! The status of the build #114 was: SUCCESS. The Pull Request #2747 was integrated: "2736-Update-Epicea-to-Spec-changes" Pull request url: https://github.com/pharo-project/pharo/pull/2747 Issue Url: https://pharo.fogbugz.com/f/cases/2736 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 5, 2019

[Pharo 7.0] Build #152: 2699 - backport pharo-vcs/tonel bug fix

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

There is a new Pharo build available! The status of the build #152 was: SUCCESS. The Pull Request #2700 was integrated: "2699 - backport pharo-vcs/tonel bug fix" Pull request url: https://github.com/pharo-project/pharo/pull/2700 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 5, 2019

Re: [Pharo-dev] managing modification of class initialization methods

by Ben Coman

On Tue, 5 Mar 2019 at 22:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Now, your solution, the pragma, is just as complex, because it would still > require people to (1) understand the issue and (2) remember to add the > pragma correctly. > I agree those points apply in relation to creating code, but for an existing method with such a pragma I believe it would be reasonably easy for newcomers to read and understand the impact of modifying the data, but I've really nothing to back up that belief. cheers -ben

March 5, 2019

[Pharo 7.0] Build #151: 2699 - backport pharo-vcs/tonel bug fix

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

There is a new Pharo build available! The status of the build #151 was: SUCCESS. The Pull Request #2700 was integrated: "2699 - backport pharo-vcs/tonel bug fix" Pull request url: https://github.com/pharo-project/pharo/pull/2700 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 5, 2019

Re: [Pharo-dev] managing modification of class initialization methods

by Sven Van Caekenberghe

Tim, Your example is exactly the most common 'gotcha' case where something unexpected happens. In that case, when one of the underlying #massTable constants/specs changes, I would add a comment timestamp in the class #initialize method, something along the lines "last change: 20190305". You are right that this is a complex and not so obvious issue, both for newcomers as for others. The key cause of this is that we have a live image that lives longer that a classic program, people are not used to this. Class variables hold state, sometimes even complex databases. The decision to not always rerun all class #initialize methods is because sometimes these might hold expensive calculations, another reason might be that not all class #initialize methods can run in all circumstances (they might want to load external data, etc, ...). Now, your solution, the pragma, is just as complex, because it would still require people to (1) understand the issue and (2) remember to add the pragma correctly. If the dependency goes over different classes, with potentially unknown users, it might even be impossible to solve. Sven > On 5 Mar 2019, at 01:50, Tim Mackinnon <tim(a)testit.works> wrote: > > If we go back to where this comes from - I donât think its so obvious what the behaviour is. Newcomers to Smalltalk donât get it, and I suspect even seasoned Smalltalkers have to think twice or more about this. > > If we roll back to where I think this question came from: > > If I have a simple constant like #maxLimit - I can stick it as an instance method as: > > maxLimit > ^42 > > > But if my constant is more complicated like: > > massTable > | multiplier | > multipier := 4.25678. > > ^{ âaâ -> 27 * multiplier. > âbâ -> 42 * multiplier. > â¦ > âzâ -> 106 * multiplier } asDictionary > > It's not ideal to have this as an instance method - so you are advised to move it up to the class level, and try to emulate a âconstâ. > > But this still isnât good enough as its evaluated every time - so you add a class variable MassTable and initialize it once, in class>>initialize > > Initialise > > MassTable := self massTable. > > > Ok - so far so good - except you made a mistake and want to correct the value for âzâ, which you change from 106 to 110 and press save. > > But surprise, surprise, it doesnât change - because when is class #initialise actually called? Trick question it turns out - as if I make the change in GitHub, commit the code and then reload the package with iceberg - it still wonât change as reloading code doesnât cause class initialise (which is surprising to most). > > I think that this this quite common occurrence shouldnât be so mysterious - why canât I just change the code, save it and have the value change in some obvious manor without some voodoo. This is one of those strange cases of smalltalk where it doesnât obviously do what I expect and I need to know too much of the system to do the right thing. > > I think we could come up with a way to make this easier - but It would be good to get the wisdom of the crowd in on this. > > This is one of the early exercise in Exercism, and weâd like to know the best, element, in keeping with the philosophy solution. > > At the moment, a class variable with a lazy getter is the suggested solution e.g. > > massTable > âMyClass MassTable := nil. self massTable >>>â > > ^MassTable ifNil: [ MassTable := self createMassTable ] > > Where you have to remember to click on the example icon, or evaluate a doIt is the best solution. > > To me - this is WTF? Surely we can do better in an environment where we control the compiler, ide and interaction model? > > Tim > > > >> On 4 Mar 2019, at 16:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> (1) the basic concepts are clear (and have been for a long time): >> >> - when a class initialize method is loaded, it is executed afterwards, if and only if the source code changed >> >> - there are startUp[:] and shutDown[:] and SessionManager to handle images coming up, saving and going down >> >> With these tools you can build any behaviour you want. >> >> I am not sure we need something else, except maybe more education >> >> >> (2) the problem is much larger than just the class initialize method, since that can call other methods (like #initializeConstants, etc, ..) - even if the class initialize method did not change, a method further down might have and could require re-initialization. >> >> For this reason I sometimes put a timestamp in a comment of the class initialize method to force re-initialization since I known that I added a new constant somewhere (much) further down. >> >> >> Complex new features might do more harm than good >> >>> On 4 Mar 2019, at 17:13, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> >>> >>> On Mon, 4 Mar 2019 at 20:08, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>>> Am 04.03.2019 um 03:46 schrieb Ben Coman <btc(a)openinworld.com>: >>>> >>>> In relation to developing sample solutions for an Exercism exercise, the following observation was made about class initialization... >>>> >>>>> class is initialized on load - and not when you modify it - so this can be very confusing for users >>>> >>>> My first thought was to wonder if Quality Assistant could track whether a class initialize method had been run after it was modified, >>>> and display alerts. >>>> >>>> Alternatively, I wonder if a reasonable pattern would be to couple class-side lazy initialization >>>> with a pragma to reset a variable when the method is saved... >>>> >>>> MyClass class >> referenceData >>>> <onSaveResetVariable: ReferenceData> >>>> ^ ReferenceData := ReferenceData ifNil: [ 'reference data' ] >>>> >>> >>> Isnât the usual way to do that to register the class in the shutdown list and implement #shutdown: ? >>> >>> To me a good minute to work out why I didn't understand you. >>> Sorry, I meant <onMethodSaveResetVariable: ReferenceData> >>> >>> So when 'reference data' is updated and the modified method is saved, >>> the variable gets lazy initialized *again* with the new definition. >>> >>> hope that is more clear, >>> cheers -ben >> >> > >

March 5, 2019