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

[Pharo-project] RC3 - small stuff
by Schwab,Wilhelm K March 22, 2010

March 22, 2010

Hello all, Some time ago, there was (I thought) a patch for saving workspace text to a file; I had hoped to find that in 1.0, but it is not in RC3 that I can find. The first thing I did was load the Loader extensions to Gofer. It installed as expected. I have not looked into the code, but tried #search: and found things like Citezen and Rio missing. That might be "simply" because the Configuration* packages are not in the Metacello repository?? If so, are they not there for a non-trivial reason? I then grabbed ConfigurationOfCitezen, and was hung up by an unsatisfied dependence on SmaCC. The SmaCC runtime is in my RC1 image, but I don't know how/why it was loaded; presumably CZLoader did it. Are these bugs or features? I am leaning toward bugs, but the question is whether any or all of the following appicable: (1) ConfigurationOfCitezen needs to load prerequisites; (2) Loader is in the wrong to not see them; (3) I need to add repositories to Loader; (4) various ConfigurationOf* packages need to be in the Metacello repository. Any ideas? Bill

2 2

[Pharo-project] [update 1.1] #11287
by Marcus Denker March 22, 2010

March 22, 2010

11287 ----- Issue 2136: Smalltalk and SmalltalkImage -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.1] #11286
by Marcus Denker March 22, 2010

March 22, 2010

11286 ----- Issue 2179: Tweak from nicolas in sync Pharo and Squeak Issue 2181: CompiledMethod >>getSourceFor: selector in: class Issue 2173: MC browser selection Issue 2186: Adding some methods to the WorldMenu for deprecation Issue 2142: isInMemory should be removed. -- Marcus Denker -- marcus(a)2denker.de http://www.2denker.de 2denker UG (haftungsbeschrÃ¤nkt) Sitz KÃ¶ln Amtsgericht - Registergericht - KÃ¶ln, HRB 65065 GeschÃ¤ftsfÃ¼hrer: Christian Denker und Dr. Marcus Denker

1 0

[Pharo-project] [update 1.1] #11285
by Marcus Denker March 22, 2010

March 22, 2010

11285 ----- - Issue 2180: Move MetaObjectTools from core to PharoDev - Issue 2165: CleanUp unused packages -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] isInMemory :)
by stephane ducasse March 22, 2010

March 22, 2010

Mariano I was wondering (since we already removed a lot of the behavior related to inMemory) if we could not remove is in traitNames "Answer a SortedCollection of all traits (not including class-traits) names." | names | names := OrderedCollection new. self do: [:cl | (cl isInMemory and: [(cl isKindOf: Trait) and: [(cl name beginsWith: 'AnObsolete') not]]) ifTrue: [names add: cl name]]. ^ names and friend Stef

5 18

[Pharo-project] [ANN 1.1] prebuild Core#11284
by Marcus Denker March 22, 2010

March 22, 2010

https://gforge.inria.fr/frs/download.php/26693/PharoCore-1.1-11284-UNSTABLE… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] [ANN] Gofer Project Loader 1.0 (BETA)
by Dale Henrichs March 21, 2010

March 21, 2010

George, At the moment there is no overall way to do that for Pharo. For GemStone I have attributes for specific versions, so for GemStone I can write a spec like this: spec for: #common do: [...]. spec for: #gemstone do: [...]. spec for: #'gs2.4.x' do: [...]. spec for: #'gs3.x' do: [...]. So I can specific packages that are only loaded in GemStone 2.4 or GemStone 3.0. For Pharo I would imagine doing something like the following: spec for: #common do: [...]. spec for: #squeakCommon do: [...]. spec for: #pharo do: [...]. spec for: #'pharo1.0' do: [...]. spec for: #'pharo1.1' do: [...]. Then packages that were specific to 1.0 and 1.1 can be specified. I haven't added this to Metacello for Pharo, because I was kind of waiting for the need to appear rather than add a feature that noone needs, so I've been waiting for someone to ask for the feature:) Dale ----- "George Herolyants" <george.herolyants(a)gmail.com> wrote: | Thanks for the explanation, Dale! | | May be it's obvious and I'm asking stupid questions but then I don't | understand how can I specify in my configuration the differences | between the versions of the target platform? | | 2010/3/20 Dale Henrichs <dale.henrichs(a)gemstone.com>: | > George, | > | > The mcz files containing the Metacello configurations _are_ copied, | but the configuration itself is not modified in the scheme. | > | > The idea of using different repositories is to indicate which of the | many different projects are _expected_ or _known_ to work in Pharo1.1 | or Pharo1.0. | > | > For GemStone, I have createed a GemSource MetacelloRepository and I | have copied the metacello configurations that I know have been ported | to GemStone. I've done this so that folks can know what is supported. | I make sure that all of the tests run green and that all of the | configs in the GemSource MetacelloRepository can be loaded. | > | > It does not stop someone from loading a configuration into GemStone | that isn't in the GemSource MetacelloRepository, but if you do and run | into trouble, my answer will probably be that it hasn't been ported | yet. | > | > The same thing can apply to Squeak, but someone would have to step | up to testing/approving metacello configurations that run with the | various versions. | > | > Without this extra step of approval/testing, it's difficult for | someone that doesn't have their finger on the pulse of the latest and | greatest happenings to know what to expect ... | > | > Dale

2 1

Re: [Pharo-project] [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
by Dale Henrichs March 21, 2010

March 21, 2010

Mariano, I am seriously considering releasing 1.0-beta.25 today ... I have smacked the heck out Metacello over the last three days without issues so I'm thinking I can let this puppy out the door:)...Especially if it will clean up the release process... One other point I have noticed is that the following configurations aren't pointing to the correct repository: ConfigurationOfOmniBrowser ConfigurationOfRefactoringBrowser ConfigurationOfOCompletion ConfigurationOfShout ConfigurationOfProfStef They all reference the package-cache instead of SqueakSource MetacelloRepository. I'm assuming this is because they were in your package-cache when you did the build. I think this is happening because of a recent change in the sorting order for Gofer ... For the build process you may want to either make sure your package-cache is empty or use disablePackageCache in the places where you explicitly load a Configuration or perhaps something else? Dale ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | > | > I see that the installScript uses ConfigurationOfMetacello from | > gemsource metacello repository instead of Metacello repository. | Given | > that this will be the final release of 1.0, shouldn't we copy | > ConfigurationOfMetacello to squeaksource/MetacelloRepository so that | the | > package registered in monticello is this instead of the gemstone | one. | > This repo for ConfigurationOfMetacello overrides the one of | PharoCore | > that points to squeaksource. | > | > Dale, can you put this version in squeaksource. The release is very | > close and anyway it will be shipped in Pharo dev 1.0, so will reach | a | > lot of people, even if not on squeaksource | > | > | Yes. This is because I added the ImageForDevelopers in the group. With | that, | when running headless I have the problem with the progress Bar. | Then, i needed to use the silntly method, which is in Metacello | beta.25 | which is not released yet. That's why I have to put the other one. | | Don't worry that beta.25 will be then correctly uploaded and released. | After | that, the installScript will be even simpler as I won't need to | install | Metacello manually, but with the ensureMetacello ;) | | Cheers | | Mariano | | | | > Cheers | > > | > > Mariano | > > | > > _______________________________________________ | > > Pharo-users mailing list | > > Pharo-users(a)lists.gforge.inria.fr | > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users | > | > -- | > Miguel CobÃ¡ | > http://miguel.leugim.com.mx | > | > | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 3

Re: [Pharo-project] [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
by Dale Henrichs March 21, 2010

March 21, 2010

3 4

[Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
by Mariano Martinez Peck March 21, 2010

March 21, 2010

Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo 1.0. This image is based in PharoCore-1.0-10515rc3. The image also contain lot of fixes and improvements of external packages: These, are the fixed issues of the external tools: OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 O2: issues 1887, 1312, 1429, 1886, 2073 New Inspector: issues 1783, 1499 Refactoring Browser: issue 2108 The link is: https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… Cheers Mariano

4 9