February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] About migrating Pharo 1.0, 1.1 and 1.2 and 1.3 from ss to Smalltalkhub

by stephane ducasse

On Feb 17, 2013, at 12:10 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > We should have a "import" button I think ^^ :) I would like to be able to remove wrong file :) For the import button I can manage it :) Ben we should migrate spec from SS3 to Pharo. Do you want me to do it. I'm in machine mode right now. Stef > > Ben > > On Feb 17, 2013, at 12:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi >> >> I would like to migrate the complete history of Pharo to SmalltalkHub. >> >> So I imagine that I will create a new project named Pharo1.0 under the Pharo team >> We should do the same for Pharo2.0 at some point >> >> >> When we will be start Pharo3.0 we should do the same so like that we will have >> >> Pharo/Pharo1.0 >> Pharo/Pharo1.4 >> Pharo/Pharo2.0 >> Pharo/Pharo3.0 >> >> is is ok? >> >> Stef >

Feb. 17, 2013

Re: [Pharo-project] About migrating Pharo 1.0, 1.1 and 1.2 and 1.3 from ss to Smalltalkhub

by Benjamin

We should have a "import" button I think ^^ Ben On Feb 17, 2013, at 12:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I would like to migrate the complete history of Pharo to SmalltalkHub. > > So I imagine that I will create a new project named Pharo1.0 under the Pharo team > We should do the same for Pharo2.0 at some point > > > When we will be start Pharo3.0 we should do the same so like that we will have > > Pharo/Pharo1.0 > Pharo/Pharo1.4 > Pharo/Pharo2.0 > Pharo/Pharo3.0 > > is is ok? > > Stef

Feb. 17, 2013

Re: [Pharo-project] Migrated XMLWriter to SmalltalkHub

by stephane ducasse

I checked and the configuration was loading 15 versions. Stef Name: Collections-Support-StephaneDucasse.35 Author: StephaneDucasse Time: 26 May 2010, 9:42:16 pm UUID: b4d0a1ee-0e5e-458c-9856-a72b6a0a19e6 Ancestors: Collections-Support-StephaneDucasse.34 - Issue2317: FasterGrayPNGs. Thanks Squeak/Henrik - Issue 2468: Better method trailer method creation. Part two. Thanks Igor - Issue2242: FormConversionGeneralization. Henrik - Better ScriptLoader comment to explain our process. - Issue 1377: Senders of and implementers of does not work when symbol selected. Thanks Guile. - Issue 2074: Creating classes with Strings as the key in Smalltalk. Thanks marcus. - Issue 2480: prepare deprecation of and:and: + deprecated and:and:and:and: So just ignoring On Feb 17, 2013, at 12:00 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > On Feb 17, 2013, at 11:19 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Feb 17, 2013, at 11:08 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi guys >>> >>> I migrated XMLWriter from Squeaksource to Smalltalkhub. I added a little test package and removed the fact that some >>> old Collections-Support package!!! was loaded on top of new ones! Argh. >>> >> >> What we really need to do is to integrate all the basic improvements of Moose in the base system. >> Those that are general, useful and good. >> >> (Those of the kind that Moose people forget that these are additions and they always start to file >> bug reports why we removed those things in the new Pharo Version ;-) > > > Yes but this had nothing with moose extensions. Just that the configuration was loading an old versions > from an old pharo repository. > >> >> Marcus > >

Feb. 17, 2013

[Pharo-project] About migrating Pharo 1.0, 1.1 and 1.2 and 1.3 from ss to Smalltalkhub

by StÃ©phane Ducasse

Hi I would like to migrate the complete history of Pharo to SmalltalkHub. So I imagine that I will create a new project named Pharo1.0 under the Pharo team We should do the same for Pharo2.0 at some point When we will be start Pharo3.0 we should do the same so like that we will have Pharo/Pharo1.0 Pharo/Pharo1.4 Pharo/Pharo2.0 Pharo/Pharo3.0 is is ok? Stef

Feb. 17, 2013

Re: [Pharo-project] Migrated XMLWriter to SmalltalkHub

by stephane ducasse

On Feb 17, 2013, at 11:19 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 17, 2013, at 11:08 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> I migrated XMLWriter from Squeaksource to Smalltalkhub. I added a little test package and removed the fact that some >> old Collections-Support package!!! was loaded on top of new ones! Argh. >> > > What we really need to do is to integrate all the basic improvements of Moose in the base system. > Those that are general, useful and good. > > (Those of the kind that Moose people forget that these are additions and they always start to file > bug reports why we removed those things in the new Pharo Version ;-) Yes but this had nothing with moose extensions. Just that the configuration was loading an old versions from an old pharo repository. > > Marcus

Feb. 17, 2013

Re: [Pharo-project] Migrated XMLWriter to SmalltalkHub

by Marcus Denker

On Feb 17, 2013, at 11:08 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I migrated XMLWriter from Squeaksource to Smalltalkhub. I added a little test package and removed the fact that some > old Collections-Support package!!! was loaded on top of new ones! Argh. > What we really need to do is to integrate all the basic improvements of Moose in the base system. Those that are general, useful and good. (Those of the kind that Moose people forget that these are additions and they always start to file bug reports why we removed those things in the new Pharo Version ;-) Marcus

Feb. 17, 2013

[Pharo-project] Migrated XMLWriter to SmalltalkHub

by StÃ©phane Ducasse

Hi guys I migrated XMLWriter from Squeaksource to Smalltalkhub. I added a little test package and removed the fact that some old Collections-Support package!!! was loaded on top of new ones! Argh. Stef

Feb. 17, 2013

[Pharo-project] [update 2.0] #20551

by Marcus Denker

20551 ----- Issue 7523: Now update the class icon when method modified or removed http://code.google.com/p/pharo/issues/detail?id=7523 Issue 7522: rename File out Stack to Fuel out Stack http://code.google.com/p/pharo/issues/detail?id=7522 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-MarcusDenker.1042.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.426.diff

Feb. 17, 2013

[Pharo-project] SmalltalkHub

by StÃ©phane Ducasse

Is there a way to remove a file from the repository? Stef

Feb. 17, 2013

Re: [Pharo-project] Problems with Metacello

by stephane ducasse

On Feb 16, 2013, at 10:36 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > Hi Dale > > I have two questions: > > > first question: className usage in presence of regular package. > ------------------------------------------------------------------------------------------- > In the following baseline, I do not understand why I'm forced to specify the className because the configuration > is based on the project name. > > > spec project: 'OrderPreservingDictionary' with: [ > spec > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ without className > > versionString: #stable; > loads: #('Core'); > repository: 'http://smalltalkhub.com/mc/Pharo/OrderPreservingDictionary/main']. > > does not work > > while > > spec project: 'OrderPreservingDictionary' with: [ > spec > className: 'ConfigurationOfOrderPreservingDictionary'; > versionString: #stable; > loads: #('Core'); > repository: 'http://smalltalkhub.com/mc/Pharo/OrderPreservingDictionary/main']. > Works > > > baseline200: spec > <version: '2.0.0-baseline'> > > spec for: #common do: [ > spec > blessing: #baseline; > description: 'Migrated to SmalltalkHub and taking into account new configurations of subcomponents'; > repository: 'http://smalltalkhub.com/mc/Pharo/XMLWriter/main'. > > spec project: 'OrderPreservingDictionary' with: [ > spec > className: 'ConfigurationOfOrderPreservingDictionary'; > versionString: #stable; > loads: #('Core'); > repository: 'http://smalltalkhub.com/mc/Pharo/OrderPreservingDictionary/main']. > > spec package: 'XML-Writer' with: [spec requires: 'OrderPreservingDictionary']. > > spec > group: 'default' with: #('Core'); > group: 'Core' with: #('XML-Writer'); > group: 'Tests' with: #() ]. > > > spec for: #squeakCommon do: [ > spec package: 'Collections-Support' with: [ > spec repository: 'http://www.squeaksource.com/Pharo' ] ]. > > > second question > ----------------------- > > People wrote the following in the baseline > > > spec for: #squeakCommon do: [ > spec package: 'Collections-Support' with: [ > spec repository: 'http://www.squeaksource.com/Pharo' ] ]. > > I commented the squeakCommon part because it was loading an old package in pharo! > And this package is part of Pharo. > Now when I comment the version I do not understand why it is still trying to load a package version because there is already a > version in the image. > > I will remove it from the baseline but I do not understand this behavior. Packages present in the image do not take > precedence? I imagine that this is because they are not saved in the same repository than the one of pharo2.0 I will have a look to see if it changes something. > > > version200: spec > <version: '2.0.0' imports: #('2.0.0-baseline')> > spec > for: #common > do: [ spec > blessing: #release; > package: 'XML-Writer' with: 'XML-Writer-JAAyer.5' ]; > > " I do not understand the following line because it means that we would load an older version than the one currently in Pharo. Clearly the best way to introduce bugs and losing hours trying to understand why. > for: #squeakCommon do: [ spec package: 'Collections-Support' with: 'Collections-Support-StephaneDucasse.35' ];" > for: #gemstone > do: [ > spec > package: 'Collections-Support' with: 'Collections-Support.g-OttoBehrens.45'; > package: 'Collections-Tests-Support' with: 'Collections-Tests-Support.g-OttoBehrens.3' ] > > > Now I do not understand why it loads a package when the package > > Stef > >

Feb. 17, 2013