Re: [Pharo-users] FLSerialization>>analysisStep too slow?

Sure, it's a great news that the leader could give me a hand. I came from Dolphin, not acquainted with pharo configuration, though I knew a lot that it could automize the loading and update. It depended upon Magritte3, Sandstone, and my packages. The store directory need to be changed in

Re: [Pharo-users] FLSerialization>>analysisStep too slow?

Well, it is just my intent to place related playgrounds, doc, help, and classes/methods, mophic, tool browser etc into domain object dbs of topics/playgrounds trees while exploring the image and studing/writing packages. It's just a convenient help and an working enviornment I made specifically

Re: [Pharo-users] Pharo Launcher name

+1 Envoyé de mon iPhone > Le 16 déc. 2017 à 20:32, Glenn Hoetker a écrit : > > I love the Pharo Launcher. But, I find it confusing to have an application > called “Pharo.app”. Nothing in that name suggests it is a launcher. It is > also very confusing to have an

Re: [Pharo-users] Pharo Launcher name

Le 17/12/2017 à 00:32, Glenn Hoetker a écrit : > I love the Pharo Launcher.  But, I find it confusing to have an > application called “Pharo.app”. Nothing in that name suggests it is a > launcher.  It is also very confusing to have an application called > “Pharo.app” next to one called

[Pharo-users] Pharo Launcher name

I love the Pharo Launcher. But, I find it confusing to have an application called “Pharo.app”. Nothing in that name suggests it is a launcher. It is also very confusing to have an application called “Pharo.app” next to one called “Pharo6.1.app” when they are very different things (at least

[Pharo-users] Athens error

Hi, With DrGeo built on image Pharo7.0-64bit-e41f921 Athens error shows up on the canvas (screenshot). The drgeo dev. environment based on the older Pharo7.0-64bit-f82fc36 image does not have this error with the same VM. The DrGeo build removes some pharo package but it is unlikely to

Re: [Pharo-users] Working directory

Now introducing a new name means that all the documentation, books, videos are obsolete. And this is a cost too. On Sat, Dec 16, 2017 at 5:03 PM, Alistair Grant wrote: > Hi Ben, > > On 15 December 2017 at 22:14, Ben Coman wrote: >> >> >> On 16

Re: [Pharo-users] Working directory

Hi Ben, On 15 December 2017 at 22:14, Ben Coman wrote: > > > On 16 December 2017 at 04:34, Cyril Ferlicot D. > wrote: >> >> Le 15/12/2017 à 21:24, Hilaire a écrit : >> > In P3: >> > >> > FileSystem disk workingDirectory >> > =>File @

Re: [Pharo-users] Working directory

On Sat, Dec 16, 2017 at 12:01 PM, Ben Coman wrote: > > > On 16 December 2017 at 16:02, Stephane Ducasse > wrote: >> >> Hi ben >> >> We should think about it. Indeed. >> Now about the names. I'm wondering if they cover well enough the >> situation.

Re: [Pharo-users] Working directory

On 16 December 2017 at 16:02, Stephane Ducasse wrote: > Hi ben > > We should think about it. Indeed. > Now about the names. I'm wondering if they cover well enough the situation. > In fact I would like to have imageDirectory (it exists but not in > FileSystem) and

Re: [Pharo-users] FLSerialization>>analysisStep too slow?

Do you want that I help you defining a configuration for your project? Stef On Sat, Dec 16, 2017 at 9:10 AM, Stephane Ducasse wrote: > Hi eno > > can you tell us what is TkIDE? > Because most of us are hobbysts the truth is in the eye of the beholder > :) > > Stef

Re: [Pharo-users] FLSerialization>>analysisStep too slow?

Hi eno can you tell us what is TkIDE? Because most of us are hobbysts the truth is in the eye of the beholder :) Stef On Tue, Dec 12, 2017 at 3:47 PM, Eno wrote: > > My package TkIDE relied on > object database, sandstone, to