- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] another file reference question

by Alistair Grant

Hi Stef, On 2 February 2018 at 20:58, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Then I do not get why / is expecting a string and cannot accept a path. > > Then I do not get why we have paths. > Stef Paths are intended to be internal, and not something you ever deal with directly. I'm not sure I understand what you want to do, but maybe try replacing #/ with #resolve:, e.g.: '/home' asFileReference resolve: 'user' asFileReference " File @ /home/user" or: '/home' asFileReference resolve: 'user' asFileReference path " File @ /home/user" Cheers, Alistair > On Fri, Feb 2, 2018 at 8:22 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> HI >> >> I have the following scenario: >> >> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >> asFileReference / >> 'book.pillar' >> >>>>> >> "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result/book.pillar" >> >> ok it works. >> >> I want to update the contents of a target folder only if a file is >> missing or too old compared to a source. >> >> The idea is that I have a target folder and I need to know if a file >> located in the source tree should be copied under the target. >> So I compute the difference from the root of the source to the file >> and I want to apply this path to the target to check some file >> properties. >> >> now I do not understand how I can get the following working: >> >> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >> asFileReference >> / >> >> ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/book.pillar' >> asFileReference path) >> relativeTo: ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo' >> asFileReference path) >> >> >> Stef >

Feb. 2, 2018

Re: [Pharo-dev] another file reference question

by Denis Kudriashov

Hi Can you provide more simple example with shorter paths? I am lost in these long strings :). 2018-02-02 20:22 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > HI > > I have the following scenario: > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > asFileReference / > 'book.pillar' > > >>> > "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result/book.pillar" > > ok it works. > > I want to update the contents of a target folder only if a file is > missing or too old compared to a source. > > The idea is that I have a target folder and I need to know if a file > located in the source tree should be copied under the target. > So I compute the difference from the root of the source to the file > and I want to apply this path to the target to check some file > properties. > > now I do not understand how I can get the following working: > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > asFileReference > / > > ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/book.pillar' > asFileReference path) > relativeTo: ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo' > asFileReference path) > > > Stef > >

Feb. 2, 2018

Re: [Pharo-dev] printString of fileReference sucks!

by Denis Kudriashov

2018-02-02 20:39 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > If for some reason the option chosen is to keep the current > printString then the printString should be: > >>> 'File @ ''/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result''' > So I am for this approach

Feb. 2, 2018

Re: [Pharo-dev] printString of fileReference sucks!

by Denis Kudriashov

Hi. I do not think that getting simple string as result is a good idea. It is important to easily distinguish class of object using printIt operation and as a field in raw inspector. During code migration to FileSystem it is classic way to check variables in debugger to see if they are already file references or they are still strings. printIt is very handy in such cases. Best regards, Denis 2018-02-02 20:39 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > Hi Stef, all, > > I've seen this "inconsistency" as well. The current printSting tries > to be descriptive but isn't handy to work with. > > I would go one step further and have no #asFileReference suffix nor > File @ prefix, it is: > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > asFileReference printString > >>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > > > If for some reason the option chosen is to keep the current > printString then the printString should be: > >>> 'File @ ''/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result''' > > It is, a string with three tokens, the class name, the @ symbol and a > string as an argument, that way you can evaluate the result back. > > I prefer the first one, it enables you to work with files on > workspaces, if you're using inspectors the printString doesn't matter > much, since you're dealing with a specialized tool and there is no way > you can confuse a FileReference with a regular String instance > > Best regards, > Esteban A. Maringolo > > > 2018-02-02 16:12 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > > Hi > > > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > > asFileReference printString > >>>> "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result" > > > > so either we add @ one File or we redefine printString one reference to > be > > > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- > Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > > asFileReference so that we can do something with the printString > > result. > > > > What do you think? > > Guille is it what we talked together? > > > > Setf > > > >

Feb. 2, 2018

Re: [Pharo-dev] Change Pharo window icon

by Stephane Ducasse

Yes I did that when I was at University. So clearly dated. On Fri, Feb 2, 2018 at 8:40 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > For Windows one can change it using a resource editor. > > http://www.angusj.com/resourcehacker/ > > Phil > > On Feb 2, 2018 20:33, "Stephane Ducasse" <stepharo.self(a)gmail.com> wrote: >> >> Would it be possible to change the icon without having to compile a new >> VM? >> To me the current setup looks so monolithic and dated. >> I would expect that somebody can deploy a application with its own >> logo by just providing some new resources. >> >> Stef >> >> On Wed, Jan 31, 2018 at 11:17 PM, Eliot Miranda <eliot.miranda(a)gmail.com> >> wrote: >> > Hi Vincent, >> > >> > On Wed, Jan 31, 2018 at 12:07 PM, <Vincent.Blondeau(a)lamresearch.com> >> > wrote: >> >> >> >> Hi, >> >> >> >> I would like to know how to change the main Pharo window icon. I saw >> >> that >> >> there is a primitive for the title: >> >> DisplayScreen class >> primitiveWindowTitle:string: ; primitive: >> >> 'primitiveHostWindowTitle' module:'HostWindowPlugin' >> >> but I cannot find one for the icon. >> >> Should another primitive need to be implemented? >> > >> > >> > The icon is baked into the VM executable. So to change it one has to >> > build >> > a VM with a different icon. >> > >> > On Windows it is in >> > {build.win32x86,build.win64x64}/pharo.cog.spur/Pharo.ico >> > and the file that specifies to use Pharo.ico is >> > {build.win32x86,build.win64x64}/pharo.cog.spur/Pharo.rc >> > >> > On Mac OS X it is in >> > platforms/iOS/vm/OSX/Pharo.icns >> > (alongside three others such as PharoImage.icns) >> > and the file that specifies to use Pharo.icns is >> > {build.macos32x86,build.macos64x64}/pharo.cog.spur/Makefile >> > in setting the VM variable. The file that associates the other icons >> > with >> > specific file types is >> > platforms/iOS//vm/OSX/Pharo-Info.plist >> > >> > If you're changing the Pharo icon let me suggest you update the icon >> > files >> > themselves in the opensmalltalk-vm source tree. >> > >> > If you're creating a new variant of the VM for some new purpose (say a >> > special Lam VM) then let me suggest you add the icons to the >> > opensmalltalk-vm source tree, creating special build directories for >> > these >> > VMs, such as {build.macos32x86,build.macos64x64}/lam.pharo.cog.spur/ >> > >> > If you want to do this privately, then take either of the approaches >> > above >> > and simply don't publish the edits. You can write a script that takes >> > an >> > updated checked-out opensmalltalk-vm source tree and edits it with files >> > from a specific repository. I have such scripts and can help you with >> > them. >> > Hint, pax is a very convenient directory hierarchy copying tool >> > available at >> > least on Mac OS X. pax -rwlk will copy the trees under a sequence of >> > directories into their corresponding places in a target tree. >> > >> >> >> >> Thanks! >> >> >> >> Vincent >> >> >> >> >> > >> > >> > >> > -- >> > _,,,^..^,,,_ >> > best, Eliot >> >

Feb. 2, 2018

FileSystem copyToFolder: is missing :(

by Stephane Ducasse

Hi copyTo: forces the user to manipulate full path while we could also have aFileReference copyToFolder: aFileReference Now I have to create the target. Stef

Feb. 2, 2018

Re: [Pharo-dev] printString of fileReference sucks!

by Stephane Ducasse

I saw that guillermo already needed it for pillar Path >> pillarPrintString self isEmpty ifTrue: [ ^ '' ]. ^ String streamContents: [ :str | str nextPutAll: (self at: 1) asString. 2 to: self size do: [:i | str nextPutAll: self delimiter; nextPutAll: (self at: i) ] ] so there is clearly something wrong. On Fri, Feb 2, 2018 at 8:57 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Exactly, let us see what others think and we fix it. > > To me FileSystem deserves some love. > > > On Fri, Feb 2, 2018 at 8:39 PM, Esteban A. Maringolo > <emaringolo(a)gmail.com> wrote: >> Hi Stef, all, >> >> I've seen this "inconsistency" as well. The current printSting tries >> to be descriptive but isn't handy to work with. >> >> I would go one step further and have no #asFileReference suffix nor >> File @ prefix, it is: >> >> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >> asFileReference printString >>>>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >> >> >> If for some reason the option chosen is to keep the current >> printString then the printString should be: >>>>> 'File @ ''/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result''' >> >> It is, a string with three tokens, the class name, the @ symbol and a >> string as an argument, that way you can evaluate the result back. >> >> I prefer the first one, it enables you to work with files on >> workspaces, if you're using inspectors the printString doesn't matter >> much, since you're dealing with a specialized tool and there is no way >> you can confuse a FileReference with a regular String instance >> >> Best regards, >> Esteban A. Maringolo >> >> >> 2018-02-02 16:12 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> Hi >>> >>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >>> asFileReference printString >>>>>> "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result" >>> >>> so either we add @ one File or we redefine printString one reference to be >>> >>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >>> asFileReference so that we can do something with the printString >>> result. >>> >>> What do you think? >>> Guille is it what we talked together? >>> >>> Setf >>> >>

Feb. 2, 2018

Re: [Pharo-dev] another file reference question

by Stephane Ducasse

Then I do not get why / is expecting a string and cannot accept a path. Then I do not get why we have paths. Stef On Fri, Feb 2, 2018 at 8:22 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > HI > > I have the following scenario: > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > asFileReference / > 'book.pillar' > >>>> > "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result/book.pillar" > > ok it works. > > I want to update the contents of a target folder only if a file is > missing or too old compared to a source. > > The idea is that I have a target folder and I need to know if a file > located in the source tree should be copied under the target. > So I compute the difference from the root of the source to the file > and I want to apply this path to the target to check some file > properties. > > now I do not understand how I can get the following working: > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > asFileReference > / > > ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/book.pillar' > asFileReference path) > relativeTo: ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo' > asFileReference path) > > > Stef

Feb. 2, 2018

Re: [Pharo-dev] printString of fileReference sucks!

by Stephane Ducasse

Exactly, let us see what others think and we fix it. To me FileSystem deserves some love. On Fri, Feb 2, 2018 at 8:39 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Hi Stef, all, > > I've seen this "inconsistency" as well. The current printSting tries > to be descriptive but isn't handy to work with. > > I would go one step further and have no #asFileReference suffix nor > File @ prefix, it is: > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > asFileReference printString >>>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' > > > If for some reason the option chosen is to keep the current > printString then the printString should be: >>>> 'File @ ''/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result''' > > It is, a string with three tokens, the class name, the @ symbol and a > string as an argument, that way you can evaluate the result back. > > I prefer the first one, it enables you to work with files on > workspaces, if you're using inspectors the printString doesn't matter > much, since you're dealing with a specialized tool and there is no way > you can confuse a FileReference with a regular String instance > > Best regards, > Esteban A. Maringolo > > > 2018-02-02 16:12 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> Hi >> >> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >> asFileReference printString >>>>> "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result" >> >> so either we add @ one File or we redefine printString one reference to be >> >> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >> asFileReference so that we can do something with the printString >> result. >> >> What do you think? >> Guille is it what we talked together? >> >> Setf >> >

Feb. 2, 2018

Re: [Pharo-dev] Change Pharo window icon

by phil＠highoctane.be

For Windows one can change it using a resource editor. http://www.angusj.com/resourcehacker/ Phil On Feb 2, 2018 20:33, "Stephane Ducasse" <stepharo.self(a)gmail.com> wrote: > Would it be possible to change the icon without having to compile a new VM? > To me the current setup looks so monolithic and dated. > I would expect that somebody can deploy a application with its own > logo by just providing some new resources. > > Stef > > On Wed, Jan 31, 2018 at 11:17 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > Hi Vincent, > > > > On Wed, Jan 31, 2018 at 12:07 PM, <Vincent.Blondeau(a)lamresearch.com> > wrote: > >> > >> Hi, > >> > >> I would like to know how to change the main Pharo window icon. I saw > that > >> there is a primitive for the title: > >> DisplayScreen class >> primitiveWindowTitle:string: ; primitive: > >> 'primitiveHostWindowTitle' module:'HostWindowPlugin' > >> but I cannot find one for the icon. > >> Should another primitive need to be implemented? > > > > > > The icon is baked into the VM executable. So to change it one has to > build > > a VM with a different icon. > > > > On Windows it is in > > {build.win32x86,build.win64x64}/pharo.cog.spur/Pharo.ico > > and the file that specifies to use Pharo.ico is > > {build.win32x86,build.win64x64}/pharo.cog.spur/Pharo.rc > > > > On Mac OS X it is in > > platforms/iOS/vm/OSX/Pharo.icns > > (alongside three others such as PharoImage.icns) > > and the file that specifies to use Pharo.icns is > > {build.macos32x86,build.macos64x64}/pharo.cog.spur/Makefile > > in setting the VM variable. The file that associates the other icons > with > > specific file types is > > platforms/iOS//vm/OSX/Pharo-Info.plist > > > > If you're changing the Pharo icon let me suggest you update the icon > files > > themselves in the opensmalltalk-vm source tree. > > > > If you're creating a new variant of the VM for some new purpose (say a > > special Lam VM) then let me suggest you add the icons to the > > opensmalltalk-vm source tree, creating special build directories for > these > > VMs, such as {build.macos32x86,build.macos64x64}/lam.pharo.cog.spur/ > > > > If you want to do this privately, then take either of the approaches > above > > and simply don't publish the edits. You can write a script that takes an > > updated checked-out opensmalltalk-vm source tree and edits it with files > > from a specific repository. I have such scripts and can help you with > them. > > Hint, pax is a very convenient directory hierarchy copying tool > available at > > least on Mac OS X. pax -rwlk will copy the trees under a sequence of > > directories into their corresponding places in a target tree. > > > >> > >> Thanks! > >> > >> Vincent > >> > >> > > > > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > >

Feb. 2, 2018