- Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20152

by StÃ©phane Ducasse

20152 ----- - Issue 6105: Spec version 1.0 Thanks Benjamin van Ryseghem . http://code.google.com/p/pharo/issues/detail?id=6105

June 22, 2012

[Pharo-project] How to contribute to Pharo book

by Torsten Bergmann

How can we expect people to contribute to the collabroactive book when the section on "how to contribute" is empty? http://book.pharo-project.org/book/Contribute/ContributeToPharoBook Bye T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

June 22, 2012

Re: [Pharo-project] New System Progress Bar

by phil＠highoctane.be

What about a Progressing Trait? 2012/6/22 Igor Stasenko <siguctua(a)gmail.com> > btw, about human readable.., > i don't understand, why we don't have something as simple as: > > collection do: [... ] showingProgress: 'Processing collection' > (1 to: 100) do: [ ...] showingProgress: 'Processing ' > > 1 to: 100 do: [ ...] showingProgress: 'Processing ' > > i don't care what happens inside, but this interface is IMO much simpler > and straightforward: > a user just adds showingProgress: at the end, and voila, his silent block > now showing a progress. > > -- > Best regards, > Igor Stasenko. > > -- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

June 22, 2012

[Pharo-project] New VMs at http://www.mirandabanda.org/files/Cog/VM/VM.r2559/

by Eliot Miranda

http://www.mirandabanda.org/files/Cog/VM/VM.r2559/ CogVM binaries as per VMMaker.oscog-eem.163/r2559. Make wakeHighestPriority filter-out zombie processes; fixes Newspeak/Glue crash. Add -blockonerror flag to Unix & Mac VMs to allow attaching gdb on error/segv. Make the sigsegv handler catch SIGILL and SIGBUS on Unix and Mac. Add 64-bit file support to linux builds. Fix sqUnixX11.c ClipChildren to ClipByChildren. -- best, Eliot

June 22, 2012

[Pharo-project] #assert:equals:

by Sean P. DeNigris

This pattern is common in our tests: "self assert: a = b." I much prefer "self assert: a equals: b." It makes it easier to diagnose failing tests, especially if a or b are expressions with side-effects. Do you agree? Sean -- View this message in context: http://forum.world.st/assert-equals-tp4636050.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 22, 2012

[Pharo-project] Translating FileDirectory et al to FileSystem

by Sean P. DeNigris

We're getting there! I can't believe how much effort and progress there is already. One thing I've been noticing... when porting DirectoryEntry and subclasses to FileSystemDirectoryEntry, #name should be translated to #basename (otherwise, you get 'Directory Entry: ...', not the filename). Some of the updates (several authors) are going to have to be re-fixed because of this (I nabbed a few already). Also, FileDirectory>>pathName should become #fullName (which incidentally is pretty safe because FileDirectory>>fullName does the same thing). Cheers, Sean -- View this message in context: http://forum.world.st/Translating-FileDirectory-et-al-to-FileSystem-tp46360… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 22, 2012

Re: [Pharo-project] badDirectoryPath

by Sean P. DeNigris

It seems like the primitive is not returning enough context. badDirectoryPath is a catch-all for any error. For example, if you send #entries to aFileReference on a directory where you don't have enough permissions, you get #badDirectoryPath. Besides being misleading - the path is not really "bad" - it's hard to deal with the error because it's so general. For example, DiskStore>>directoryAt:ifAbsent:nodesDo: has a bug (http://code.google.com/p/pharo/issues/detail?id=6122) ... entry := Primitives lookupEntryIn: encodedPathString index: index. entry = #badDirectoryPath ifTrue: [ ^ absentBlock value ]. ... So if the entry exists but the primitive fails (e.g. not enough permissions), the absentBlock is evaluated. It's easy enough to fix, but how would you signal a helpful error? Cheers, Sean -- View this message in context: http://forum.world.st/badDirectoryPath-tp4635913p4636046.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 22, 2012

Re: [Pharo-project] New System Progress Bar

by Igor Stasenko

btw, about human readable.., i don't understand, why we don't have something as simple as: collection do: [... ] showingProgress: 'Processing collection' (1 to: 100) do: [ ...] showingProgress: 'Processing ' 1 to: 100 do: [ ...] showingProgress: 'Processing ' i don't care what happens inside, but this interface is IMO much simpler and straightforward: a user just adds showingProgress: at the end, and voila, his silent block now showing a progress. -- Best regards, Igor Stasenko.

June 22, 2012

Re: [Pharo-project] Where is the PBE VM?

by Sven Van Caekenberghe

On 21 Jun 2012, at 22:43, Camillo Bruni wrote: >>> I am seriously considering including the "Metacello Scripting API doc"[3] as the class comment for the Metacello class, but you have to admit that [3] is more readable than [4]. > > but it still reads fairly well even in the plain text format :) > >>> BTW, Markdown isn't the only markup syntax[5]...supporting one of the many would be sufficient.. > > indeed, I am somehow torn towards MarkDown (totally arbitrary choice I guess). > Unless someone comes up with a very convincing argument I'd stick with markdown :) I love Markdown as well: it is very simple, it remains readable as source text and it renders well to HTML. Sven

June 21, 2012

Re: [Pharo-project] Where is the PBE VM?

by Camillo Bruni

>> along these lines is anyone working on a Markdown[1] formatter for Pharo? PetitMarkdown <http://ss3.gemstone.com/ss/petitmarkdown.html> Yes I patched the existing parser to be more or less useful. but it was far from complete plus the old design did not really permit for the full markdown syntax :/ so damien started a new prototype which parses the basic blocks first and then goes into details. >> I am probably notorious for missing class comments, but I am more motivated to write class comments if I can produce nicely formatted comments[2]. so far igor used our old parser to create the NativeBoos documentation filled with interactive links to methods and classes plus decent formatting for source code and titles >> I am seriously considering including the "Metacello Scripting API doc"[3] as the class comment for the Metacello class, but you have to admit that [3] is more readable than [4]. but it still reads fairly well even in the plain text format :) >> BTW, Markdown isn't the only markup syntax[5]...supporting one of the many would be sufficient.. indeed, I am somehow torn towards MarkDown (totally arbitrary choice I guess). Unless someone comes up with a very convincing argument I'd stick with markdown :)

June 21, 2012