May 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

by Denis Kudriashov

2018-05-21 21:14 GMT+03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > On 21 May 2018, at 20:07, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > > > If I'm recalling well (which I might not :)) there is one thing (that I > don't quite like) that prevents these two classes to be easily merged into > one: their #defaultAction. > > We need a good talk/discussion about default actions. > > I am pretty confused by them, and my first reaction is that I don't like > them, too much UI in there. > I am 100% with you. UI queries to users should be in UI. > > Step 1 is to define clearly what #defaultAction is, what is should do, > what is allowed, what not, good practices, intended purpose, etc... > > > On Mon, May 21, 2018 at 7:07 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > On Mon, May 21, 2018 at 03:01:57PM +0200, Cyril Ferlicot D. wrote: > > > Le 21/05/2018 ?? 14:58, Alistair Grant a ??crit??: > > > > Hi Everyone, > > > > > > > > Does anyone know the history behind FileDoesNotExist and > > > > FileDoesNotExistException? > > > > > > > > Both classes exist in 6.1, and as far as I can tell, both are > intended > > > > to do the same thing, i.e. the class comments are: > > > > > > > > FileDoesNotExist; > > > > > > > > I am raised when an operation is attempted on a file that does not > > > > exist. This includes cases where a file operation is attempted on a > > > > directory. > > > > > > > > > > > > > > > > FileDoesNotExistException: > > > > > > > > Notify when fie does not exist > > > > > > > > > > > > > > > > This means that programs have to check for both in exceptions, or be > > > > very sure of whether any object they are using ultimately refers to a > > > > File or a FileReference. > > > > > > > > If there isn't a good reason for having both, I think we should > remove > > > > one. Since FileDoesNotExistException is loaded first in the > bootstrap > > > > process (since it is part of Files, not FileSystem), keeping it > probably > > > > makes more sense. > > > > > > > > Similar duplication exists for FileAlreadyExistsException and > > > > FileExists. > > > > > > > > Thoughts? > > > > > > > > > > Hi Alistar, > > > > > > See the conversation here: > > > > > > https://pharo.fogbugz.com/f/cases/19026/Merge-FileDoesNotExist-and- > FileDoesNotExistException > > > > Thanks, Cyril! > > > > > > > > On Mon, May 21, 2018 at 03:36:05PM +0200, Sven Van Caekenberghe wrote: > > > I vote for the simple names without Exception in them. > > > > On Mon, May 21, 2018 at 05:59:32PM +0300, Denis Kudriashov wrote: > > > +1 > > > > Me too... :-) > > > > > > I'll work on this next. > > > > Cheers, > > Alistair > > > > > > > > > > > > -- > > > > Guille Polito > > Research Engineer > > > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - http://www.cnrs.fr > > > > Web: http://guillep.github.io > > Phone: +33 06 52 70 66 13 > > >

May 21, 2018

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

by Sven Van Caekenberghe

> On 21 May 2018, at 20:07, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > If I'm recalling well (which I might not :)) there is one thing (that I don't quite like) that prevents these two classes to be easily merged into one: their #defaultAction. We need a good talk/discussion about default actions. I am pretty confused by them, and my first reaction is that I don't like them, too much UI in there. Step 1 is to define clearly what #defaultAction is, what is should do, what is allowed, what not, good practices, intended purpose, etc... > On Mon, May 21, 2018 at 7:07 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Mon, May 21, 2018 at 03:01:57PM +0200, Cyril Ferlicot D. wrote: > > Le 21/05/2018 ?? 14:58, Alistair Grant a ??crit??: > > > Hi Everyone, > > > > > > Does anyone know the history behind FileDoesNotExist and > > > FileDoesNotExistException? > > > > > > Both classes exist in 6.1, and as far as I can tell, both are intended > > > to do the same thing, i.e. the class comments are: > > > > > > FileDoesNotExist; > > > > > > I am raised when an operation is attempted on a file that does not > > > exist. This includes cases where a file operation is attempted on a > > > directory. > > > > > > > > > > > > FileDoesNotExistException: > > > > > > Notify when fie does not exist > > > > > > > > > > > > This means that programs have to check for both in exceptions, or be > > > very sure of whether any object they are using ultimately refers to a > > > File or a FileReference. > > > > > > If there isn't a good reason for having both, I think we should remove > > > one. Since FileDoesNotExistException is loaded first in the bootstrap > > > process (since it is part of Files, not FileSystem), keeping it probably > > > makes more sense. > > > > > > Similar duplication exists for FileAlreadyExistsException and > > > FileExists. > > > > > > Thoughts? > > > > > > > Hi Alistar, > > > > See the conversation here: > > > > https://pharo.fogbugz.com/f/cases/19026/Merge-FileDoesNotExist-and-FileDoes… > > Thanks, Cyril! > > > > On Mon, May 21, 2018 at 03:36:05PM +0200, Sven Van Caekenberghe wrote: > > I vote for the simple names without Exception in them. > > On Mon, May 21, 2018 at 05:59:32PM +0300, Denis Kudriashov wrote: > > +1 > > Me too... :-) > > > I'll work on this next. > > Cheers, > Alistair > > > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

May 21, 2018

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

by Guillermo Polito

If I'm recalling well (which I might not :)) there is one thing (that I don't quite like) that prevents these two classes to be easily merged into one: their #defaultAction. On Mon, May 21, 2018 at 7:07 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Mon, May 21, 2018 at 03:01:57PM +0200, Cyril Ferlicot D. wrote: > > Le 21/05/2018 ?? 14:58, Alistair Grant a ??crit??: > > > Hi Everyone, > > > > > > Does anyone know the history behind FileDoesNotExist and > > > FileDoesNotExistException? > > > > > > Both classes exist in 6.1, and as far as I can tell, both are intended > > > to do the same thing, i.e. the class comments are: > > > > > > FileDoesNotExist; > > > > > > I am raised when an operation is attempted on a file that does not > > > exist. This includes cases where a file operation is attempted on a > > > directory. > > > > > > > > > > > > FileDoesNotExistException: > > > > > > Notify when fie does not exist > > > > > > > > > > > > This means that programs have to check for both in exceptions, or be > > > very sure of whether any object they are using ultimately refers to a > > > File or a FileReference. > > > > > > If there isn't a good reason for having both, I think we should remove > > > one. Since FileDoesNotExistException is loaded first in the bootstrap > > > process (since it is part of Files, not FileSystem), keeping it > probably > > > makes more sense. > > > > > > Similar duplication exists for FileAlreadyExistsException and > > > FileExists. > > > > > > Thoughts? > > > > > > > Hi Alistar, > > > > See the conversation here: > > > > https://pharo.fogbugz.com/f/cases/19026/Merge-FileDoesNotExist-and- > FileDoesNotExistException > > Thanks, Cyril! > > > > On Mon, May 21, 2018 at 03:36:05PM +0200, Sven Van Caekenberghe wrote: > > I vote for the simple names without Exception in them. > > On Mon, May 21, 2018 at 05:59:32PM +0300, Denis Kudriashov wrote: > > +1 > > Me too... :-) > > > I'll work on this next. > > Cheers, > Alistair > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 21, 2018

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

by Alistair Grant

On Mon, May 21, 2018 at 03:01:57PM +0200, Cyril Ferlicot D. wrote: > Le 21/05/2018 ?? 14:58, Alistair Grant a ??crit??: > > Hi Everyone, > > > > Does anyone know the history behind FileDoesNotExist and > > FileDoesNotExistException? > > > > Both classes exist in 6.1, and as far as I can tell, both are intended > > to do the same thing, i.e. the class comments are: > > > > FileDoesNotExist; > > > > I am raised when an operation is attempted on a file that does not > > exist. This includes cases where a file operation is attempted on a > > directory. > > > > > > > > FileDoesNotExistException: > > > > Notify when fie does not exist > > > > > > > > This means that programs have to check for both in exceptions, or be > > very sure of whether any object they are using ultimately refers to a > > File or a FileReference. > > > > If there isn't a good reason for having both, I think we should remove > > one. Since FileDoesNotExistException is loaded first in the bootstrap > > process (since it is part of Files, not FileSystem), keeping it probably > > makes more sense. > > > > Similar duplication exists for FileAlreadyExistsException and > > FileExists. > > > > Thoughts? > > > > Hi Alistar, > > See the conversation here: > > https://pharo.fogbugz.com/f/cases/19026/Merge-FileDoesNotExist-and-FileDoes… Thanks, Cyril! On Mon, May 21, 2018 at 03:36:05PM +0200, Sven Van Caekenberghe wrote: > I vote for the simple names without Exception in them. On Mon, May 21, 2018 at 05:59:32PM +0300, Denis Kudriashov wrote: > +1 Me too... :-) I'll work on this next. Cheers, Alistair

May 21, 2018

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

by Denis Kudriashov

+1 2018-05-21 16:36 GMT+03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I vote for the simple names without Exception in them. > > > On 21 May 2018, at 15:01, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> > wrote: > > > > Le 21/05/2018 Ã 14:58, Alistair Grant a Ã©crit : > >> Hi Everyone, > >> > >> Does anyone know the history behind FileDoesNotExist and > >> FileDoesNotExistException? > >> > >> Both classes exist in 6.1, and as far as I can tell, both are intended > >> to do the same thing, i.e. the class comments are: > >> > >> FileDoesNotExist; > >> > >> I am raised when an operation is attempted on a file that does not > >> exist. This includes cases where a file operation is attempted on a > >> directory. > >> > >> > >> > >> FileDoesNotExistException: > >> > >> Notify when fie does not exist > >> > >> > >> > >> This means that programs have to check for both in exceptions, or be > >> very sure of whether any object they are using ultimately refers to a > >> File or a FileReference. > >> > >> If there isn't a good reason for having both, I think we should remove > >> one. Since FileDoesNotExistException is loaded first in the bootstrap > >> process (since it is part of Files, not FileSystem), keeping it probably > >> makes more sense. > >> > >> Similar duplication exists for FileAlreadyExistsException and > >> FileExists. > >> > >> Thoughts? > >> > > > > Hi Alistar, > > > > See the conversation here: > > > > https://pharo.fogbugz.com/f/cases/19026/Merge-FileDoesNotExist-and- > FileDoesNotExistException > > > >> > >> Thanks, > >> Alistair > >> > > > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > >

May 21, 2018

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

by Sven Van Caekenberghe

I vote for the simple names without Exception in them. > On 21 May 2018, at 15:01, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 21/05/2018 Ã 14:58, Alistair Grant a Ã©crit : >> Hi Everyone, >> >> Does anyone know the history behind FileDoesNotExist and >> FileDoesNotExistException? >> >> Both classes exist in 6.1, and as far as I can tell, both are intended >> to do the same thing, i.e. the class comments are: >> >> FileDoesNotExist; >> >> I am raised when an operation is attempted on a file that does not >> exist. This includes cases where a file operation is attempted on a >> directory. >> >> >> >> FileDoesNotExistException: >> >> Notify when fie does not exist >> >> >> >> This means that programs have to check for both in exceptions, or be >> very sure of whether any object they are using ultimately refers to a >> File or a FileReference. >> >> If there isn't a good reason for having both, I think we should remove >> one. Since FileDoesNotExistException is loaded first in the bootstrap >> process (since it is part of Files, not FileSystem), keeping it probably >> makes more sense. >> >> Similar duplication exists for FileAlreadyExistsException and >> FileExists. >> >> Thoughts? >> > > Hi Alistar, > > See the conversation here: > > https://pharo.fogbugz.com/f/cases/19026/Merge-FileDoesNotExist-and-FileDoes… > >> >> Thanks, >> Alistair >> > > > -- > Cyril Ferlicot > https://ferlicot.fr

May 21, 2018

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

by Cyril Ferlicot D.

Le 21/05/2018 Ã 14:58, Alistair Grant a Ã©critÂ : > Hi Everyone, > > Does anyone know the history behind FileDoesNotExist and > FileDoesNotExistException? > > Both classes exist in 6.1, and as far as I can tell, both are intended > to do the same thing, i.e. the class comments are: > > FileDoesNotExist; > > I am raised when an operation is attempted on a file that does not > exist. This includes cases where a file operation is attempted on a > directory. > > > > FileDoesNotExistException: > > Notify when fie does not exist > > > > This means that programs have to check for both in exceptions, or be > very sure of whether any object they are using ultimately refers to a > File or a FileReference. > > If there isn't a good reason for having both, I think we should remove > one. Since FileDoesNotExistException is loaded first in the bootstrap > process (since it is part of Files, not FileSystem), keeping it probably > makes more sense. > > Similar duplication exists for FileAlreadyExistsException and > FileExists. > > Thoughts? > Hi Alistar, See the conversation here: https://pharo.fogbugz.com/f/cases/19026/Merge-FileDoesNotExist-and-FileDoes… > > Thanks, > Alistair > -- Cyril Ferlicot https://ferlicot.fr

May 21, 2018

FileDoesNotExist vs FileDoesNotExistException

by Alistair Grant

Hi Everyone, Does anyone know the history behind FileDoesNotExist and FileDoesNotExistException? Both classes exist in 6.1, and as far as I can tell, both are intended to do the same thing, i.e. the class comments are: FileDoesNotExist; I am raised when an operation is attempted on a file that does not exist. This includes cases where a file operation is attempted on a directory. FileDoesNotExistException: Notify when fie does not exist This means that programs have to check for both in exceptions, or be very sure of whether any object they are using ultimately refers to a File or a FileReference. If there isn't a good reason for having both, I think we should remove one. Since FileDoesNotExistException is loaded first in the bootstrap process (since it is part of Files, not FileSystem), keeping it probably makes more sense. Similar duplication exists for FileAlreadyExistsException and FileExists. Thoughts? Thanks, Alistair

May 21, 2018

Re: [Pharo-dev] Pharo 7 on SqueakJS (demo)

by Sven Van Caekenberghe

> On 21 May 2018, at 12:01, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, > > with some tweaks mostly related to FFI and fonts, we are able to run Pharo 7 on SqueakJS VM. > > Do not expect blazing performance. Currently, it is about two orders of magnitude slower than the native VM. > > https://pavel-krivanek.github.io/pharo/pharo.html > > Cheers, > -- Pavel Cool. I had to use Ctrl-Click to get a menu. Keyboard shortcuts also don't seem to work (Ctrl based). GT Inspectors also fail. Sven

May 21, 2018

Re: [Pharo-dev] Pharo 7 on SqueakJS (demo)

by Tudor Girba

Great work! Doru -- www.tudorgirba.com "Every thing has its own flow" > On 21 May 2018, at 13:16, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: >> Hi, >> >> with some tweaks mostly related to FFI and fonts, we are able to run Pharo >> 7 on SqueakJS VM. >> >> Do not expect blazing performance. Currently, it is about two orders of >> magnitude slower than the native VM. >> >> https://pavel-krivanek.github.io/pharo/pharo.html >> >> Cheers, >> -- Pavel >> >> > > Cool. It works on my phone. > > Stephan > > >

May 21, 2018