> On 24 Jun 2016, at 14:36, Esteban Lorenzano <[email protected]> wrote: > > so, pharo-local will be. > but regular convention is to store this kind of data into a hidden directory > (hence it would be .pharo-local, maybe)… but I understand the opposition I > will let it visible and we can re-check later.
My hero! :) > > now, tool makers, please take into account the new > > FileLocator localDirectory > > Esteban > > ps: and yes, I’m adding a setting so you can modify default local directory :) > >> On 24 Jun 2016, at 11:35, Tudor Girba <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi, >> >>> On Jun 23, 2016, at 10:18 PM, stepharo <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> What is the difference between play-cache play-stash >> >> - play-cache is populated automatically when you work in the playground. >> - play-stash stores only the pages that you gave concrete names to. You can >> double click on the tab with the name of a page and you can give it another >> name than Untitled. In this case, the file is copied in the play-stash >> folder and you can search for it by name. For example, using this mechanism >> you can name a script that you use for loading a piece of code and find it >> from spotter. >> >> Cheers, >> Doru >> >> >>> Stef >>> >>> >>> Le 23/6/16 à 17:22, Esteban Lorenzano a écrit : >>>> Hi, >>>> >>>> Since some time I’ve seen growing the amount of files/directories >>>> generated when running Pharo. Up to Pharo 2.0, we had just this: >>>> >>>> Pharo.image >>>> Pharo.changes >>>> PharoDebug.log >>>> pharo-cache >>>> >>>> now we have: >>>> >>>> Pharo.image >>>> Pharo.changes >>>> PharoDebug.log >>>> pharo-cache >>>> epicea-sessions >>>> play-cache >>>> play-stash >>>> >>>> it does not looks like much, but I think this does not looks professional >>>> (we take too much from user space). So I proposed (and implemented) a >>>> “concentrator” directory: >>>> >>>> Pharo.image >>>> Pharo.changes >>>> ./pharo >>>> … and everything for “pharo working internally” here >>>> >>>> then users have again control about what they have along with the image >>>> (this allows to some nice strategies too, when we want a version that does >>>> not pollutes the file dir). >>>> >>>> of course, this idea follows other developing spaces, where things are >>>> stored in same fashion way… for example in eclipse for java they store all >>>> eclipse data under .workspace directory. >>>> >>>> so, please note that this is NOT user space… regular pharo users will >>>> store his files along with the image, for instance filetree repositories… >>>> something like: >>>> >>>> Pharo.image >>>> Pharo.changes >>>> .pharo/ >>>> voyage/ >>>> punqlite/ >>>> etc. >>>> >>>> well… I will commit a SLICE with the changes soon (is not a hard change at >>>> all). >>>> >>>> But then: >>>> >>>> is ./pharo a good name? >>>> will this work? >>>> >>>> Esteban >>>> >>> >>> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> www.feenk.com <http://www.feenk.com/> >> >> "Every thing should have the right to be different." >
