[Pharo-project] FileDirectory <> FSFileSystem

Camillo Bruni camillobruni at gmail.com
Sat Aug 11 01:50:13 CEST 2012


hi dale,

digesting your word flow right now :P...
I don't think I will touch a computer this weekend so I probably take a look at
it on monday to make the two things work...

just to clarify what I intend to do:
- update FS in 1.4 so we have all the "modern" features
- provide an optionally loadable FileDirectory stub in 2.0

I hope like that migration should become easier, since you can simply load code in 2.0
and slowly start calling FileReference methods on the FileDirectory entries.
My FileDirectory wrapper in 2.0 is simply a subclass of FileReference, being polymorphic
here, I think, should really ease the migration task.

best
cami

On 2012-08-10, at 19:15, Dale Henrichs <dhenrich at vmware.com> wrote:

> Cami,
> 
> turns out that #readStreamDo: was added for FileTree in Pharo1.x so adding it doesn't need to be part of the base ...
> 
> #name would then be the only compatibility method ... I can add that one as an extension, too.
> 
> Dale
> 
> ----- Original Message -----
> | From: "Dale Henrichs" <dhenrich at vmware.com>
> | To: Pharo-project at lists.gforge.inria.fr
> | Sent: Friday, August 10, 2012 8:39:18 AM
> | Subject: Re: [Pharo-project] FileDirectory <> FSFileSystem
> | 
> | Cami,
> | 
> | Despite not being able to load your working version in Pharo-1.4 I am
> | making progress:). I've created a Grease-like layer for FileTree
> | that papers over the differences between FileDirectory and
> | FileSystem (there is no common protocol between the two at all:)...
> | 
> | I am now porting the FileSystemDirectoryEntry/DirectoryEntry code and
> | it would be _extremely convenient_ if FileSystemDirectoryEntry were
> | more compatible with DirectoryEntry. In my case the two methods:
> | #name and #readStreamDo: would save me a ton of work.
> | 
> | I can add them as extension methods for FileTree (and will for the
> | time being). #readStreamDo: is just plain missing and #name is an
> | obvious concession to portability...
> | 
> | Let me know whether you think these two method will be included in
> | Pharo-2.0 or not.
> | 
> | Dale
> | 
> | ----- Original Message -----
> | | From: "Camillo Bruni" <camillobruni at gmail.com>
> | | To: Pharo-project at lists.gforge.inria.fr
> | | Sent: Friday, August 10, 2012 1:56:37 AM
> | | Subject: Re: [Pharo-project] FileDirectory <> FSFileSystem
> | | 
> | | 
> | | On 2012-08-10, at 01:10, Dale Henrichs <dhenrich at vmware.com> wrote:
> | | 
> | | > Cami,
> | | > 
> | | > If you can let me know where to find your new FS code, I can take
> | | > it for a spin ...
> | | > 
> | | > I've already spent time inventing a Grease-like layer that I can
> | | > use with FileDirectory and FileSystem, but if your FileDirectory
> | | > will be available and will fulfill my needs I can toss out the
> | | > work I've done so far ...
> | | > 
> | | > I just ask that if you make up your minds once and for all here
> | | > ...
> | | > I don't want to port FileTree to Pharo-2.0 more than twice (as I
> | | > will tossing the work that I've put into porting over the last
> | | > two
> | | > days...)
> | | > 
> | | > Dale
> | | 
> | | my preliminary version is here:
> | | 
> | | http://smalltalkhub.com/mc/dh83/fisleg/main
> | | 
> | | I didn't have time to test it though ;)
> | | 
> | 
> | 
> 




More information about the Pharo-project mailing list