June 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Some Nautilus feedback
by Torsten Bergmann June 22, 2012

June 22, 2012

Sean P. DeNigris wrote: >Maybe I'm missing something... you're saying you like that when you >double-click on a new item, you end up with two browsers open on that item?! Sorry for the confusion. Forget my last comment on this. Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

1 0

[Pharo-project] Help "migrating" from classic streams to XStreams
by Mariano Martinez Peck June 22, 2012

June 22, 2012

Hi guys. We are developing Fuel with Martin Dias. Fuel is a binary serializer similar to Parcels. More info in http://rmod.lille.inria.fr/web/pier/software/Fuel For the moment, we are using the "classic" streams we want to give it a try to XStreams. My knowledge on streams is very little, so if someone can give me a hint I would really appreciate it. What I want to do right now is an adaptor of XStreams to classic stream. I mean, I want to create custom subclasses of XTFileWriteStream and XTFileReadStream that implements the same API from classic streams that we use in Fuel. And the implementations of such methods will do just a "self something" where something is the way of doing that in XStreams. So, the following is the protocol we use in Fuel for streams, and what I would love to know is the associated way to do it it XStreams. The left is classic streams, and after the "->" it is XStreams: *Reading:* nextNumber: -> ?? nextPutAll: -> write: nextStringPut: -> ?? nextPut: -> put: nextNumber:put: -> ?? nextWordPut: -> ?? *Writing: * nextNumber: -> ?? next: -> read: nextString -> ?? next -> get nextWord -> ?? Thanks a lot in advance, -- Mariano http://marianopeck.wordpress.com

3 6

[Pharo-project] New System Progress Bar
by Sean P. DeNigris June 22, 2012

June 22, 2012

To help explain the changes, here's a snippet from the fix to "Issue 6099: Deprecate #value: for system progress (was red cross during updates)" (http://code.google.com/p/pharo/issues/detail?id=6099) The API (see SystemProgressItemMorph) is not set in stone, but it's already much less confusing than the old pseudo-class implementation. Ultimately, I'd like to move to announcements instead of exceptions to signal progress, and decouple the progress model/view - maybe just [un]registering the progress morph to enable/disable. The slice in the inbox for this issue should fix the "red cross during updates" problem... MOTIVATION: The old system progress worked like this (for example)... SystemProgressMorph show: 'Doing...' from: 1 to: 100 during: [ :bar | 1 to: 100 do: [ :x | bar value: x. bar value: 'On iteration ', x asString. (Delay forMilliseconds: 20) wait "Just to slow it down so we can see what's going on" ] ]. * The work block ([ :bar | ... ] above) would accept one argument * That argument (:bar above) would be a block, that would act as a pseudo-class. Depending on what was passed to #value:, it would perform different functions. Two are illustrated above: - #value: aNumber; where aNumber is between the min and max of the progress range -> Set the bar's current progress mark to that position. For example, 'bar value: 50' above would show the operation half complete - #value: aString -> Set the label of the progress morph to aString This was very confusing, so we created a real class, SystemProgressItemMorph, which now gets passed to the work block, and has a real API. So, for example, the following becomes: SystemProgressMorph show: 'Doing...' from: 1 to: 100 during: [ :bar | 1 to: 100 do: [ :x | bar current: x. bar label: 'On iteration ', x asString. (Delay forMilliseconds: 20) wait "Just to slow it down so we can see what's going on" ] ]. As you can see, '#value: newValue' has become '#current: newValue', and '#value: newLabel' has become '#label: newLabel'. One wrinkle is that some users were passing a nil-like block instead of the the pseudo-class to suppress the system progress bar. For example: informUserDuring: aBlock aBlock value: [:string | ]. Above, [:string | ] would now cause a DNU when sent, for example, #current:, which obviously blocks don't understand. So, these cases were changed like so: informUserDuring: aBlock aBlock value: DummySystemProgressItem new. Where DummySystemProgressItem simply ignores all messages without signaling an error -- View this message in context: http://forum.world.st/New-System-Progress-Bar-tp4635912.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

7 12

[Pharo-project] [update 2.0] #20156
by StÃ©phane Ducasse June 22, 2012

June 22, 2012

20156 ----- - Issue 6131: Code Completion on TextModel. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=6131 - Issue 6127: Switching a pharo theme gives a MNU FileReference>>self. Thanks Tortsen B. http://code.google.com/p/pharo/issues/detail?id=6127

1 0

[Pharo-project] could metacello be hosted on ss3 or smalltalkhub or not load configurationOfHelp?
by Torsten Bergmann June 22, 2012

June 22, 2012

Stef wrote: >because right now we cannot load configurations because it requires >configuration of Help and >squeaksource is done. >It would be good to have a small version of metacello just loading the bare >minimum. to Dale: Especially since "configuration of Help" is not required anymore. Help system is in Pharo and Squeak included. A "core" without help would be good Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

3 4

[Pharo-project] Cincom Smalltalk Team is hiring!
by mkobetic＠gmail.com June 22, 2012

June 22, 2012

We're looking for experienced developers with passion for Smalltalk. We're especially interested in candidates that have experience relevant to VM development, or GUI/Tools development. Following link provides information on how to find the descriptions of the openings and how to apply: http://www.cincomsmalltalk.com/main/2012/05/looking-for-a-few-good-smalltal…

1 0

[Pharo-project] Some Nautilus feedback
by Torsten Bergmann June 22, 2012

June 22, 2012

>Cool! I didn't know about that. One thing though... since the original >browser changes to the clicked-on item also, I don't understand the purpose >of this feature. It seems like it'd be much more valuable to leave the first >browser on the current selection and open a new browser on the >double-clicked item. Its better to have an option/setting "double Click Opens new Browser" for that since I like the current way Bye T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

2 1

[Pharo-project] #assert:equals:
by Sean P. DeNigris June 22, 2012

June 22, 2012

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.

6 9

[Pharo-project] Concatenation
by Torsten Bergmann June 22, 2012

June 22, 2012

Try: 1. 'P' , 'haro' 2. #P , 'haro' 3. $P , 'haro' in Pharo, Squeak and Dolphin Number 3 crashes with an MNU in VW and SmalltalkMT Number 2 and 3 crash with an MNU Just wonder why ST's handle case 2 differently Bye T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

3 2

June 22, 2012

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

2 1