July 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] About file.... (argh)

by StÃ©phane Ducasse

Thanks. this is why I propose a group to work on a new file library may be starting from GNU + rio interface + URI. This can be a good item for pharo milestone 2. I will start to collect information (such as this email, GNU library, ....) Stef On Jul 30, 2008, at 8:29 PM, Lukas Renggli wrote: >> because the interface of rio is looking good. > > I agree, and I think it Rio goes in the right direction. I have some > things to consider before including RIo in Pharo though: > > - I read everything mentioned about the Null pattern and checked its > use in Rio. This looks nice and probably makes sense in the context. I > don't believe however that something like that should be part of a > standard image. People won't understand it, beginners will be confused > and it is highly incompatible with any other Smalltalk dialect. > > - Rio prominently uses #doesNotUnderstand: for delegation (not only > for the Null implementation). In my opinion this is a big no-go for > any core-library. This looks like a design smell. It makes debugging > and code understanding unnecessarily hard. > > - Internally Rio uses string concatenation everywhere. For example to > get the parent directory the path is split into two parts and a new > object is created. What about paths that contain $/ as part of a > file-name? > > - Rio mixes meta-levels. For example the inst-vars 'recursive', > 'rename' and 'binary' (temporary navigation settings) are on a > completely different level than 'value' and 'stat' (the actual model > object). > > - Rio uses a string as the internal representation of the path (Why > not a chain of parent directories?). When opening a Smalltalk image on > a different platform a conversion is supposed to happen, however this > is not implemented as far as I can see. I think a correct > implementation will be complicated because for n platforms n^2 > conversion methods have to be provided. > > - Rio does not support relative paths. If you get the directory > relative to the default path it simply stores the full absolute path. > If I move the Smalltalk image around, Rio points to the wrong > location. > > - Rio uses several non-standard extensions that I don't know where > they are coming from. I run across: Stream>>#<< and Stream>>#, > > - Why copy the name of a Ruby framework? > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 31, 2008

Re: [Pharo-project] About file.... (argh)

by StÃ©phane Ducasse

Ok I will. Stef On Jul 30, 2008, at 7:28 PM, Lukas Renggli wrote: >> do you have some example of GNU because the interface of rio is >> looking >> good. After we can discuss implementation points. > > Paolos implementation is one of the best file-directory libraries I've > ever seen. It is fully extensible, and for example zip files can be > transparently navigated and edited like directories. As far as I know > this is similar to Rio. > > Unfortunately I didn't find any documentation. Have a look at the > implementation (File.st, FilePath.st, VFS.st, VFSZip.st) at > <http://tinyurl.com/6sb6fo>. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 31, 2008

Re: [Pharo-project] Remembering the last comment when saving a slice

by StÃ©phane Ducasse

Yes please do. This is good to fix the environment and stop to turn around. stef On Jul 30, 2008, at 2:25 PM, Lukas Renggli wrote: >> I could work on this... >> Anyone agree on this? > > That would be cool, indeed. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 31, 2008

Re: [Pharo-project] ugly code related to files management

by StÃ©phane Ducasse

excellent! I will have a look at that! Stef On Jul 30, 2008, at 2:06 PM, Alexandre Bergel wrote: > Hi! > > It is now the Issue #124 on google code. > I also propose some refactoring under the name SLICE- > FixingUglyCodeRelatedtoFiles > > In PharoInBox > > Cheers, > Alexandre > > On 30 Jul 2008, at 12:09, Alexandre Bergel wrote: > >> While browsing at referencer of FileDoesNotExistException, I >> discovered the following pattern that is used in many different >> places. I find this pretty ugly: >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> file := [fd readOnlyFileNamed: keysFileName] >> on: FileDoesNotExistException do:[:ex| nil]. >> file ifNil:[^self]. "no keys file" >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >> The use of exception is completely outwitted. >> >> I would rather write: >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> [file := fd readOnlyFileNamed: keysFileName] >> on: FileDoesNotExistException do: [:ex| ^ self]. >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >> If some of you agree, I will add an issue and fix where this occurs >> (e.g., CompiledMethod>>timeStamp, FileDirectory >> class>>retrieveMIMEDocument:, FileUrl>>retrieveContents, >> ResourceManager class>>loadResource: urlString, fromCacheFileNamed: >> fileName in: dir, ResourceManager class>>lookupCachedResource: >> cachedUrlString ifPresentDo: streamBlock, >> SecurityManager>>loadSecurityKeys) >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 31, 2008

Re: [Pharo-project] http://www.pharo-project.org/

by Adrian Lienhard

On Jul 31, 2008, at 09:15 , Marcus Denker wrote: > > On 30.07.2008, at 17:23, Alexandre Bergel wrote: > >> Hi! >> >> http://www.pharo-project.org/ is down... > > Did we ever configure the domain to point anywhere? Not as much as I > remember... no, not that I know. We could make it redirect to the Google project page until we have the web site, but I think its not critical since we don't have a product to sell yet. Adrian

July 31, 2008

Re: [Pharo-project] http://www.pharo-project.org/

by Marcus Denker

On 30.07.2008, at 17:23, Alexandre Bergel wrote: > Hi! > > http://www.pharo-project.org/ is down... Did we ever configure the domain to point anywhere? Not as much as I remember... -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

July 31, 2008

Re: [Pharo-project] About file.... (argh)

by Damien Cassou

On Wed, Jul 30, 2008 at 8:29 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > - Internally Rio uses string concatenation everywhere. For example to > get the parent directory the path is split into two parts and a new > object is created. What about paths that contain $/ as part of a > file-name? In Unix systems, $/ is the only character which can't be part of a file name. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

July 31, 2008

Re: [Pharo-project] About file.... (argh)

by Keith Hodges

> - Rio does not support relative paths. If you get the directory > relative to the default path it simply stores the full absolute path. > If I move the Smalltalk image around, Rio points to the wrong > location. > It should do... 'test/myFile' asRio should be a relative directory. 'test/myFile' asRio full should be an absolute directory. Keith

July 30, 2008

Re: [Pharo-project] About file.... (argh)

by Lukas Renggli

> because the interface of rio is looking good. I agree, and I think it Rio goes in the right direction. I have some things to consider before including RIo in Pharo though: - I read everything mentioned about the Null pattern and checked its use in Rio. This looks nice and probably makes sense in the context. I don't believe however that something like that should be part of a standard image. People won't understand it, beginners will be confused and it is highly incompatible with any other Smalltalk dialect. - Rio prominently uses #doesNotUnderstand: for delegation (not only for the Null implementation). In my opinion this is a big no-go for any core-library. This looks like a design smell. It makes debugging and code understanding unnecessarily hard. - Internally Rio uses string concatenation everywhere. For example to get the parent directory the path is split into two parts and a new object is created. What about paths that contain $/ as part of a file-name? - Rio mixes meta-levels. For example the inst-vars 'recursive', 'rename' and 'binary' (temporary navigation settings) are on a completely different level than 'value' and 'stat' (the actual model object). - Rio uses a string as the internal representation of the path (Why not a chain of parent directories?). When opening a Smalltalk image on a different platform a conversion is supposed to happen, however this is not implemented as far as I can see. I think a correct implementation will be complicated because for n platforms n^2 conversion methods have to be provided. - Rio does not support relative paths. If you get the directory relative to the default path it simply stores the full absolute path. If I move the Smalltalk image around, Rio points to the wrong location. - Rio uses several non-standard extensions that I don't know where they are coming from. I run across: Stream>>#<< and Stream>>#, - Why copy the name of a Ruby framework? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

July 30, 2008

Re: [Pharo-project] About file.... (argh)

by Lukas Renggli

> do you have some example of GNU because the interface of rio is looking > good. After we can discuss implementation points. Paolos implementation is one of the best file-directory libraries I've ever seen. It is fully extensible, and for example zip files can be transparently navigated and edited like directories. As far as I know this is similar to Rio. Unfortunately I didn't find any documentation. Have a look at the implementation (File.st, FilePath.st, VFS.st, VFSZip.st) at <http://tinyurl.com/6sb6fo>. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

July 30, 2008