November 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] [OT] Phrase about Smalltalk and Ruby
by Mariano Martinez Peck Nov. 16, 2010

Nov. 16, 2010

Hi all. I remember a phrase someone said few months ago and it was something like "I kew Smalltalk was going to reborn, but I didn't know it was going to be called Ruby". Do you remember how exactly the phrase was? do you know the name of the author? thanks Mariano

4 4

[Pharo-project] permutations / combinations implementation
by Tudor Girba Nov. 16, 2010

Nov. 16, 2010

Hi, Is there an implementation of permutations and combinations of a collection? Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

3 2

[Pharo-project] Should blocks passed into Metacello methods like #for:do: return spec?
by jaayer Nov. 16, 2010

Nov. 16, 2010

Concerning Metacello's block-accepting methods, should the blocks passed in always return spec? I ask because some sends in the image pass in blocks where the last message sent is yourself to "spec", making that the return value of the block, while other blocks just fall off at the end without explicitly returning spec. Is there a reason why one should be preferred over the other?

2 1

[Pharo-project] OSProcess
by Facundo Vozzi Nov. 16, 2010

Nov. 16, 2010

Hi, I loaded OSProcess 4.3.11 on Pharo-1.1.1-dev10.09.1.image but its tests are almost all red. Do you know if 4.3.11 if the right version for Pharo 1.1.1? Thanks you, Facundo

2 4

[Pharo-project] [ANN 1.2] pre-built #12241
by Marcus Denker Nov. 16, 2010

Nov. 16, 2010

https://gforge.inria.fr/frs/download.php/27956/PharoCore-1.2-12241.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3252 in pharo: [Repackage] "Announcements" should be well structured
by pharo＠googlecode.com Nov. 16, 2010

Nov. 16, 2010

Status: Fixed Owner: Torsten....(a)astares.de CC: stephane.ducasse New issue 3252 by Torsten....(a)astares.de: [Repackage] "Announcements" should be well structured http://code.google.com/p/pharo/issues/detail?id=3252 Pharo 1.2a 12235 After an IRC discussion with Alexandre and Stef yesterday we agreed that it would be good to start working on cleaning up/organizing the packages and get better structure into the system. According to Stef we should just start and see how it goes. We will use the seaside naming convention: http://code.google.com/p/seaside/wiki/PackageNaming and I hope we can - keep tests separated but close to the code - provide a documentation/help package - document - enhance tests I will start with the announcememt framework: Install the two changesets. It documents some classes, recategorizes the tests, provide additional tests and provide a new help book. After that you have - a changed package "Announcements-Core" since I started to document - a changed package "Tests" since tests are now repackaged close to the code - a new package "Announcements-Tests-Core" => this has to be SAVED - a new package "Announcements-Help" => this has to be SAVED Open the Monticello browser to see that. If you open the help browser you will also see a new book about the framework. I dont provide a slice since I think it is easier for the integrators to use the changesets and later create the new mcz's. Attachments: 01 Recategorize.cs 796 bytes 02 Enhance.cs 9.3 KB

1 5

[Pharo-project] Monticello package names
by Max Leske Nov. 16, 2010

Nov. 16, 2010

Hi This is probably known but I figured I'd report it. Just in case. First of all, I couldn't figure out how to actually remove a package from Monticello. Unloading it simply emptied it but it would still show up in the list. Would be nice to have that. Now to the actual problem: suppose I have a package named 'FooBar'. Now I want to rename that package to 'Foobar'. I encountered the following things while trying to do this: creating a new package 'Foobar' does nothing. The old package stays in the list but I get no notification about what went wrong. trying to load the old package with the new name from Sqeuaksource through Gofer fails: Gofer new squeaksource: 'TheFoo'; package: 'Foobar'. I think this is the correct behaviour. creating a new package named 'Foobar' in a fresh image (so that the old package is not loaded in Monticello) and trying to save it to Squeaksource results in a notification telling me that the package I want to create already exists (it's messing it up with the old package). Cheers, Max

2 1

[Pharo-project] [ANN] Smalltalk Screencast
by Davide Varvello Nov. 15, 2010

Nov. 15, 2010

Hi! I've two news for this list: 1) It's actually available my screencast on Smalltalk, you can find it here: http://thinkcode.tv/catalog/introduction-to-smalltalk/ 2) But you can have it for free if you look carefully at my timeline on twitter at @Varvello or at @ThinkCodeTV Enjoy the show. Davide -- View this message in context: http://forum.world.st/ANN-Smalltalk-Screencast-tp3043919p3043919.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

Nov. 15, 2010

12241 ----- - Issue 3251: Accept a change when editing a help text gives MNU. Thanks Torsten Bergmann. - Issue 3252: [Repackage] Announcements package should be well structured. Thanks Torsten Bergmann. Stef

1 0

Nov. 15, 2010

On Nov 15, 2010, at 3:59 PM, Ralph Boland wrote: > In Squeak SequenceableCollection>>permutationsDo: will apply a block > to each permutation > of a collection. I assume it is also in Pharo. > > I have a package CombinatorialGeneration that implements a number of > combinatorial > generation algorithms. I use it for generating large numbers of test > cases. It's about > a man month of work from being ready to release. Then, based on > feedback, I will > likely have more work to do before it is production ready. It uses > some code that as > far as I know is not supported in Pharo including the generators code > added by Andreas > (? Sorry I forget his last name but it is a short name). If you find it I would like to know it :) > > Hope that helps. > > Ralph Boland >

1 0