October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Never-ending computations and cmd-dot

by Guillermo Polito

I've been bitten by this dozens of times. The problem seems to be that a second UI process is created and thus the DNU exception is automatically resumed (indefinitely). Executing the following expression seems to remove the problem: UIManager default spawnNewProcess Still, I do not know the cause of it. On Wed, Sep 27, 2017 at 4:28 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi hernan > > Indeed it would be nice to have a solution for such case. Now we did > not look at it. > > Stef > > On Tue, Sep 26, 2017 at 5:58 AM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: > > Hi Tim, > > > > Yes, I am aware of such menu item. However I would like to know if > > someone is working in a more architectural solution. > > Because I guess this would imply to hook message sends into the main > > feedback loop. > > > > Cheers, > > > > HernÃ¡n > > > > > > 2017-09-25 20:08 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: > >> Its not quite what you are asking for, but if you right click on one of > those windows, someone has helpfully added a âclose all windows to rightâ > option, which does let you rapidly get rid of them. > >> > >> Tim > >> > >>> On 25 Sep 2017, at 23:16, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >>> > >>> Hi, > >>> > >>> Guys I have the situation you will recognize in the attached picture: > >>> A never-ending recursive computation which generate zillions of > >>> pre-debug windows when cmd-dot key is pressed. > >>> > >>> Is there any setting, or any way to put a monitor to detect that > >>> cmd-dot is creating too many windows so will pop-up just one or two? > >>> Maybe someone researched this issue, does it makes sense? > >>> > >>> Cheers, > >>> > >>> HernÃ¡n > >>> <rw.png> > >> > >> > > > > -- 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

Oct. 3, 2017

Re: [Pharo-dev] String Interpolation

by Guillermo Polito

Why not having an opal plugin? The opal plugin may read strings in the form: "lalala {some expression} lololo" and replace at compile time that by: "lalala {1} lololo" format { some expression } The thing to think about is what is the delimiter for {some expression}. - a too used one may break lots of existing code. - and we should escape it On Fri, Sep 29, 2017 at 5:40 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 29 Sep 2017, at 08:54, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > This solution will not work for environments without sources too where > names like t1, t2 are used for temporary variables. > > That is true. > > I often wonder why we can't keep at least the variables names, it would > not be that expensive. There was this problem with FFI that needed source > code access as well. It would also help the debugger and make the > decompiler more powerful. > > > Anyway, nice idea. > > > > -- Pavel > > > > Dne Ätvrtek 28. zÃ¡ÅÃ 2017 Sven Van Caekenberghe <sven(a)stfx.eu> > napsal(a): > > Hi, > > > > I got into a little office discussion about string interpolation as it > is done in different programming languages. > > > > In Pharo we have String>>#format: which is pretty nice. It works as > follows: > > > > | x y | > > x := 123. > > y := #foo. > > 'x={1} and y={2}' format: { x. y }. > > > > It is also possible to use a dictionary with keys, like this: > > > > | x y | > > x := 123. > > y := #foo. > > 'x={x} and y={y}' format: { #x->x. #y->y } asDictionary. > > > > But this is not true string interpolation as described in [ > https://en.wikipedia.org/wiki/String_interpolation ]. The idea is to > write the value generating expressions directly inside the strings. > > > > Since in Pharo we add features not by extending the syntax but by adding > messages I wondered if it could be done for string interpolation. The goal > is to make the following work: > > > > | x y | > > x := 123. > > y := #foo. > > 'It seems x equals {x} and y equals {y} while Pi is still {Float pi}' > interpolate. > > > > => 'It seems x equals 123 and y equals foo while Pi is still > 3.141592653589793' > > > > Here is the implementation I came up with: > > > > String>>#interpolate > > "Format the receiver by interpolating the evaluation of expressions > > in between curly brackets in the context of the sender as in the > following 3 oneline examples. > > 'Today is {Date today}' interpolate. > > | x | x := 123. 'x equals {x} and pi equals {Float pi}' interpolate. > > 'In {#strings} you can escape \{ by prefixing it with \\' interpolate." > > > > | senderContext | > > senderContext := thisContext sender. > > ^ self class new: self size streamContents: [ :out | | stream | > > stream := self readStream. > > [ stream atEnd ] whileFalse: [ | currentChar | > > (currentChar := stream next) == ${ > > ifTrue: [ | expression result | > > expression := stream upTo: $}. > > result := Compiler new > > evaluate: expression in: senderContext to: nil notifying: > nil ifFail: [ ^ nil ] logged: false. > > out nextPutAll: result asString ] > > ifFalse: [ > > currentChar == $\ > > ifTrue: [ stream atEnd ifFalse: [ out nextPut: stream next > ] ] > > ifFalse: [ out nextPut: currentChar ] ] ] ] > > > > It is a hack that could certainly be improved. And there is of course an > obvious security problem. > > > > Thoughts ? > > > > Sven > > > > > > > -- 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

Oct. 3, 2017

Re: [Pharo-dev] Iceberg - loading baseline

by Sean P. DeNigris

Peter UhnÃ¡k wrote > Don't forget to enable Metacello integration in settings. What does this setting do? I have been plugging along without it and haven't noticed any problemsâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 3, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Henrik Sperre Johansen

Denis Kudriashov wrote > Hi. > > Many times I was trying to find "global" files of some packages in system. > > For example do you know how to find epicea session logs? > There is class side method for this at EpMonitor: > > EpMonitor logsDirectory > > Is it easy to find when you never look at it? No. > > Do you know how to find sources file? There is message in Smalltalk > global: > > Smalltalk sourcesFile > > Is it easy to find? No. > > And there are many other examples. > > But if you read about FileSystem library. You know the common place where > to find well known files. It is FileLocator. > For example changes file is here: > > FileLocator changes. > > So my idea is to introduce kind of pattern, the good style, how to access > global application files: they should be in FileLocator as extensions. > Then it would be super easy to find files of any applications. > > What do you think? > > If it is good idea then we should fix current places in system to follow > this pattern. > > Best regards, > Denis -1 from me, for the same reasons we moved away from Framework Settings as extension methods on a central "Settings" class. Keep "globals" related to a package local to the package where they are used. Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 3, 2017

Sista alternate bytecodes + Java Bytecode ?

by Ben Coman

Just wondering about an exotic idea, with Sista facilitating alternate bytecodes (btw, is that multiple bytecode sets within one Image?), how feasible would it be to have the VM process Java bytecode? cheers -ben

Oct. 3, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Guillermo Polito

Could you write a blog post? :D - What is the good practice - extending FileLocator - managing paths in a platform independent way (what to extend for unix, mac, windows, default values for unknown platforms...) On Tue, Oct 3, 2017 at 12:52 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Ok. No objections yet. > I will prepare pull requests > > 2017-10-03 12:04 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> Yes yes yes >> >> On Fri, Sep 29, 2017 at 3:58 PM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> >>> Hi denis >>> >>> I like it!. >>> >>> Stef >>> >>> On Fri, Sep 29, 2017 at 10:31 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> > Hi. >>> > >>> > Many times I was trying to find "global" files of some packages in >>> system. >>> > >>> > For example do you know how to find epicea session logs? >>> > There is class side method for this at EpMonitor: >>> > >>> > EpMonitor logsDirectory >>> > >>> > Is it easy to find when you never look at it? No. >>> > >>> > Do you know how to find sources file? There is message in Smalltalk >>> global: >>> > >>> > Smalltalk sourcesFile >>> > >>> > Is it easy to find? No. >>> > >>> > And there are many other examples. >>> > >>> > But if you read about FileSystem library. You know the common place >>> where to >>> > find well known files. It is FileLocator. >>> > For example changes file is here: >>> > >>> > FileLocator changes. >>> > >>> > So my idea is to introduce kind of pattern, the good style, how to >>> access >>> > global application files: they should be in FileLocator as extensions. >>> > Then it would be super easy to find files of any applications. >>> > >>> > What do you think? >>> > >>> > If it is good idea then we should fix current places in system to >>> follow >>> > this pattern. >>> > >>> > Best regards, >>> > Denis >>> >>> >> >> >> -- >> >> >> >> 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 <+33%206%2052%2070%2066%2013> >> > > -- 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

Oct. 3, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Denis Kudriashov

Ok. No objections yet. I will prepare pull requests 2017-10-03 12:04 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Yes yes yes > > On Fri, Sep 29, 2017 at 3:58 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi denis >> >> I like it!. >> >> Stef >> >> On Fri, Sep 29, 2017 at 10:31 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> > Hi. >> > >> > Many times I was trying to find "global" files of some packages in >> system. >> > >> > For example do you know how to find epicea session logs? >> > There is class side method for this at EpMonitor: >> > >> > EpMonitor logsDirectory >> > >> > Is it easy to find when you never look at it? No. >> > >> > Do you know how to find sources file? There is message in Smalltalk >> global: >> > >> > Smalltalk sourcesFile >> > >> > Is it easy to find? No. >> > >> > And there are many other examples. >> > >> > But if you read about FileSystem library. You know the common place >> where to >> > find well known files. It is FileLocator. >> > For example changes file is here: >> > >> > FileLocator changes. >> > >> > So my idea is to introduce kind of pattern, the good style, how to >> access >> > global application files: they should be in FileLocator as extensions. >> > Then it would be super easy to find files of any applications. >> > >> > What do you think? >> > >> > If it is good idea then we should fix current places in system to follow >> > this pattern. >> > >> > Best regards, >> > Denis >> >> > > > -- > > > > 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 <+33%206%2052%2070%2066%2013> >

Oct. 3, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Denis Kudriashov

I implement query for annotations of concrete class. So right now if you will do MyFrameworkAnnotation registeredInstances it will return only MyFrameworkAnnotation instances. It will not include any MyConcreteAnnotation instance. We can change this part if it is better to work with all subclasses. Or we can introduce another message like registeredSubInstances with consistency to general allSubInstances method, Another detail about inheritance: subclasses inherit superclass annotations and override them. 2017-10-03 12:10 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Ok, I'm back from vacations so I'll give a comment other than what I did > :P. > > First I like it. > > Second, how does it work with respect to inheritance? I mean, if I have > for example: > > ClassAnnotation subclass: MyFrameworkAnnotation. > > And then > > MyFrameworkAnnotation subclass: MyConcreteAnnotation1. > MyFrameworkAnnotation subclass: MyConcreteAnnotation2. > > Can I query all my annotations or should do an isKindOf: by hand? > > On Fri, Sep 29, 2017 at 1:10 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> tx! >> >> On Fri, Sep 29, 2017 at 9:58 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >>> >>> 2017-09-28 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>>> I would not use meta because you would not write annotationAnnotations >>>> :) >>>> and annotations is meta by its name. >>>> >>>> classAnnotation is much better than metaAnnotation >>>> >>> >>> Done. >>> >>> >>>> >>>> Stef >>>> >>>> >>>> On Thu, Sep 28, 2017 at 5:40 PM, Denis Kudriashov <dionisiydk(a)gmail.com >>>> > wrote: >>>> >>>>> So I renamed it to ClassAnnotation with all related names. >>>>> >>>>> But I keep meta prefix in #metaAnnotations Class extension to avoid >>>>> general name: >>>>> >>>>> MyClass metaAnnotations >>>>> >>>>> You can check updated readme for details https://github.com/dio >>>>> nisiydk/ClassAnnotation >>>>> >>>>> 2017-09-26 17:31 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>>> >>>>>> ;) >>>>>> >>>>>> On Tue, Sep 26, 2017 at 1:28 PM, Ben Coman <btc(a)openinworld.com> >>>>>> wrote: >>>>>> >>>>>>> Shhh... The first rule of meta-club is we don't talk about meta-club. >>>>>>> >>>>>>> >>>>>>> cheers -ben >>>>>>> >>>>>>> >>>>>>> On Mon, Sep 25, 2017 at 11:09 PM, Guillermo Polito < >>>>>>> guillermopolito(a)gmail.com> wrote: >>>>>>> >>>>>>>> Why calling them meta-annotation and not just annotation? >>>>>>>> Annotations are in general already meta :) >>>>>>>> >>>>>>>> On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov < >>>>>>>> dionisiydk(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi. >>>>>>>>> >>>>>>>>> I glad to present one class package which introduces reusable >>>>>>>>> mechanism for first class annotations. >>>>>>>>> >>>>>>>>> The project can be found on github https://github.com/dion >>>>>>>>> isiydk/ClassMetaAnnotation. >>>>>>>>> And I tried to describe why it is needed in my blog >>>>>>>>> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >>>>>>>>> >>>>>>>>> And here is overview: >>>>>>>>> >>>>>>>>> Every annotation should be subclass of ClassMetaAnnotation. To >>>>>>>>> attach it to class you create new class side method which will return an >>>>>>>>> instance of the annotation. Method should be marked with pragma >>>>>>>>> #classMetaAnnotation: >>>>>>>>> >>>>>>>>> >>>>>>>>> MyClass class>>specialAnnotation >>>>>>>>> >>>>>>>>> <classMetaAnnotation> >>>>>>>>> >>>>>>>>> ^MySpecialAnnotation new >>>>>>>>> >>>>>>>>> >>>>>>>>> To query annotations from system there are two methods: >>>>>>>>> >>>>>>>>> 1) You can ask concrete annotation class for all declared >>>>>>>>> instances: >>>>>>>>> >>>>>>>>> MySpecialAnnotation declaredInstances >>>>>>>>> >>>>>>>>> 2) You can ask given class for all attached annotations: >>>>>>>>> >>>>>>>>> MyClass metaAnnotations >>>>>>>>> >>>>>>>>> Every annotation includes information about annotated class and >>>>>>>>> the selector of declaring method. >>>>>>>>> All annotations are cached. So it is cheap to query them. There >>>>>>>>> are extra messages to enumerate annotations using block. >>>>>>>>> >>>>>>>>> Now let's discuss it. I think it can be good addition for the >>>>>>>>> Pharo 7. Especially that it is very small code. >>>>>>>>> >>>>>>>>> Also I would like to thank Marcus who helps me realize this >>>>>>>>> concept in Commander and Calypso which I start simplify with this library. >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> Denis >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> 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 <+33%206%2052%2070%2066%2013> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > > > -- > > > > 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 <+33%206%2052%2070%2066%2013> >

Oct. 3, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Guillermo Polito

Ok, I'm back from vacations so I'll give a comment other than what I did :P. First I like it. Second, how does it work with respect to inheritance? I mean, if I have for example: ClassAnnotation subclass: MyFrameworkAnnotation. And then MyFrameworkAnnotation subclass: MyConcreteAnnotation1. MyFrameworkAnnotation subclass: MyConcreteAnnotation2. Can I query all my annotations or should do an isKindOf: by hand? On Fri, Sep 29, 2017 at 1:10 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > tx! > > On Fri, Sep 29, 2017 at 9:58 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2017-09-28 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >>> I would not use meta because you would not write annotationAnnotations :) >>> and annotations is meta by its name. >>> >>> classAnnotation is much better than metaAnnotation >>> >> >> Done. >> >> >>> >>> Stef >>> >>> >>> On Thu, Sep 28, 2017 at 5:40 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> >>>> So I renamed it to ClassAnnotation with all related names. >>>> >>>> But I keep meta prefix in #metaAnnotations Class extension to avoid >>>> general name: >>>> >>>> MyClass metaAnnotations >>>> >>>> You can check updated readme for details https://github.com/dio >>>> nisiydk/ClassAnnotation >>>> >>>> 2017-09-26 17:31 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>> >>>>> ;) >>>>> >>>>> On Tue, Sep 26, 2017 at 1:28 PM, Ben Coman <btc(a)openinworld.com> >>>>> wrote: >>>>> >>>>>> Shhh... The first rule of meta-club is we don't talk about meta-club. >>>>>> >>>>>> >>>>>> cheers -ben >>>>>> >>>>>> >>>>>> On Mon, Sep 25, 2017 at 11:09 PM, Guillermo Polito < >>>>>> guillermopolito(a)gmail.com> wrote: >>>>>> >>>>>>> Why calling them meta-annotation and not just annotation? >>>>>>> Annotations are in general already meta :) >>>>>>> >>>>>>> On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov < >>>>>>> dionisiydk(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hi. >>>>>>>> >>>>>>>> I glad to present one class package which introduces reusable >>>>>>>> mechanism for first class annotations. >>>>>>>> >>>>>>>> The project can be found on github https://github.com/dion >>>>>>>> isiydk/ClassMetaAnnotation. >>>>>>>> And I tried to describe why it is needed in my blog >>>>>>>> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >>>>>>>> >>>>>>>> And here is overview: >>>>>>>> >>>>>>>> Every annotation should be subclass of ClassMetaAnnotation. To >>>>>>>> attach it to class you create new class side method which will return an >>>>>>>> instance of the annotation. Method should be marked with pragma >>>>>>>> #classMetaAnnotation: >>>>>>>> >>>>>>>> >>>>>>>> MyClass class>>specialAnnotation >>>>>>>> >>>>>>>> <classMetaAnnotation> >>>>>>>> >>>>>>>> ^MySpecialAnnotation new >>>>>>>> >>>>>>>> >>>>>>>> To query annotations from system there are two methods: >>>>>>>> >>>>>>>> 1) You can ask concrete annotation class for all declared instances: >>>>>>>> >>>>>>>> MySpecialAnnotation declaredInstances >>>>>>>> >>>>>>>> 2) You can ask given class for all attached annotations: >>>>>>>> >>>>>>>> MyClass metaAnnotations >>>>>>>> >>>>>>>> Every annotation includes information about annotated class and the >>>>>>>> selector of declaring method. >>>>>>>> All annotations are cached. So it is cheap to query them. There are >>>>>>>> extra messages to enumerate annotations using block. >>>>>>>> >>>>>>>> Now let's discuss it. I think it can be good addition for the Pharo >>>>>>>> 7. Especially that it is very small code. >>>>>>>> >>>>>>>> Also I would like to thank Marcus who helps me realize this concept >>>>>>>> in Commander and Calypso which I start simplify with this library. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> Denis >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> >>>>>>> >>>>>>> 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 <+33%206%2052%2070%2066%2013> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > -- 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

Oct. 3, 2017

Re: [Pharo-dev] Should we always put application file paths into FileLocator?

by Guillermo Polito

Yes yes yes On Fri, Sep 29, 2017 at 3:58 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi denis > > I like it!. > > Stef > > On Fri, Sep 29, 2017 at 10:31 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > Hi. > > > > Many times I was trying to find "global" files of some packages in > system. > > > > For example do you know how to find epicea session logs? > > There is class side method for this at EpMonitor: > > > > EpMonitor logsDirectory > > > > Is it easy to find when you never look at it? No. > > > > Do you know how to find sources file? There is message in Smalltalk > global: > > > > Smalltalk sourcesFile > > > > Is it easy to find? No. > > > > And there are many other examples. > > > > But if you read about FileSystem library. You know the common place > where to > > find well known files. It is FileLocator. > > For example changes file is here: > > > > FileLocator changes. > > > > So my idea is to introduce kind of pattern, the good style, how to access > > global application files: they should be in FileLocator as extensions. > > Then it would be super easy to find files of any applications. > > > > What do you think? > > > > If it is good idea then we should fix current places in system to follow > > this pattern. > > > > Best regards, > > Denis > > -- 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

Oct. 3, 2017