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

Re: [Pharo-users] Working directory

by Stephane Ducasse

https://github.com/SquareBracketAssociates/DeepIntoPharo I will wait for the new version of pillar to port it. Right now I cannot latex it on my machine. Stef On Thu, Jan 18, 2018 at 7:25 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Stef, > > On 18 January 2018 at 18:43, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Tx alistair >> >> this is great that we made progress on this point. >> May be we should update the fileSystem chapter > > Yep. Can you point me to the source? I will try and take a look. > > I also think I'll add #workingDirectory: (be able to set the working > directory). I know Rajula did the work, but it didn't make it in to > the PR for some reason. Hopefully I can dig it up. > > Cheers, > Alistair > > > > >> On Thu, Jan 18, 2018 at 9:51 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> Hi Hilaire & Denis, >>> >>> On 18 January 2018 at 09:38, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>> Also notice that OS can give program very surprising working directory when >>>> you run it using UI tools. >>>> For example in MacOS drag image to the vm using Finder assigns root (/) as >>>> working directory. >>>> >>>> >>>> 2017-12-15 21:38 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: >>>>> >>>>> Oh, in a build for a DrGeo app based on P7, the working directory is one >>>>> level highter to the image folder. >>>>> >>>>> So in P7, there are two different results for the working directory: the >>>>> user home directory, and one level hight to image dir. >>>>> >>>>> What's the context? Where to look at? >>> >>> For Pharo 7: >>> >>> The working directory is C getcwd(). The differences you are seeing >>> will be the result of how Pharo is launched. If you run it from the >>> command line, it will be the current directory of the shell. I don't >>> use MacOS, but it sounds like dragging a file to an executable always >>> uses the root directory as cwd. >>> >>> The working directory is cached in DiskStore DefaultWorkingDirectory. >>> It's set at session startup to DiskStore >>> class>>defaultWorkingDirectory, which ultimately calls getcwd(). >>> >>> HTH, >>> Alistair >>> >> >

Jan. 18, 2018

Re: [Pharo-users] Working directory

by Alistair Grant

Hi Stef, On 18 January 2018 at 18:43, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Tx alistair > > this is great that we made progress on this point. > May be we should update the fileSystem chapter Yep. Can you point me to the source? I will try and take a look. I also think I'll add #workingDirectory: (be able to set the working directory). I know Rajula did the work, but it didn't make it in to the PR for some reason. Hopefully I can dig it up. Cheers, Alistair > On Thu, Jan 18, 2018 at 9:51 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Hilaire & Denis, >> >> On 18 January 2018 at 09:38, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>> Also notice that OS can give program very surprising working directory when >>> you run it using UI tools. >>> For example in MacOS drag image to the vm using Finder assigns root (/) as >>> working directory. >>> >>> >>> 2017-12-15 21:38 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: >>>> >>>> Oh, in a build for a DrGeo app based on P7, the working directory is one >>>> level highter to the image folder. >>>> >>>> So in P7, there are two different results for the working directory: the >>>> user home directory, and one level hight to image dir. >>>> >>>> What's the context? Where to look at? >> >> For Pharo 7: >> >> The working directory is C getcwd(). The differences you are seeing >> will be the result of how Pharo is launched. If you run it from the >> command line, it will be the current directory of the shell. I don't >> use MacOS, but it sounds like dragging a file to an executable always >> uses the root directory as cwd. >> >> The working directory is cached in DiskStore DefaultWorkingDirectory. >> It's set at session startup to DiskStore >> class>>defaultWorkingDirectory, which ultimately calls getcwd(). >> >> HTH, >> Alistair >> >

Jan. 18, 2018

Re: [Pharo-users] Working directory

by Stephane Ducasse

Tx alistair this is great that we made progress on this point. May be we should update the fileSystem chapter Stef On Thu, Jan 18, 2018 at 9:51 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Hilaire & Denis, > > On 18 January 2018 at 09:38, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> Also notice that OS can give program very surprising working directory when >> you run it using UI tools. >> For example in MacOS drag image to the vm using Finder assigns root (/) as >> working directory. >> >> >> 2017-12-15 21:38 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: >>> >>> Oh, in a build for a DrGeo app based on P7, the working directory is one >>> level highter to the image folder. >>> >>> So in P7, there are two different results for the working directory: the >>> user home directory, and one level hight to image dir. >>> >>> What's the context? Where to look at? > > For Pharo 7: > > The working directory is C getcwd(). The differences you are seeing > will be the result of how Pharo is launched. If you run it from the > command line, it will be the current directory of the shell. I don't > use MacOS, but it sounds like dragging a file to an executable always > uses the root directory as cwd. > > The working directory is cached in DiskStore DefaultWorkingDirectory. > It's set at session startup to DiskStore > class>>defaultWorkingDirectory, which ultimately calls getcwd(). > > HTH, > Alistair >

Jan. 18, 2018

Re: [Pharo-users] unsolicited package-cache use

by Ben Coman

On 18 January 2018 at 22:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Peter Kenny wrote >> Are you sure it's a bot? Google the name - there is a real person living >> near Seattle, with an interest in Smalltalk. > > I browsed some other posts from this account to the lists on Nabble. They > were more obviously on topic. Also, I met [him] at a Smalltalk conference or > two. My experience was that he speaks from a meta level and you have to > connect the dots yourself, which can be difficult to follow. IMHO he should > not be banned. I also browsed his history of posts. Their presentation is often strangely formatted and there seems a strange mix of on-topic posts certainly human generated** and off-topic posts that are distinctly bot-like. Its almost like there is a poetry virus riding on his email client. Now in either case regardless whether the latter posts are human or bot generated, they are distracting and not appropriate for the list. The appropriate action would raise these concerns (done) while avoiding easy context triggers and judge the nature of the public response, or private response to the one who raised the original concern. cheers -ben **or generated by a manifestation of the singularity, with whom we should maintain a positive working relationship.

Jan. 18, 2018

Re: [Pharo-users] unsolicited package-cache use

by Dale Henrichs

Hilaire, Have you included a method in your BaselineOf that looks like this: projectClass Â Â Â ^ MetacelloCypressBaselineProject if not, then what looks like a package-cache problem could be that you haven't told Metacello that you are using a metadataless filetree/tonel repository. Metacello has an internal rule to not load Monticello packages of the same version, since they are already loaded. However, when using metadataless repositories the filetree/tonel Monticello package readers typically generate a package name using the author/version `-cypress.1`, which make Metacello think that the versions are the same and the package is not loaded ... by including the above method in your baselineof, Metacello will know to ignore the Monticello author/version of the package and always load it.... Of course, because Monticello only installs changed definitions when loading a package, "loading the same package over and over again" costs a little bit in loading the _definitions_ into the image from disk, but doesn't end up compiling any new methods or creating new classes ... Dale On 1/18/18 6:49 AM, Hilaire wrote: > It was a month ago; I don't remember the details but from what I can > recover from my memory the scenario was: > > - From my dev. environment I saved code through Tonel, in the DrGeo > used CVS. > > - When building, I specifically ask the code saved thought Tonel to be > installed but the package-cache code version was used instead. It > could be out of sync. > > > Le 18/01/2018 Ã 15:22, Dale Henrichs a Ã©critÂ : >> Hilaire, >> >> Metacello just uses Monticello for loading and it is Monticello that >> is using the package-cache ... if there were a way to turn of the >> package-cache for Monticello I don't think that Metacello would know >> the difference. >> >> But, I am curious why you care whether or not package is used? >> >> Is there a specific problem that you are having? >> >> Dale >

Jan. 18, 2018

Re: [Pharo-users] unsolicited package-cache use

by Hilaire

It was a month ago; I don't remember the details but from what I can recover from my memory the scenario was: - From my dev. environment I saved code through Tonel, in the DrGeo used CVS. - When building, I specifically ask the code saved thought Tonel to be installed but the package-cache code version was used instead. It could be out of sync. Le 18/01/2018 Ã 15:22, Dale Henrichs a Ã©critÂ : > Hilaire, > > Metacello just uses Monticello for loading and it is Monticello that > is using the package-cache ... if there were a way to turn of the > package-cache for Monticello I don't think that Metacello would know > the difference. > > But, I am curious why you care whether or not package is used? > > Is there a specific problem that you are having? > > Dale -- Dr. Geo http://drgeo.eu

Jan. 18, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo TechTalk Dates

by Marcus Denker

> On 18 Jan 2018, at 15:35, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Marcus, > > Suggested topic: Contributing to Pharo7. :-) Indeed! The Feb 15 Date seems good for that. Marcus

Jan. 18, 2018

Re: [Pharo-users] unsolicited package-cache use

by Hilaire

Ok, the scary part get out then. According to what I understood, here three things for Kjell regarding his interest on DrGeo: 1) Get my latest DrGeo build[1]. The shipped VM within the application is out of sync, therefore a recent 32Bits VM should be used against the image located in DrGeo.app/Contets/Resources/drgeo.image 2) Concerning differential geometric, I don't know much. However DrGeo can be programmatically drived, particularly point defined by bloc can be useful to produce interactive graph with point interacting in cascade. See this Newton-Raphson example[2] Dr. Geo on Netwo-Raphson method 3) There is doc for programming DrGeo but the English version is a bit out of sync, http://www.drgeo.eu/help Hilaire [1] https://www.dropbox.com/s/wc18e21p371z28f/DrGeo.app-18.01a.zip?dl=0 [2] https://math.stackexchange.com/questions/726369/when-does-the-newton-raphso… Le 18/01/2018 Ã 15:06, Sean P. DeNigris a Ã©critÂ : > I browsed some other posts from this account to the lists on Nabble. They > were more obviously on topic. Also, I met Kjell at a Smalltalk conference or > two. My experience was that he speaks from a meta level and you have to > connect the dots yourself, which can be difficult to follow. IMHO he should > not be banned. -- Dr. Geo http://drgeo.eu

Jan. 18, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo TechTalk Dates

by Alistair Grant

Hi Marcus, Suggested topic: Contributing to Pharo7. :-) Thanks! Alistair On 18 January 2018 at 14:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Here are the next dates for the Pharo Techtalks. > (for recording of the past ones, see: http://pharo.org/TechTalk ) > > > Jan 30: Pharo TechTalk: Genetic Algorithms > https://association.pharo.org/event-2757884 > > For the others we have no topic yet, but dates are pre-fixed to: > > Feb 15 > https://association.pharo.org/event-2797065 > > March 22 > https://association.pharo.org/event-2797067 > > April 12 > https://association.pharo.org/event-2797068 > > May 17 > https://association.pharo.org/event-2797069 > > June 14 > https://association.pharo.org/event-2797070 > > > - If you have ideas for topics, please tell us! > - With no topic, we will use this slot for a general free discussion. > - If you want to do a TechTalk about a topic but no date is good, we can > change the date! > > Marcus >

Jan. 18, 2018

Re: [Pharo-users] unsolicited package-cache use

by Dale Henrichs

Hilaire, Metacello just uses Monticello for loading and it is Monticello that is using the package-cache ... if there were a way to turn of the package-cache for Monticello I don't think that Metacello would know the difference. But, I am curious why you care whether or not package is used? Is there a specific problem that you are having? Dale On 1/17/18 8:30 PM, HernÃ¡n Morales Durand wrote: > Hi Hilaire, > > Which Pharo version? > Have you found any solution to this? > In Gofer there was #disablePackageCache, in Metacello I don't know, > maybe experimenting with MetacelloLoaderPolicy but there are no class > comments. > Cheers, > > HernÃ¡n > > > 2017-12-18 17:24 GMT-03:00 Hilaire <hilaire(a)drgeo.eu>: >> If understood correctly, when using a tonel file repository to build up an >> image, Pharo seems instead to take the sources from some package-cache, >> which is out of sync, because the tonel file repo was updated from another >> image, with a different cache. I guess I can trick the file system but it is >> for the least very annoying, for the worst unreliable. >> >> >> >> Le 10/12/2017 Ã 18:16, Hilaire a Ã©crit : >>> I am using tonel format to install from and save to a local repository. >>> >>> How to prevent Monticello/Configuration/Metacello to save packages to the >>> image package-cache dir? >>> >>> Even when installing from a configuration with repo on tonel file format, >>> packages get created in the image package-cache directory. >>> >>> I have read there and there, Pharo gets confused and uses wrongly the >>> package-cache versions and not the local repo. >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >>

Jan. 18, 2018