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

Re: [Pharo-users] ensureCreateFile

by Valentin Ryckewaert

I used this because here it's the folder which doesn't exist so I didn't know if FileDoesNotExist were a good idea, here it's as you want. 2016-04-26 11:24 GMT+02:00 Cyril Ferlicot Delbecque < cyril.ferlicot(a)gmail.com>: > > > On 26/04/2016 10:34, Valentin Ryckewaert wrote: > > Hi ! > > > > I made this if it's ok for you i'll post it on fogbugs : > > > > AbstractFileReference > > createFile > > "Create if necessary a file for the receiver. If the parent does not > > exist return an exception" > > self parent ensureCreateDirectory. > > self writeStream close. > > createDirectory > > "Verifies that the directory does not exist and only creates if > > necessary. Do not remove files contained if they exist.If the parents > > does not exist return an exception" > > self parent exists ifFalse:[self error:'The parent directory does not > > exist']. > > ^ self resolve ensureCreateDirectory > > ensureCreateFile > > "Create if necessary a file for the receiver. If the parent does not > > exist creates it" > > self parent ensureCreateDirectory. > > self writeStream close. > > ensureCreateDirectory "Verifies that the directory does not exist and > > only creates if necessary. Do not remove files contained if they > > exist.If the parents folder does not exist create it" ^ self resolve > > ensureCreateDirectory > > > > Hi, > > I think that createDirectory should raise a FileDoesNotExist instead of > an Exception. > > BTW, this may be good to discuss in another issue but we have a > FileDoesNotExistException and a FileDoesNotExist in the image. Maybe we > can unify both? Or if there is a difference we can explain it in the > class comment because I don't see the difference. > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > >

April 26, 2016

Re: [Pharo-users] ensureCreateFile

by Cyril Ferlicot Delbecque

On 26/04/2016 10:34, Valentin Ryckewaert wrote: > Hi ! > > I made this if it's ok for you i'll post it on fogbugs : > > AbstractFileReference > createFile > "Create if necessary a file for the receiver. If the parent does not > exist return an exception" > self parent ensureCreateDirectory. > self writeStream close. > createDirectory > "Verifies that the directory does not exist and only creates if > necessary. Do not remove files contained if they exist.If the parents > does not exist return an exception" > self parent exists ifFalse:[self error:'The parent directory does not > exist']. > ^ self resolve ensureCreateDirectory > ensureCreateFile > "Create if necessary a file for the receiver. If the parent does not > exist creates it" > self parent ensureCreateDirectory. > self writeStream close. > ensureCreateDirectory "Verifies that the directory does not exist and > only creates if necessary. Do not remove files contained if they > exist.If the parents folder does not exist create it" ^ self resolve > ensureCreateDirectory > Hi, I think that createDirectory should raise a FileDoesNotExist instead of an Exception. BTW, this may be good to discuss in another issue but we have a FileDoesNotExistException and a FileDoesNotExist in the image. Maybe we can unify both? Or if there is a difference we can explain it in the class comment because I don't see the difference. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

April 26, 2016

Re: [Pharo-users] [ANN] Genetic Algorithm is available from the Catalog

by CÃ©drick BÃ©ler

I think this is GeneticAlgorithm ^^ Cheers, Cedrik EnvoyÃ© de mon iPhone > Le 26 avr. 2016 Ã 10:22, Serge Stinckwich <serge.stinckwich(a)gmail.com> a Ã©crit : > > Cool but without name this is maybe difficult to find :-) > > On Mon, Apr 25, 2016 at 10:10 PM, Alexandre Bergel > <alexandre.bergel(a)me.com> wrote: >> Hi! >> >> I did a bit of programmingâ¦ A genetic algorithm is available from the Catalog. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

April 26, 2016

Re: [Pharo-users] ensureCreateFile

by Valentin Ryckewaert

Hi, https://pharo.fogbugz.com/f/cases/18084/FileReference-EnsureCreateFile the issue report I just corrected it in the slice Peter, sorry for my mistake. 2016-04-26 10:34 GMT+02:00 Valentin Ryckewaert < valentin.ryckewaert(a)gmail.com>: > Hi ! > > I made this if it's ok for you i'll post it on fogbugs : > > AbstractFileReference > createFile > "Create if necessary a file for the receiver. If the parent does not > exist return an exception" > self parent ensureCreateDirectory. > self writeStream close. > createDirectory > "Verifies that the directory does not exist and only creates if necessary. > Do not remove files contained if they exist.If the parents does not exist > return an exception" > self parent exists ifFalse:[self error:'The parent directory does not > exist']. > ^ self resolve ensureCreateDirectory > ensureCreateFile > "Create if necessary a file for the receiver. If the parent does not > exist creates it" > self parent ensureCreateDirectory. > self writeStream close. > ensureCreateDirectory "Verifies that the directory does not exist and only > creates if necessary. Do not remove files contained if they exist.If the > parents folder does not exist create it" ^ self resolve > ensureCreateDirectory > > 2016-04-26 10:34 GMT+02:00 Valentin Ryckewaert < > valentin.ryckewaert(a)gmail.com>: > >> Hi ! >> >> I made this if it's ok for you i'll post it on fogbugs : >> >> AbstractFileReference >> createFile >> "Create if necessary a file for the receiver. If the parent does not >> exist return an exception" >> self parent ensureCreateDirectory. >> self writeStream close. >> createDirectory >> "Verifies that the directory does not exist and only creates if >> necessary. Do not remove files contained if they exist.If the parents does >> not exist return an exception" >> self parent exists ifFalse:[self error:'The parent directory does not >> exist']. >> ^ self resolve ensureCreateDirectory >> ensureCreateFile >> "Create if necessary a file for the receiver. If the parent does not >> exist creates it" >> self parent ensureCreateDirectory. >> self writeStream close. >> ensureCreateDirectory "Verifies that the directory does not exist and >> only creates if necessary. Do not remove files contained if they exist.If >> the parents folder does not exist create it" ^ self resolve >> ensureCreateDirectory >> >> >> 2016-04-25 16:28 GMT+02:00 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> oui moi aussi >>> je me demandais si on devait introduire une autre methode mais en fait >>> le nouveau comportement est compatible donc je le ferais. >>> >>> >>> On 25 Apr 2016, at 13:58, Valentin Ryckewaert < >>> valentin.ryckewaert(a)gmail.com> wrote: >>> >>> Tu en penses quoi toi ? >>> Je trouve Ã§a illogique que ensureCreate ne signifie pas la meme chose >>> pour un dossier ou pour un fichier. >>> >>> ---------- Forwarded message ---------- >>> From: Valentin Ryckewaert <valentin.ryckewaert(a)gmail.com> >>> Date: 2016-04-22 10:11 GMT+02:00 >>> Subject: Re: [Pharo-users] ensureCreateFile >>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>> >>> >>> For me ensureCreateFolder is made to be sure the folder is created, if >>> you make '/home/a/b/c/d' with a b c d not existing it will create all of >>> them. >>> ensureCreateFile should do the same thing no ? >>> >>> 2016-04-21 13:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >>> >>>> because it's like this >>>> >>>> ensureCreateFolder : create the folder structure if necessary >>>> ensureCreateFile : create the file if necessary >>>> >>>> I really don't see any gain from changing existing behavior and >>>> introducing potential problems. >>>> If I ask for file to be created, I don't expect that the system will >>>> suddenly start creating folders, that's a unintentional side effect. >>>> If you need it for your convenience, then it's dead-easy to implement >>>> without breaking existing stuff. >>>> >>>> >>>> On Thu, Apr 21, 2016 at 10:35 AM, Denis Kudriashov < >>>> dionisiydk(a)gmail.com> wrote: >>>> >>>>> >>>>> 2016-04-21 9:55 GMT+02:00 Valentin Ryckewaert < >>>>> valentin.ryckewaert(a)gmail.com>: >>>>> >>>>>> Yes but why ensureCreateFile then ? >>>>>> Why don't we juste create a message createFile as there is >>>>>> createFolder ? >>>>>> createFolder : create the folder >>>>>> createFile : create the file >>>>>> >>>>>> ensureCreateFolder : create the folder and its parents if necessary >>>>>> ensureCreateFile : create the file and its parents if necessary >>>>>> >>>>> >>>>> +1 >>>>> >>>> >>>> >>> >>> >>> -------------------------------------------- >>> StÃ©phane Ducasse >>> http://stephane.ducasse.free.fr >>> http://www.synectique.eu / http://www.pharo.org >>> 03 59 35 87 52 >>> Assistant: Julie Jonas >>> 03 59 57 78 50 >>> 03 59 35 86 16 >>> >>> S. Ducasse - Inria >>> 40, avenue Halley, >>> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >>> Villeneuve d'Ascq 59650 >>> France >>> >>> >> >

April 26, 2016

Re: [Pharo-users] ensureCreateFile

by Denis Kudriashov

2016-04-26 10:34 GMT+02:00 Valentin Ryckewaert < valentin.ryckewaert(a)gmail.com>: > createFile > "Create if necessary a file for the receiver. If the parent does not > exist return an exception" > self parent ensureCreateDirectory. > self writeStream close. > But it is wrong? It same as ensureCreateFile

April 26, 2016

Re: [Pharo-users] ensureCreateFile

by Peter UhnÃ¡k

> > > AbstractFileReference > createFile > "Create if necessary a file for the receiver. If the parent does not > exist return an exception" > self parent ensureCreateDirectory. > self writeStream close. > > ensureCreateFile > "Create if necessary a file for the receiver. If the parent does not > exist creates it" > self parent ensureCreateDirectory. > self writeStream close. > I don't see any difference in the implementation. Wrong copy/paste? But from the comments I am for it. :)

April 26, 2016

Re: [Pharo-users] ensureCreateFile

by Valentin Ryckewaert

Hi ! I made this if it's ok for you i'll post it on fogbugs : AbstractFileReference createFile "Create if necessary a file for the receiver. If the parent does not exist return an exception" self parent ensureCreateDirectory. self writeStream close. createDirectory "Verifies that the directory does not exist and only creates if necessary. Do not remove files contained if they exist.If the parents does not exist return an exception" self parent exists ifFalse:[self error:'The parent directory does not exist']. ^ self resolve ensureCreateDirectory ensureCreateFile "Create if necessary a file for the receiver. If the parent does not exist creates it" self parent ensureCreateDirectory. self writeStream close. ensureCreateDirectory "Verifies that the directory does not exist and only creates if necessary. Do not remove files contained if they exist.If the parents folder does not exist create it" ^ self resolve ensureCreateDirectory 2016-04-26 10:34 GMT+02:00 Valentin Ryckewaert < valentin.ryckewaert(a)gmail.com>: > Hi ! > > I made this if it's ok for you i'll post it on fogbugs : > > AbstractFileReference > createFile > "Create if necessary a file for the receiver. If the parent does not exist > return an exception" > self parent ensureCreateDirectory. > self writeStream close. > createDirectory > "Verifies that the directory does not exist and only creates if necessary. > Do not remove files contained if they exist.If the parents does not exist > return an exception" > self parent exists ifFalse:[self error:'The parent directory does not > exist']. > ^ self resolve ensureCreateDirectory > ensureCreateFile > "Create if necessary a file for the receiver. If the parent does not exist > creates it" > self parent ensureCreateDirectory. > self writeStream close. > ensureCreateDirectory "Verifies that the directory does not exist and only > creates if necessary. Do not remove files contained if they exist.If the > parents folder does not exist create it" ^ self resolve > ensureCreateDirectory > > > 2016-04-25 16:28 GMT+02:00 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> oui moi aussi >> je me demandais si on devait introduire une autre methode mais en fait >> le nouveau comportement est compatible donc je le ferais. >> >> >> On 25 Apr 2016, at 13:58, Valentin Ryckewaert < >> valentin.ryckewaert(a)gmail.com> wrote: >> >> Tu en penses quoi toi ? >> Je trouve Ã§a illogique que ensureCreate ne signifie pas la meme chose >> pour un dossier ou pour un fichier. >> >> ---------- Forwarded message ---------- >> From: Valentin Ryckewaert <valentin.ryckewaert(a)gmail.com> >> Date: 2016-04-22 10:11 GMT+02:00 >> Subject: Re: [Pharo-users] ensureCreateFile >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> >> >> For me ensureCreateFolder is made to be sure the folder is created, if >> you make '/home/a/b/c/d' with a b c d not existing it will create all of >> them. >> ensureCreateFile should do the same thing no ? >> >> 2016-04-21 13:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> >>> because it's like this >>> >>> ensureCreateFolder : create the folder structure if necessary >>> ensureCreateFile : create the file if necessary >>> >>> I really don't see any gain from changing existing behavior and >>> introducing potential problems. >>> If I ask for file to be created, I don't expect that the system will >>> suddenly start creating folders, that's a unintentional side effect. >>> If you need it for your convenience, then it's dead-easy to implement >>> without breaking existing stuff. >>> >>> >>> On Thu, Apr 21, 2016 at 10:35 AM, Denis Kudriashov <dionisiydk(a)gmail.com >>> > wrote: >>> >>>> >>>> 2016-04-21 9:55 GMT+02:00 Valentin Ryckewaert < >>>> valentin.ryckewaert(a)gmail.com>: >>>> >>>>> Yes but why ensureCreateFile then ? >>>>> Why don't we juste create a message createFile as there is >>>>> createFolder ? >>>>> createFolder : create the folder >>>>> createFile : create the file >>>>> >>>>> ensureCreateFolder : create the folder and its parents if necessary >>>>> ensureCreateFile : create the file and its parents if necessary >>>>> >>>> >>>> +1 >>>> >>> >>> >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> 03 59 57 78 50 >> 03 59 35 86 16 >> >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >> >

April 26, 2016

Re: [Pharo-users] [ANN] Genetic Algorithm is available from the Catalog

by Serge Stinckwich

Cool but without name this is maybe difficult to find :-) On Mon, Apr 25, 2016 at 10:10 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I did a bit of programmingâ¦ A genetic algorithm is available from the Catalog. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 26, 2016

Re: [Pharo-users] Moose-Algos-Graph Library in Pharo 5

by Volkert

Christophe, Alexandre, i will give it a try .... How can i load "Moose-Tests-Algos-Graph" into Pharo 5.0? Thanks, Volkert On 25.04.2016 10:23, Christophe Demarey wrote: > Hi, > > Moose-Algos-Graph contains very classical algorithmes applying on graphes (Breadth-first search, dijkstra, tarjan, topological sorting, etc). > It is now in Pharo 5 because it is used by the dependency analyser. > As Alexandre said, there are almost no documentation and it is not so easy to combine algorithms (run an algo on the output of another algo). > You can look at Moose-Tests-Algos-Graph package (to be loaded) and DADependencyChecker>>#shortestPathToPackageIntroducingDependency:startingFrom: for some examples. > > Christophe > > >> Le 24 avr. 2016 Ã 20:55, Alexandre Bergel <alexandre.bergel(a)me.com> a Ã©crit : >> >> Hi Volkert! >> >> This package contains some classical graph algorithms we use in software analysis (e.g., clustering, strong component). >> Unfortunately, there is no much documentation about it. If you are using these algorithms, then it would be great to write some documentation. >> >> In addition to this package, and as you know, Roassal offers many layout algorithms. >> >> Regarding, >> Alexandre >> >>> On Apr 24, 2016, at 6:39 AM, Volkert <volkert(a)komponentenwerkstatt.de> wrote: >>> >>> Dear all, >>> >>> if have found the "Moose-Algos-Graph" package in Pharo 5. What is the idea behind this package? Is this "the" official Pharo Graph Library? >>> Do we have some examples how to use it? >>> >>> LG, >>> Volkert >>> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >

April 25, 2016

Re: [Pharo-users] Dawn Theme on Pharo 4.0

by Brad Selfridge

Love the theme. I have a few questions. 1). It there a way to user the Watery theme min/max/close window button styles in this theme? 2). Is there a way for the active window shadow value to be lighter (to help differentiate the active widow)? 3). The tool tip text is hard to read. Can the text be changed to contrast more with the background? 4). Can the theme name, (the one displayed in the System/Settings/Appearance), be changed to Pharo3 Dawn rather than Pharo3 Dark? Thanks, ----- Brad Selfridge -- View this message in context: http://forum.world.st/Dawn-Theme-on-Pharo-4-0-tp4889541p4891953.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 25, 2016