- Pharo-dev - lists.pharo.org

[Pharo-project] changes necessary to make merging of squeak trunk in pharo possible
by Nicolas Cellier Aug. 28, 2009

Aug. 28, 2009

Name: Polymorph-Tools-Diff-nice.25 Author: nice Time: 27 August 2009, 10:50:11 pm UUID: c934f7e5-c68f-42c7-9e31-d61b12bfa16f Ancestors: Polymorph-Tools-Diff-stephane_ducasse.24 Made two changes to be able to merge squeak trunk in pharo Please review and update Polymorph

3 6

[Pharo-project] [ANN] Pharo-Kernel
by Pavel Krivanek Aug. 27, 2009

Aug. 27, 2009

Hi all, I've prepared a set of shrinking scripts and patches that create a headless image with only basic kernel classes from the Pharo-Core. The output image has about 2 MB. It is the bleeding edge project that should help in Pharo modularization and cleanup. It currently more or less corresponds to basic.image from the KernelImage so it doesn't include GUI, network support, Monticello etc., however SUnit and kernel tests are supported. For more information and downloads see http://code.google.com/p/pharo/wiki/PharoKernel Cheers, -- Pavel

6 7

[Pharo-project] Loading packages with Gofer and Flair
by Fernando olivero Aug. 27, 2009

Aug. 27, 2009

Hi, How can i specify post install actions when using Gofer and Flair protocol. If i implement SomePackageLoader>>#load, i can send the message #postInstall. SomePackageLoader >>load | config | self ensureFlairAndGofer. config := (Smalltalk at: #FLConfiguration) new. self allFor: config. config load. self postInstall. But i've also seen the FLoadable>>postLoadAction: method, but when i used i've get an erro with a description that it shouldnt be used. Thanks, Fernando

1 0

[Pharo-project] FW: New Pharo based on core 10418
by Schwab,Wilhelm K Aug. 27, 2009

Aug. 27, 2009

Damien, It wasn't hard, but I wonder whether I might have changed the default browser. Is there a way to determine the current setting for that? I will try to repeat the process later this AM. Bill -----Original Message----- From: Damien Cassou [mailto:damien.cassou@gmail.com] Sent: Thursday, August 27, 2009 6:04 AM To: Schwab,Wilhelm K Subject: Re: [Pharo-project] New Pharo based on core 10418 On Wed, Aug 26, 2009 at 8:31 PM, Schwab,Wilhelm K<bschwab(a)anest.ufl.edu> wrote: > Right clicking in the browsers gives the #isClassNode and then #isMethodNode walkbacks. Hi Bill, could you please detail me the process to reproduce? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

2 2

[Pharo-project] Preparing Pharo sprint at esug
by StÃ©phane Ducasse Aug. 27, 2009

Aug. 27, 2009

Hi guys ESUG is approaching really fast and I would like to come up with a set of actions for the sprint (we will revise them) I see two kinds of possible actions: towards 1.0 - cleaning and fixing 1.0 items -- cuis fonts -- pending bug fixes... - checking squeak fixes towards 1.1 - since we will meet physically we can meet and check next step item - Preferences/Setting with alain it would be good to check the status of the bug tracker and update it if we see missing items Stef

2 4

[Pharo-project] Compiler Notifications
by Lukas Renggli Aug. 27, 2009

Aug. 27, 2009

I "merged" the changes of Colin "The compiler now uses notifications to signal that a correctable error has been found in the method source, rather than interacting directly with the user" into the Pharo compiler. This was a bit tricky because the compiler is quite different and some classes are somehow called different, but it seems to work now. Also the tests pass. http://www.squeaksource.com/PharoInbox/CompilerTests-lr.17.mcz http://www.squeaksource.com/PharoInbox/Compiler-lr.118.mcz Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

2 1

[Pharo-project] Fwd: Better senders/implementers UI
by StÃ©phane Ducasse Aug. 27, 2009

Aug. 27, 2009

Begin forwarded message: > Scott Wallace made a nice improvement to the regular senders/ > implementers browsers. It reuses in the same window, and adds a > history pane so you can see how you got to a certain point, and can > back track if necessary. > > This has not been updated since 3.8 I think, but if properly > integrated rather than as separate package it might be quite nice: > > http://www.squeaksource.com/Green.html

2 2

[Pharo-project] about looking at some squeak fixes
by Torsten Bergmann Aug. 27, 2009

Aug. 27, 2009

Stephane wrote >If you want to help. one is "Clarify the meaning of #asOop in Squeak." which is already solved: Just review and integrate the changeset in http://code.google.com/p/pharo/issues/detail?id=1074 Bye Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] New Pharo based on core 10418 - Win32 Installer
by Torsten Bergmann Aug. 27, 2009

Aug. 27, 2009

The according Win32 Setup is available from: http://pharo-project.org/pharo-download or directly http://gforge.inria.fr/frs/download.php/22828/setup_pharo1.0-10418-BETAdev0… What is new: ============ - the name of the setup follows the pharo version scheme (see [1]) as requested by Miguel and therefore matches the name of Damiens ZIP package - the newest windows VM 3.11.4 from Andreas is used (see [2]) - the VM now correctly reports it's version when you select Properties -> Version in the explorer (see [3]) - includes the lates image 10418 from Damien (see [4]) Have fun T. [1] http://n2.nabble.com/Pharo-name-format-td3365418.html#a3385477 [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2009-August/002993.html [3] http://lists.squeakfoundation.org/pipermail/vm-dev/2009-August/002996.html [4] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-August/012923.html -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

2 1

Aug. 27, 2009

Hi since there is a new burst of activity in squeak (probably related to the fact that pharo exists) it would be nice to check the changes. I like the log that they sent it helps spotting change. May be we should have the same to support simple browsing of commit. However I do not know where this behavior comes from. Stef

2 4