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

Re: [Pharo-dev] Using TreeModel>>selectAll

by Benjamin

Thatâs the default behaviour I was thinking today of introducing a special one which act as you described Ben On 11 Dec 2013, at 21:49, Nicolai Hess <nicolaihess(a)web.de> wrote: > One thing I didn't understand is, are valueholders supposed to announce changes, even if > the "value" didn't changed? > > |log node | > log := OrderedCollection new. > node:= > TreeNodeModel new > content: $a; > whenSelectedChanged:[:item | self halt.log add:item]; > selected: true; > selected: true; > selected: true. > log > > will log three times, even the value (selected=true) didn't changed at all. > (or at most one if "selected" is initialized with false). > > Nicolai > > > > 2013/12/9 Martin Dias <tinchodias(a)gmail.com> > thanks for your help, Ben > > On Mon, Dec 9, 2013 at 11:15 AM, Benjamin > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > > I am still chasing why itâs executed three times > > > > Must be an issue in the info propagation. > > > > Ben > > > > On 09 Dec 2013, at 06:48, Martin Dias <tinchodias(a)gmail.com> wrote: > > > > Hi, I'm back with more annoying questions :) > > > > Using #whenSelectedItemsChanged:, I see that the block is evaluated a lot of > > times: > > > > log := OrderedCollection new. > > roots := #(1 2) collect: [ :each | > > TreeNodeModel new > > content: each; > > selected: true; > > yourself ]. > > > > TreeModel new > > roots: roots; > > multiSelection: true; > > whenSelectedItemsChanged: [ :items | > > log add: items ]; > > openWithSpec. > > log ---> an OrderedCollection(#() an OrderedCollection(1) an > > OrderedCollection(1) an OrderedCollection(1 2) an OrderedCollection(1 2) an > > OrderedCollection(1 2)) > > > > I'd expect only one evaluation... is it a bug or a feature? > > > > cheers, > > MartÃn > > > > > > On Sun, Dec 8, 2013 at 12:22 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> > >> aha! thanks > >> > >> MartÃn > >> > >> On Sat, Dec 7, 2013 at 10:33 AM, Benjamin > >> <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> > roots := #(1 2 3) collect: [ :e | TreeNodeModel new content: e ; > >> > yourself ]. > >> > > >> > TreeModel new > >> > roots: roots; > >> > multiSelection: true; > >> > openWithSpec. > >> > > >> > roots third > >> > selected: true; > >> > takeHighlight > >> > > >> > Ben > >> > > >> > On 07 Dec 2013, at 05:44, Martin Dias <tinchodias(a)gmail.com> wrote: > >> > > >> > ouch! thanks Ben. > >> > > >> > Another related question: is there any way of selecting an arbitrary > >> > item? I tried (among others) with: > >> > > >> > TreeModel new > >> > roots: #(1 2 3); > >> > multiSelection: true; > >> > openWithSpec; > >> > selection: 3 > >> > > >> > without success. > >> > > >> > Cheers, > >> > MartÃn > >> > > >> > > >> > > >> > On Thu, Dec 5, 2013 at 4:17 PM, Benjamin > >> > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> > > >> > your tree here is single selection so it will not work > >> > > >> > TreeModel new > >> > roots: #(1 2 3); > >> > multiSelection: true; > >> > openWithSpec; > >> > selectAll > >> > > >> > Ben > >> > > >> > On 05 Dec 2013, at 15:38, Martin Dias <tinchodias(a)gmail.com> wrote: > >> > > >> > Hi, > >> > > >> > I'm not sure how this method should be used. I tried in different > >> > ways, for example: > >> > > >> > TreeModel new > >> > roots: #(1 2 3); > >> > selectAll; > >> > openWithSpec > >> > > >> > But always the items are unselected. Is it a bug? or I didn't find the > >> > way to use it? > >> > > >> > Thanks, > >> > MartÃn > >> > > >> > > >> > > >> > > > > > > > > >

Dec. 11, 2013

Re: [Pharo-dev] Voronoi diagram

by Natalia Tymchuk

Hello. Cool. It is easy to download. Does anybody know how to use it, because there are no comments and tests? Best regards, Natalia 2013/12/10 NISHIHARA Satoshi <goonsh(a)gmail.com> > Voronoi-2d-Diagram, you can install from Configuration browser of 2.0. ;-) > > 2013/12/8 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > > Check this out > > > > http://www.smalltalkhub.com/#!/~goonsh/Voronoi-2d-Diagram > > http://www.squeaksource.com/VoronoiDiagram.html > > > > There is also an old package implementing Voronoi diagrams also, I can > have > > a look if you those are not enough for your needs. > > Cheers > > > > HernÃ¡n > > > > El 07/12/2013 13:59, Natalia Tymchuk escribiÃ³: > > > >> Hello. > >> I started implementing visualization of Voronoi diagrams and I need to > >> do a lot of operations on the lines and polygons. I have some questions: > >> Is it implemented somewhere? > >> Did somebody do something with the Voronoi diagrams? > >> > >> Best regards, > >> Natalia > >> > >> > > > > > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] > >

Dec. 11, 2013

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

by Esteban Lorenzano

I will promote the latest vm (latest before spur) as stable tomorrow morning. So I suppose he can try that :) Pharo-VM-mac-latest.zip<http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-latest.zip> cheers, Esteban On Wed, Dec 11, 2013 at 7:41 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 11 Dec 2013, at 19:37, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > Hi Dario, > > > > > > On Wed, Dec 11, 2013 at 12:41 AM, Dario Trussardi < > dario.trussardi(a)tiscali.it> wrote: > > Ciao Eliot, > > > > > >> Hi Dario, > >> > >> > >> On Tue, Dec 10, 2013 at 8:12 AM, Dario Trussardi < > dario.trussardi(a)tiscali.it> wrote: > >> Ciao, > >> > >> i work with a new Pharo 2.0 20628 image. > >> > >> I do first : > >> A) Gofer new url: ' > http://smalltalkhub.com/mc/DiegoLont/QCMagritte/main'; package: > 'ConfigurationOfQCMagritte'; load. > >> > >> and: > >> B) ((Smalltalk at: #ConfigurationOfQCMagritte) project > version: '0.2') load: #( 'Demo' ). > >> > >> After some works the system when Fetching 1.0.2.1 of > ConfigurationOfTwitteBootstrap > >> > >> erase the error: > >> > >> > >> SmallInteger(Object)>>doesNotUnderstand: #isEmpty > >> MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: > >> MetacelloMCVersionSpec>>resolveToLoadableSpecs: > >> MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | > ... > >> > MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: > in Block: [:dict | ... > >> > MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: > in Block: [^ aBlock value: dict] > >> BlockClosure>>on:do: > >> > MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: > >> > MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: > >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:at:doing: > >> MetacelloMCVersionSpec>>expandToLoadableSpecNames: > >> MetacelloMCVersion>>expandToLoadableSpecNames: > >> MetacelloMCProjectSpec>>relativeCurrentVersion in Block: [vrsn > expandToLoadableSpecNames: (loadList := self...etc... > >> BlockClosure>>on:do: > >> MetacelloMCProjectSpec>>relativeCurrentVersion > >> MetacelloProjectReferenceSpec>>relativeCurrentVersion > >> MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: in Block: [:prj | ... > >> MetacelloProjectReferenceSpec>>projectDo:packageDo:groupDo: > >> MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: in > Block: [:name | | pkgSpec | (pkgSpec := map... > >> Array(SequenceableCollection)>>do: > >> MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: > >> MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: > >> MetacelloMCVersionSpec>>isPartiallyCurrent > >> MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: > [:version | ... > >> Array(SequenceableCollection)>>do: > >> MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: > [:cache | ... > >> > MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: > in Block: [:dict | ... > >> > MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: > in Block: [^ aBlock value: dict] > >> BlockClosure>>on:do: > >> > MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: > >> > >> Any idea? > >> > >> I suspect you have an older, buggy, VM. What does the VM say to > -version? > > > > How i can define the VM that the system used ? > > > > The Mac finder has facilities for choosing an app for a document type. > google will find it quickly. > > > > In the menu System / System Reported i found this: > > > > Virtual Machine --------------- > /Users/dtr/Desktop/Pharo2.0.app/Contents/MacOS/Pharo NBCoInterpreter > NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit > NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious > > .org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 > Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> > Jenkins build #14535 Mac Cocoa Cog 5.8b12 21-Sep-10 > >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString git:// > gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit > NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > > > > It is significant ? > > > > yes. that VM is buggy. I suggest you use the most up-to-date Pharo VM. > Pharo VM guys, what VM would you recommend for Dario? > > http://www.pharo-project.org/ > > => > > http://www.pharo-project.org/pharo-download > > => > > http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-stable.zip > > Or did you already try this ? > > > In my MacBook i have run some Pharo version. > > > > For open the Pharo 2.0 i double click on the Pharo 2.0 icon on the > desktop. > > > > Right ? > > > > Thanks, > > > > Dario > > > >> > >> Thanks, > >> > >> Dario > >> > >> -- > >> HTH, > >> Eliot > > > > > > > > > > -- > > best, > > Eliot > > >

Dec. 11, 2013

Re: [Pharo-dev] Using TreeModel>>selectAll

by Nicolai Hess

One thing I didn't understand is, are valueholders supposed to announce changes, even if the "value" didn't changed? |log node | log := OrderedCollection new. node:= TreeNodeModel new content: $a; whenSelectedChanged:[:item | self halt.log add:item]; selected: true; selected: true; selected: true. log will log three times, even the value (selected=true) didn't changed at all. (or at most one if "selected" is initialized with false). Nicolai 2013/12/9 Martin Dias <tinchodias(a)gmail.com> > thanks for your help, Ben > > On Mon, Dec 9, 2013 at 11:15 AM, Benjamin > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > > I am still chasing why itâs executed three times > > > > Must be an issue in the info propagation. > > > > Ben > > > > On 09 Dec 2013, at 06:48, Martin Dias <tinchodias(a)gmail.com> wrote: > > > > Hi, I'm back with more annoying questions :) > > > > Using #whenSelectedItemsChanged:, I see that the block is evaluated a > lot of > > times: > > > > log := OrderedCollection new. > > roots := #(1 2) collect: [ :each | > > TreeNodeModel new > > content: each; > > selected: true; > > yourself ]. > > > > TreeModel new > > roots: roots; > > multiSelection: true; > > whenSelectedItemsChanged: [ :items | > > log add: items ]; > > openWithSpec. > > log ---> an OrderedCollection(#() an OrderedCollection(1) an > > OrderedCollection(1) an OrderedCollection(1 2) an OrderedCollection(1 2) > an > > OrderedCollection(1 2)) > > > > I'd expect only one evaluation... is it a bug or a feature? > > > > cheers, > > MartÃn > > > > > > On Sun, Dec 8, 2013 at 12:22 AM, Martin Dias <tinchodias(a)gmail.com> > wrote: > >> > >> aha! thanks > >> > >> MartÃn > >> > >> On Sat, Dec 7, 2013 at 10:33 AM, Benjamin > >> <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> > roots := #(1 2 3) collect: [ :e | TreeNodeModel new content: e ; > >> > yourself ]. > >> > > >> > TreeModel new > >> > roots: roots; > >> > multiSelection: true; > >> > openWithSpec. > >> > > >> > roots third > >> > selected: true; > >> > takeHighlight > >> > > >> > Ben > >> > > >> > On 07 Dec 2013, at 05:44, Martin Dias <tinchodias(a)gmail.com> wrote: > >> > > >> > ouch! thanks Ben. > >> > > >> > Another related question: is there any way of selecting an arbitrary > >> > item? I tried (among others) with: > >> > > >> > TreeModel new > >> > roots: #(1 2 3); > >> > multiSelection: true; > >> > openWithSpec; > >> > selection: 3 > >> > > >> > without success. > >> > > >> > Cheers, > >> > MartÃn > >> > > >> > > >> > > >> > On Thu, Dec 5, 2013 at 4:17 PM, Benjamin > >> > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> > > >> > your tree here is single selection so it will not work > >> > > >> > TreeModel new > >> > roots: #(1 2 3); > >> > multiSelection: true; > >> > openWithSpec; > >> > selectAll > >> > > >> > Ben > >> > > >> > On 05 Dec 2013, at 15:38, Martin Dias <tinchodias(a)gmail.com> wrote: > >> > > >> > Hi, > >> > > >> > I'm not sure how this method should be used. I tried in different > >> > ways, for example: > >> > > >> > TreeModel new > >> > roots: #(1 2 3); > >> > selectAll; > >> > openWithSpec > >> > > >> > But always the items are unselected. Is it a bug? or I didn't find the > >> > way to use it? > >> > > >> > Thanks, > >> > MartÃn > >> > > >> > > >> > > >> > > > > > > > > >

Dec. 11, 2013

Re: [Pharo-dev] Which tests should be run in CI?

by Stephan Eggermont

Torsten, For unit tests building on green builds might be enough, but what about integration/smoke tests? Concrete case: I added a test to check that no class implements >>packages That is a test that should be run by all builds, but is not. The consequence is that Moose and Pharo3 based builds using seaside or magritte can not reliably use "senders of" I assume there are more tests like this. Stephan

Dec. 11, 2013

Re: [Pharo-dev] Which tests should be run in CI?

by Torsten Bergmann

Hi Stephan, that depends - for instance for "Bootstrap" I follow the pattern that most other contributions have configured: I only run the tests of the Bootstrap package to see when my own stuff breaks. If I would run all tests it may never be green because the underlying platform may be on the move. Usually a build can depende on another build (like Pharo 3) - so if this is not green the chain does not continue. At least this is how I see it... Bye T. > Gesendet: Mittwoch, 11. Dezember 2013 um 21:14 Uhr > Von: "Stephan Eggermont" <stephan(a)stack.nl> > An: pharo-dev(a)lists.pharo.org, Moose-dev(a)iam.unibe.ch > Betreff: [Pharo-dev] Which tests should be run in CI? > > I notice that several builds are green, though I added a breaking test to Pharo 3. > That probably means that those builds don't run all of the Pharo tests. > Most builds probably don't need to run all tests (all the time), but it might be > useful to be able to mark tests as integration tests, that are expected to be > run by all downstream builds. > > Concrete, every Pharo 3 build that loads Grease should currently be red. > > Stephan >

Dec. 11, 2013

Which tests should be run in CI?

by Stephan Eggermont

I notice that several builds are green, though I added a breaking test to Pharo 3. That probably means that those builds don't run all of the Pharo tests. Most builds probably don't need to run all tests (all the time), but it might be useful to be able to mark tests as integration tests, that are expected to be run by all downstream builds. Concrete, every Pharo 3 build that loads Grease should currently be red. Stephan

Dec. 11, 2013

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

by Sven Van Caekenberghe

On 11 Dec 2013, at 19:37, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Dario, > > > On Wed, Dec 11, 2013 at 12:41 AM, Dario Trussardi <dario.trussardi(a)tiscali.it> wrote: > Ciao Eliot, > > >> Hi Dario, >> >> >> On Tue, Dec 10, 2013 at 8:12 AM, Dario Trussardi <dario.trussardi(a)tiscali.it> wrote: >> Ciao, >> >> i work with a new Pharo 2.0 20628 image. >> >> I do first : >> A) Gofer new url: 'http://smalltalkhub.com/mc/DiegoLont/QCMagritte/main'; package: 'ConfigurationOfQCMagritte'; load. >> >> and: >> B) ((Smalltalk at: #ConfigurationOfQCMagritte) project version: '0.2') load: #( 'Demo' ). >> >> After some works the system when Fetching 1.0.2.1 of ConfigurationOfTwitteBootstrap >> >> erase the error: >> >> >> SmallInteger(Object)>>doesNotUnderstand: #isEmpty >> MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: >> MetacelloMCVersionSpec>>resolveToLoadableSpecs: >> MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] >> BlockClosure>>on:do: >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:at:doing: >> MetacelloMCVersionSpec>>expandToLoadableSpecNames: >> MetacelloMCVersion>>expandToLoadableSpecNames: >> MetacelloMCProjectSpec>>relativeCurrentVersion in Block: [vrsn expandToLoadableSpecNames: (loadList := self...etc... >> BlockClosure>>on:do: >> MetacelloMCProjectSpec>>relativeCurrentVersion >> MetacelloProjectReferenceSpec>>relativeCurrentVersion >> MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: in Block: [:prj | ... >> MetacelloProjectReferenceSpec>>projectDo:packageDo:groupDo: >> MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: in Block: [:name | | pkgSpec | (pkgSpec := map... >> Array(SequenceableCollection)>>do: >> MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: >> MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: >> MetacelloMCVersionSpec>>isPartiallyCurrent >> MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: [:version | ... >> Array(SequenceableCollection)>>do: >> MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: [:cache | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] >> BlockClosure>>on:do: >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: >> >> Any idea? >> >> I suspect you have an older, buggy, VM. What does the VM say to -version? > > How i can define the VM that the system used ? > > The Mac finder has facilities for choosing an app for a document type. google will find it quickly. > > In the menu System / System Reported i found this: > > Virtual Machine --------------- /Users/dtr/Desktop/Pharo2.0.app/Contents/MacOS/Pharo NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious > .org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > > It is significant ? > > yes. that VM is buggy. I suggest you use the most up-to-date Pharo VM. Pharo VM guys, what VM would you recommend for Dario? http://www.pharo-project.org/ => http://www.pharo-project.org/pharo-download => http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-stable.zip Or did you already try this ? > In my MacBook i have run some Pharo version. > > For open the Pharo 2.0 i double click on the Pharo 2.0 icon on the desktop. > > Right ? > > Thanks, > > Dario > >> >> Thanks, >> >> Dario >> >> -- >> HTH, >> Eliot > > > > > -- > best, > Eliot

Dec. 11, 2013

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

by Eliot Miranda

Hi Dario, On Wed, Dec 11, 2013 at 12:41 AM, Dario Trussardi < dario.trussardi(a)tiscali.it> wrote: > Ciao Eliot, > > > Hi Dario, > > > On Tue, Dec 10, 2013 at 8:12 AM, Dario Trussardi < > dario.trussardi(a)tiscali.it> wrote: > >> Ciao, >> >> i work with a new Pharo 2.0 20628 image. >> >> I do first : >> A) Gofer new url: ' >> http://smalltalkhub.com/mc/DiegoLont/QCMagritte/main'; package: >> 'ConfigurationOfQCMagritte'; load. >> >> and: >> B) ((Smalltalk at: #ConfigurationOfQCMagritte) project >> version: '0.2') load: #( 'Demo' ). >> >> After some works the system when Fetching 1.0.2.1 of >> ConfigurationOfTwitteBootstrap >> >> erase the error: >> >> >> SmallInteger(Object)>>doesNotUnderstand: #isEmpty >> MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: >> MetacelloMCVersionSpec>>resolveToLoadableSpecs: >> MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: >> in Block: [:dict | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: >> in Block: [^ aBlock value: dict] >> BlockClosure>>on:do: >> >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: >> >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:at:doing: >> MetacelloMCVersionSpec>>expandToLoadableSpecNames: >> MetacelloMCVersion>>expandToLoadableSpecNames: >> MetacelloMCProjectSpec>>relativeCurrentVersion in Block: [vrsn >> expandToLoadableSpecNames: (loadList := self...etc... >> BlockClosure>>on:do: >> MetacelloMCProjectSpec>>relativeCurrentVersion >> MetacelloProjectReferenceSpec>>relativeCurrentVersion >> MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: in Block: [:prj | ... >> MetacelloProjectReferenceSpec>>projectDo:packageDo:groupDo: >> MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: in Block: >> [:name | | pkgSpec | (pkgSpec := map... >> Array(SequenceableCollection)>>do: >> MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: >> MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: >> MetacelloMCVersionSpec>>isPartiallyCurrent >> MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: >> [:version | ... >> Array(SequenceableCollection)>>do: >> MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: >> [:cache | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: >> in Block: [:dict | ... >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: >> in Block: [^ aBlock value: dict] >> BlockClosure>>on:do: >> >> MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: >> >> Any idea? >> > > I suspect you have an older, buggy, VM. What does the VM say to -version? > > > How i can define the VM that the system used ? > The Mac finder has facilities for choosing an app for a document type. google will find it quickly. > In the menu System / System Reported i found this: > > Virtual Machine --------------- > /Users/dtr/Desktop/Pharo2.0.app/Contents/MacOS/Pharo NBCoInterpreter > NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit > NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious > .org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 > Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> > Jenkins build #14535 Mac Cocoa Cog 5.8b12 21-Sep-10 > >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString > git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit > NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > > It is significant ? > yes. that VM is buggy. I suggest you use the most up-to-date Pharo VM. Pharo VM guys, what VM would you recommend for Dario? > > In my MacBook i have run some Pharo version. > > For open the Pharo 2.0 i double click on the Pharo 2.0 icon on the > desktop. > > Right ? > > Thanks, > > Dario > > > >> Thanks, >> >> Dario >> > > -- > HTH, > Eliot > > > -- best, Eliot

Dec. 11, 2013

Re: [Pharo-dev] [Spec] whenSelectedItemsChanged: on TreeModel

by Benjamin

As I said to Martin, I will investigate why, but itâs a bit tricky Must be some issue in MorphTreeMorph I introduced recently Ben On 11 Dec 2013, at 16:46, Roberto Minelli <roberto.minelli(a)usi.ch> wrote: > Hi, > > I am experiencing problems with #whenSelectedItemsChanged: on a TreeModel. > > In particular, the block (i.e., argument of #whenSelectedItemsChanged: gets randomly executed a couple of times (3/4) the second time that the selection happens. The first time is fine. It looks like the registration of the âeventâ or âannouncementâ is done multiple times. > > Any hint? > > Cheers, > R

Dec. 11, 2013