April 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Recover question at startup

by Ben Coman

> > On Sat, Apr 14, 2018 at 5:56 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > >> Replying to myself for the record, these two lines seem to inactivate >> Epicea >> >> "Inactivate Epicea" >> EpSettings monitorEnabled: false. >> EpSettings lostEventsDetectorEnabled: false. >> >> >> Now, there is still likely an issue I don't understand > > On 15 April 2018 at 00:32, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Hi, > I have been checking this problem and the message is shown because is > trying to find the ombu file for the current session. > Usually what it does is comparing the file with the recorded size and > timestamp in the image to check that the file has no new changes. > If the file is newer or larger than the previous info of the image, the > recover message appears. > > I think there is a bug here, although I am not sure, I think that MartÃn > has to help to understand it. > Because in the current implementation if the file does not exists it > produces the recovery message. > Even though it can show that there are changes, if there is no file with > them I think is quite difficult to recover them. > > This behaviour is not happening in the machine where the image is built, > because the file exists in the disk. They are stored in the pharo-local > directory. > > Cheers, > Pablo > I didn't have a chance to check for repeat-ability, but yesterday I saved-quit and Image-A, then in PharoLauncher did a Copy of Image-A to image-B, then opening Image-B got a question about Recovery that I didn't expect or want. cheers -ben

April 15, 2018

Re: [Pharo-users] Where do we go now ?

by Ben Coman

On 13 April 2018 at 17:49, Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Esteban Lorenzano <estebanlm(a)gmail.com> > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Bcc: > Date: Fri, 13 Apr 2018 09:49:15 +0000 (UTC) > Subject: Re: [Pharo-users] Where do we go now ? > For those interested. > > Created the issues 21686, 21693, 21695, 21696. > > And more to come... > Thanks for those. I don't much time right to devote, but managed to knock one off. And I learn't something new. I'd not known there was a setting for screen background. The other ones seem related to a problem dealing with user home folders containing non-ascii characters. Currently this seems only to affect a small number of people, but is a show stopper for them, and the numbers will grow with our hoped for growing popularity. As a work around, in the PharoLauncher settings can you set the directories like C:\PharoLauncher\images C:\PharoLaucnher\vms and report if that helps. Note, I bumped into an issue changing that setting myself recently where it tries to migrate the existing images from the old to the new folder, causing a catch-22 when your trying to do that to work around other problems. To work around that, I had to scroll down the debug stack to find where the migration was iterating through the image folders, and short circuit that with "Return entered value" from the context menu. Any value will do when the return value is not used. good luck. @PharoLauncher maintainers, can the change in this setting be made to succeed even if the migration fails. (I need to run right now) cheers -ben

April 15, 2018

Re: [Pharo-users] QRCode - A thank you note

by Ben Coman

On 14 April 2018 at 22:15, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sven Van Caekenberghe-2 wrote > > Thanks Jochen, thanks everyone. > > Great report! Thanks, Sven :) I was thinking in the same direction - that > my > posts always seem to focus on our work moving forward, and I rarely take > the > time to do a nice writeup of successful applications like these, of which > I've had many. > > I was also thinking that many of the recent animated discussions are signs > of health in our community I recently came across an interesting hypothesis... "There are two types of programming languages. Those that people complain about, and those that people don't use." Is it masochistic to hope we are moving towards the former? > because: a) They seem to often involve people that are not regular posters to the > list, signaling a potential widening of buy-in > While there is likely a growing need to guard against trolls, consider that newcomers may commit limited time to posting, be hurting and lash out, and with fresh eyes, may be poking us where it hurts. For us, don't take it personally. If we focus our response on the technical aspects, we lead the discussion where we want it to go. The easiest thing for a Pharo newcomer to do when experiencing problems is to just drop it and move on to something else. That they put in the effort to articulate their issues is a good thing, and are the seeds of a contributor concerned with making Pharo better. For newcomers, remember that many people have invested a lot of volunteer effort into Pharo and is something dear to our hearts. We love specific *constructive* feedback that helps us make Pharo better, but broad complaints only detract with little benefit. cheers -ben P.S. Years ago, this article was influential to me... http://www.catb.org/esr/faqs/smart-questions.html > b) While our community values constructive feedback (even if it's very > direct), it also fiercely protects people who have given us a lot (as > evidenced by the overwhelming response to a recent trolling on another ML) > c) Maybe most important: they are often about code and infrastructure that > didn't even *exist* a few years ago. For example, now we complain about > breaking builds; I'm sure we all remember not long ago when there was *no* > CI at all to complain about! It seems amazing that the system is as stable > as it is considering everything we overhauled/invented, including: streams, > http, file system, browser (2x), git support, FFI, changes, catalog, the > compiler, GTâ¦ > > For myself, I am clear that any instability is a small price to pay for the > power and hope that Pharo offers. Every time I drop out of our live, > direct, > turetles-all-the-way down into a Ruby script, command line, or > configuration > file, this is proven again. > > All we have to do is hang on! It is a well known principle that it often > seem most difficult just before success and the difference is who quits and > who doesn't :) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

April 15, 2018

Re: [Pharo-users] Recover question at startup

by Hilaire

Le 14/04/2018 Ã 18:32, tesonep(a)gmail.com a Ã©critÂ : > > This behaviour is not happening in the machine where the image is > built, because the file exists in the disk. They are stored in the > pharo-local directory. And it tries to access itÂ and at some point the path to the file get absolute, right? Then saved in the built image? May be this should not happen. Thanks for the clarifications. Hilaire -- Dr. Geo http://drgeo.eu

April 14, 2018

Re: [Pharo-users] Recover question at startup

by tesonep＠gmail.com

Hi, I have been checking this problem and the message is shown because is trying to find the ombu file for the current session. Usually what it does is comparing the file with the recorded size and timestamp in the image to check that the file has no new changes. If the file is newer or larger than the previous info of the image, the recover message appears. I think there is a bug here, although I am not sure, I think that MartÃn has to help to understand it. Because in the current implementation if the file does not exists it produces the recovery message. Even though it can show that there are changes, if there is no file with them I think is quite difficult to recover them. This behaviour is not happening in the machine where the image is built, because the file exists in the disk. They are stored in the pharo-local directory. Cheers, Pablo On Sat, Apr 14, 2018 at 5:56 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Replying to myself for the record, these two lines seem to inactivate > Epicea > > "Inactivate Epicea" > EpSettings monitorEnabled: false. > EpSettings lostEventsDetectorEnabled: false. > > > Now, there is still likely an issue I don't understand > > > > -- > Dr. Geo > http://drgeo.eu > > > > -- Pablo Tesone. tesonep(a)gmail.com

April 14, 2018

Re: [Pharo-users] Recover question at startup

by Hilaire

Replying to myself for the record, these two lines seem to inactivate Epicea Â Â Â "Inactivate Epicea" Â Â Â EpSettings monitorEnabled: false. Â Â Â EpSettings lostEventsDetectorEnabled: false. Now, there is still likely an issue I don't understand -- Dr. Geo http://drgeo.eu

April 14, 2018

Re: [Pharo-users] [OT] Reminder about quoting/top-posting

by Sean P. DeNigris

Esteban A. Maringolo wrote > Can I ask for more trimming of the quoted text and/or emails replied to? +1. Always good and courteous advice. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 14, 2018

Re: [Pharo-users] QRCode - A thank you note

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > Thanks Jochen, thanks everyone. Great report! Thanks, Sven :) I was thinking in the same direction - that my posts always seem to focus on our work moving forward, and I rarely take the time to do a nice writeup of successful applications like these, of which I've had many. I was also thinking that many of the recent animated discussions are signs of health in our community because: a) They seem to often involve people that are not regular posters to the list, signaling a potential widening of buy-in b) While our community values constructive feedback (even if it's very direct), it also fiercely protects people who have given us a lot (as evidenced by the overwhelming response to a recent trolling on another ML) c) Maybe most important: they are often about code and infrastructure that didn't even *exist* a few years ago. For example, now we complain about breaking builds; I'm sure we all remember not long ago when there was *no* CI at all to complain about! It seems amazing that the system is as stable as it is considering everything we overhauled/invented, including: streams, http, file system, browser (2x), git support, FFI, changes, catalog, the compiler, GTâ¦ For myself, I am clear that any instability is a small price to pay for the power and hope that Pharo offers. Every time I drop out of our live, direct, turetles-all-the-way down into a Ruby script, command line, or configuration file, this is proven again. All we have to do is hang on! It is a well known principle that it often seem most difficult just before success and the difference is who quits and who doesn't :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 14, 2018

Re: [Pharo-users] Where do we go now ?

by Stephane Ducasse

Hilaire I will not start to argue. The bootstrap is in production since the beginning of Pharo 70. Now building multiple different images from it is another story. Stef On Sat, Apr 14, 2018 at 10:45 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > Le 13/04/2018 Ã 19:49, Stephane Ducasse a Ã©crit : >> >> We know where we go (we have a roadmap) and this is always the same >> and we are getting there. Tell me one smalltalk that is bootstrapped. > > I don't see we are there yet. At least from my humble point of view the > bootstrap still looks like WIP. > > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

April 14, 2018

Re: [Pharo-users] IDEA: I will record an Iceberg cast (an "Icecast" ; ) ) every tuesday

by Stephane Ducasse

Use big fonts. And add a title: "commiting a change" Stef On Sat, Apr 14, 2018 at 9:23 AM, Richard O'Keefe <raoknz(a)gmail.com> wrote: > You hero, sir. > > > On 14 April 2018 at 19:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> hi, >> >> The idea is to show a small example of something and to answer questions. >> >> First âIcecast" will be next Tuesday. >> You can send your questions in the iceberg channel or in list. >> >> cheers, >> Esteban >> >> ps: Is âevery tuesdayâ until I run out of things to show or time ;) > >

April 14, 2018