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

FileSystem inconsistency

by StÃ©phane Ducasse

Hi I'm doing a pass on the FileSystem chapter (yes you know the documentation that nobody write but everybody wants to read), I'm updating/adding method comments and I get the following. paf does not exist (FileSystem disk workingDirectory / 'paf' ) delete. works without barking => may delete should barks to be consistent. (FileSystem disk workingDirectory / 'paf' ) deleteAll. barks! (FileSystem disk workingDirectory / 'paf' ) deleteAllChildren. barks! (FileSystem disk workingDirectory / 'paf' ) deleteIfAbsent: [ Warning signal: ' File does not exist' ] . works Stef

May 22, 2013

Re: [Pharo-dev] clean, please

by Igor Stasenko

On 22 May 2013 19:41, Paul Davidowitz <pdavidow(a)fastmail.fm> wrote: > Let's keep this clean, please! > keep clean what? -- Best regards, Igor Stasenko.

May 22, 2013

Re: [Pharo-dev] Ants we are smaller and smaller (was MC Filetree ..)

by Igor Stasenko

My own understanding where Pharo is heading in couple worlds can be described as follows: - make better smalltalk And making better sometimes means breaking eggs, and fixing something which is not broken. Sure thing, Pharo is not immune from wrong decisions and bad ideas (as any other project). But as long as visions stays same, bad things can be fixed and made better. -- Best regards, Igor Stasenko.

May 22, 2013

clean, please

by Paul Davidowitz

Let's keep this clean, please!

May 22, 2013

FileSystem ensureDeleted

by StÃ©phane Ducasse

(FileSystem disk workingDirectory / 'fooFolder3') ensureDirectory. (FileSystem disk workingDirectory / 'fooFolder3') ensureDeleted. works I get a primitive failure (FileSystem disk workingDirectory / 'fooFolder') createDirectory. (FileSystem disk workingDirectory / 'fooFolder' / 'fooInsidefoo') createDirectory. (FileSystem disk workingDirectory / 'fooFolder') ensureDeleted. because ensureDeleted is defined as ensureDeleted self deleteIfAbsent: []. and it would be better to define it as ensureDeleted self deleteAll. What do you think?

May 22, 2013

Re: [Pharo-dev] Ants we are smaller and smaller (was MC Filetree ..)

by phil＠highoctane.be

Well, yet another ant doing business w/ Pharo over here. I signed for the consortium and not for staying stuck in the eighties for sure. Phil On Wed, May 22, 2013 at 7:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Janko, > > On 22 May 2013, at 17:43, Janko MivÅ¡ek <janko.mivsek(a)eranova.si> wrote: > > > Dne 22. 05. 2013 16:14, piÅ¡e stephane ducasse: > > > >> PS: we are ants running around while elephants (python, ruby, > Javascripts) are passing close by. > >> Not making serious progress is death. > > > > We will be even smaller ants if we won't cooperate and listen to each > > other, and this thread is exact example, how listening don't go very > well. > > > > Also, sending messages like Pharo as Smalltalk-inspired instead of > > naming it proudly as Pharo Smalltalk is also a short-sighted, again > > making divisions instead of cooperation. Not to mention that outside > > world is confused, questioning if Pharo is or will stay Smalltalk at all. > > > > And ants we are smaller and smaller... > > It is actually the complete opposite: the Pharo project is responsible for > a lot of, if not most, renewed interest in Smalltalk. The last couple of > years, activity in the Pharo community has been increasing steadily. The > sheer amount of people and projects is proof of that. > > It is precisely due to the direction and actual steps taken by Pharo that > so many organisations and business are using it. And although the Pharo > vision is much more than that, the approach to moving forward, sometimes > taking ownership and responsibility and occasionally breaking backwards > compatibility, is what makes the current velocity of change possible. > > And there are so many more cool things in the pipeline. > > Sven > > > Janko > > > > > > -- > > Janko MivÅ¡ek > > Aida/Web > > Smalltalk Web Application Server > > http://www.aidaweb.si > > > > >

May 22, 2013

fileSystem copyAllTo: ??

by StÃ©phane Ducasse

(FileSystem disk workingDirectory / 'fooFolder') ensureDelete. (FileSystem disk workingDirectory / 'pif' ) ensureFile. (FileSystem disk workingDirectory / 'fooFolder') ensureDirectory. (FileSystem disk workingDirectory / 'pif' ) copyAllTo: (FileSystem disk workingDirectory / 'fooFolder'). It barks and I do not why even with (FileSystem disk workingDirectory / 'fooFolder') ensureDelete. (FileSystem disk workingDirectory / 'pif' ) ensureFile. (FileSystem disk workingDirectory / 'fooFolder') ensureDirectory. (FileSystem disk workingDirectory / 'pif' ) copyAllTo: (FileSystem disk workingDirectory / 'fooFolder').

May 22, 2013

could we rename ensureDeleted into ensureDelete?

by stephane ducasse

Because I do not understand why we use paste suddenly?

May 22, 2013

Re: [Pharo-dev] MC Filetree -- missing FiletreeURL ?

by Sven Van Caekenberghe

Frank, On 22 May 2013, at 14:55, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 22 May 2013 13:44, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >> On 2013-05-22, at 14:36, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> >>> On 22 May 2013 13:20, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> >>>> On 2013-05-22, at 14:02, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>> >>>>> On 22 May 2013 12:49, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>>>>>>> >>>>>>>> ./pharo Pharo.image config filetree://`pwd`/../src/ >>>>>>>> >>>>>>>> Fails on trying to execute #mcRepositoryAsUser:withPassword: on a GenericUrl >>>>>>>> instance inside Gofer. >>>>>>> >>>>>>> Yep, I'd agree with your assessment. Has Pharo forked Gofer, or does >>>>>>> it still use Lukas Renggli's repository? >>>>>> >>>>>> We forked it. We cannot built a part of our infrastructure on a project that can vanished in nature. >>>>> >>>>> Well. What I should have asked was "have you cloned the repository >>>>> with the intention of pushing improvements upstream, or have you >>>>> forked the project with no intention of pushing changes upstream?" >>>> >>>> well, check on how much we changed in detail and them come back. >>> >>> Sorry, was that supposed to be an answer? I must go find out how much >>> work you've done before guessing whether you've forked and abandoned >>> upstream? >> >> abandon or progress that's the question here. > > That's a false dichotomy. There's a middle path, where you do the MC > equivalent of a pull request. Now there's something useful to aim for: > GitHub works so very, very well because it's utterly trivial to make > upstream repositories know you have improvements lying around. Because > fragmentation of your committer base _does not help you_ in the long > run. > > Now if the upstream maintainer _dies_, sure, that's a different story. > >>> Like I said: What I want to know is this: if I want to make a change >>> to infrastructure common to multiple Smalltalks, does Pharo expect me >>> to submit special unique snowflake additions to Pharo AND to upstream? >> >> well if you expect us to push anything upstream then have a look at the >> massive amount of changes that happened since pharo 1.0. > > I don't care about Pharo 1.0 in the context of this discussion. I care > about one particular package, one that should have no UI elements in > it or similar nasty sources of entanglement. (I have attempted to port > quite a few Pharo packages to Squeak. Lack of separation between UI > and core functionality has been the only reason I've had to abandon a > port, thus far.) And certainly Gofer as it's pulled in via Metacello > (er, which one? The upstream one, not Pharo's fork of same) works fine > in Pharo, Squeak and Gemstone, and wherever else Metacello and Gofer > run. I should _not_ have to submit to more than one repository to add > functionality to Gofer. > >> There IS a reason pharo forked from squeak... > > I'm not pursuing this thread: it's my understanding that the fork was > largely political, and personal, and that's as far as I'm going to > talk about it. Well, you are wrong about the reasons for the fork, IMO. But it is a done deal. (See my answer to Janko). Now, for library/framework developers/maintainers it is hard to be compatible with different Smalltalk implementations. It is not impossible, but requires manpower, interest and will. Recently, only Fuel managed to do that (of the bigger projects). Sven PS: I occasionally read the Squeak mailing and I see the work that you are doing and it is impressive. Your attitude, approach and drive remind me of the many Pharo developers. I would not dream of convincing you, but IMHO you would fit perfectly in the Pharo community, where you would find more interaction and feedback - maybe you would even reconsider using Smalltalk in business. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

May 22, 2013

Re: [Pharo-dev] FileSystem moveTo:

by stephane ducasse

I imagine that (FileSystem disk workingDirectory / 'paf' ) moveTo: (FileSystem disk workingDirectory / 'fooFolder' / 'paf') I thought that it was inside somethingâ¦.. On May 22, 2013, at 7:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > How do I move a file inside a folder? > > (FileSystem disk workingDirectory / 'paf' ) ensureFile. > (FileSystem disk workingDirectory / 'fooFolder') ensureDirectory. > > (FileSystem disk workingDirectory / 'paf' ) moveTo: (FileSystem disk workingDirectory / 'fooFolder') > > this does not work? > What is the semantics of moveTo: (Yes I'm adding a comment)â¦.. > > Stef > > >

May 22, 2013