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

[Pharo-project] About dependency granularity in metacello
by StÃ©phane Ducasse Feb. 10, 2013

Feb. 10, 2013

Hi dale I'm migrating Moose and I got the following question. In terms of granularity of dependency when depending of project. Before we had Fame that depended directly on one package of phexample. baseline11: spec <version: '1.1-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec description: 'Baseline 1.1 first version on SmalltalkHub, copied from baseline 1.0 on SqueakSource'. spec repository: 'http://www.smalltalkhub.com/mc/Moose/Fame/main'. spec package: 'Fame-Core'; package: 'Fame-Util'; package: 'Fame-ImportExport' with: [spec requires: #('Fame-Core' ) ]; package: 'Fame-SmalltalkBinding' with: [spec requires: #('Fame-Core' ) ]; package: 'Fame-Example'; package: 'Phexample' with: [spec repository: 'http://www.squeaksource.com/phexample' ]; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ package: 'Fame-Tests-Core' with: [spec requires: #('Fame-Core' 'Fame-Example' 'Phexample' ) ]. spec group: 'Core' with: #('Fame-Core' 'Fame-ImportExport' 'Fame-Util' 'Fame-SmalltalkBinding' ); group: 'Tests' with: #('Fame-Tests-Core' ) ]. Stefan created a configuration for PhExample so the Fame baseline now depends on the Phexample project baseline12: spec <version: '1.2-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec description: 'Baseline 1.2 to make explicit that Fame depends on HashTable and Phexample (now on smalltalkHub and with working configurations'. spec repository: 'http://www.smalltalkhub.com/mc/Moose/Fame/main'. spec project: 'HashTable' with: [ spec className: 'ConfigurationOfHashTable'; versionString: #stable; repository: 'http://www.smalltalkhub.com/mc/Moose/HashTable/main' ]. spec project: 'Phexample' with: [ spec className: 'ConfigurationOfPhexample'; versionString: #stable; repository: 'http://www.smalltalkhub.com/mc/Phexample/main' ]. spec package: 'Fame-Core' with: [spec requires: 'HashTable']; package: 'Fame-Util'; package: 'Fame-ImportExport' with: [spec requires: #('Fame-Core' ) ]; package: 'Fame-SmalltalkBinding' with: [spec requires: #('Fame-Core' ) ]; package: 'Fame-Example'; package: 'Fame-Tests-Core' with: [spec requires: #('Fame-Core' 'Fame-Example') ]. spec group: 'Core' with: #('Fame-Core' 'Fame-ImportExport' 'Fame-Util' 'Fame-SmalltalkBinding' ); group: 'Tests' with: #('Fame-Tests-Core' ) ]. Now my question we got from package: 'Fame-Tests-Core' with: [spec requires: #('Fame-Core' 'Fame-Example' 'Phexample' ) ]. to a dependency between project and I was wondering if this is ok because may be a project is large and we only depend on a small part. Then doing so we are also losing the information that this is Fame-Tests-Core that introduces the dependency to PhExample and for large project such information can be important So is there a way to keep it? Stef

4 5

[Pharo-project] [update 2.0] #20532
by Marcus Denker Feb. 10, 2013

Feb. 10, 2013

20532 ----- Issue 7471: Make #testRewrites a little more readable http://code.google.com/p/pharo/issues/detail?id=7471 Issue 7468: NECCompletion still a bit askew http://code.google.com/p/pharo/issues/detail?id=7468 Issue 6550: [BUG Spec]: DropListModel>>whenSelectionChanged: http://code.google.com/p/pharo/issues/detail?id=6550 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-MarcusDenker.97.diff http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.93.diff http://ss3.gemstone.com/ss/Pharo20/AST-Tests-Core-MarcusDenker.21.diff

1 0

[Pharo-project] Migrated HashTable from ss to SmalltalkHub
by StÃ©phane Ducasse Feb. 10, 2013

Feb. 10, 2013

- migrated all the history - defined configurationOf - All tests are green under 1.4 and 2.0 Stef

5 4

Re: [Pharo-project] Pharo-project Digest, Vol 58, Issue 10
by Angelo Schneider Feb. 10, 2013

Feb. 10, 2013

Sorry to disturb, I'm likely on the wrong mailing list. Is there one for more "consumer" related questions? Best Regards Angelo privat: -------------------- www.oomentor.de -------------------------- Angelo Schneider OOAD/UML Angelo.Schneider(a)oomentor.de Putlitzstr. 24 Patterns/FrameWorks Fon: +49 721 9812465 76137 Karlsruhe C++/JAVA Mob: +49 172 9873893

3 2

[Pharo-project] Things i am working on now
by Igor Stasenko Feb. 10, 2013

Feb. 10, 2013

- building VM on windows - updating VM configs to use new location of NB - fixes to NB for windows - more precise copying of machine code for primitive 220 , to copy exact machine code without extra garbage, so it can fail primitive and won't run random machine instructions - testing if everything builds with "PharoVMBuilder build" -- Best regards, Igor Stasenko.

6 10

[Pharo-project] Nice scripts to migrate projects to SmalltalkHub
by StÃ©phane Ducasse Feb. 10, 2013

Feb. 10, 2013

from the Gofer chapter of course | go | go := Gofer new. go squeaksource: 'ht'. (go allResolved select: [:each | 'Hash*' match: each packageName]) do: [:pack| self crLog: pack packageName. go package: pack packageName; fetch] | go repo | repo := MCSmalltalkhubRepository owner: 'Moose' project: 'HashTable' user: 'StephaneDucasse' password: 'xxxxx'. go := Gofer new. go repository: repo. (((FileSystem disk workingDirectory / 'package-cache') allFiles select: [:each | 'Hash*.mcz' match: each basename]) groupedBy: [:each | (each base copyUpToLast: $-) ]) keys do: [:name | go package: name; push] Here the script handle multiple packages automatically for example. This is not the case for HashTable but really useful in other cases. S.

1 0

[Pharo-project] ConfigurationOfPetitParser has broken #'common' section
by Frank Shearar Feb. 10, 2013

Feb. 10, 2013

By "broken" I mean "it might work fine in Pharo but it doesn't in Squeak". That's because PetitParser now uses Glamour, which pulls in a whole host of things that probably don't work in Squeak. (I don't know, I haven't tried, but these are all UI things, and the UI is where Pharo and Squeak are least compatible.) I'm being a bit rude in that I don't yet have a fix for the issue. Ideally, a ConfigurationOf would have Pharo specific stuff and Squeak specific stuff in separate sections, with only the shared things (right now, not Glamour, nor its dependents) in the #'common' section. However, if someone doesn't beat me to it, I'll submit a fix soon, once Squeak 4.4 is out the door. frank

5 10

[Pharo-project] [update 2.0] #20531
by Marcus Denker Feb. 10, 2013

Feb. 10, 2013

20531 ----- Issue 7464: Code critic - codecritc browser http://code.google.com/p/pharo/issues/detail?id=7464 Issue 7102: Dont insert spaces between SmartCharacters http://code.google.com/p/pharo/issues/detail?id=7102 Issue 7466: PluggableTextMorph redo still not working http://code.google.com/p/pharo/issues/detail?id=7466 Diff information: http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.91.diff http://ss3.gemstone.com/ss/Pharo20/Morphic-MarcusDenker.1350.diff http://ss3.gemstone.com/ss/Pharo20/Manifest-CriticBrowser-MarcusDenker.57.d… http://ss3.gemstone.com/ss/Pharo20/Manifest-Core-MarcusDenker.111.diff

4 5

[Pharo-project] Redline Smalltalk V1.0 ...
by James Ladd Feb. 10, 2013

Feb. 10, 2013

Hi All, Redline Smalltalk, a Smalltalk for the JAVA Virtual Machine, is making a big push to get V1.0 out. We really need your help with the class library (in Smalltalk) or in Java with the implementation or with financial support via Indiegogo here. Helping Redline brings more people to Smalltalk and that has to be a good thing. Please help today. - James.

1 0

[Pharo-project] Soup works in 2.0
by Sean P. DeNigris Feb. 9, 2013

Feb. 9, 2013

All tests pass. I updated the config and uploaded it to SqS and ss3... Cheers, Sean -- View this message in context: http://forum.world.st/Soup-works-in-2-0-tp4665907.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 10