[Pharo-dev] Should we always put application file paths into FileLocator?
guillermopolito at gmail.com
Tue Oct 3 06:04:52 EDT 2017
Yes yes yes
On Fri, Sep 29, 2017 at 3:58 PM, Stephane Ducasse <stepharo.self at gmail.com>
> Hi denis
> I like it!.
> On Fri, Sep 29, 2017 at 10:31 AM, Denis Kudriashov <dionisiydk at gmail.com>
> > Hi.
> > Many times I was trying to find "global" files of some packages in
> > 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
> > 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
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* <http://guillep.github.io>
*Phone: *+33 06 52 70 66 13
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev