- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Following the white rabbit

by Guillermo Polito

Vamos Esteban!!! On Mon, Apr 2, 2012 at 9:16 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > >> > > > > Excellent news ! > > > > I am happy and I wish you a great job there with RMOD. > > The biggest challenge will be to manage expectations, your workload and > your priorities. > > :) > Indeed. One step at a time butâ¦. plenty of them and FAST :) > > Stef > > > I am sure you will do great. > > > > Sven > > > > >

April 2, 2012

Re: [Pharo-project] Following the white rabbit

by StÃ©phane Ducasse

>> > > Excellent news ! > > I am happy and I wish you a great job there with RMOD. > The biggest challenge will be to manage expectations, your workload and your priorities. :) Indeed. One step at a time butâ¦. plenty of them and FAST :) Stef > I am sure you will do great. > > Sven >

April 2, 2012

Re: [Pharo-project] Following the white rabbit

by Sven Van Caekenberghe

On 02 Apr 2012, at 18:15, Esteban Lorenzano wrote: > Hi list, > > Today was my first day working for Pharo consortium, and is not necessary to write how wonderful experience is to work in something really meaningful for al of us, smalltalkers who are trying to make a living using this environment. > > So far, I'm just starting to feel the magic, how it is everything in the real side of the matrix. A powerful world with tons of valuable things done, tons ongoing and even more tons just being started to dream. > > All my work this year will be improve the Pharo infraestructure and collaborate on consortium kick-off, so I'm going to do things at several levels. > In particular this first week, I will be working on: > -getting Pharo 1.4 ready to release (not just me, everybody here are commited to that, but well... I'm being paid for INRIA to do it :P) > -start the Pharo consortium website building, which I think it will be a pier site with our own developed components. > > I'll keep you on track of what I'm doing. > > best, > Esteban > > ps: Of course, I want to thank to Stef and Marcus for this great job and all the RMOD team here for being so helpful. Excellent news ! I am happy and I wish you a great job there with RMOD. The biggest challenge will be to manage expectations, your workload and your priorities. I am sure you will do great. Sven

April 2, 2012

Re: [Pharo-project] SciSmalltalk first commit

by Chris Cunningham

On Mon, Apr 2, 2012 at 10:36 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > In order to have something coherent, every sub-librairies of > Sci-Smalltalk should be packaged as 'Math-XXX'. Right now, i have > Math-Random and Math-Random-Tests. > Just curious, why Sci in the name, but Math as the package? I could see that growing over time, but to start with the discrepancy seems odd. Not a problem, just odd. -Chris

April 2, 2012

Re: [Pharo-project] Weird Error with loading Moose in Pharo 1.3 (latest)

by StÃ©phane Ducasse

pay attention that Moose configuration only load in 1.4 now. Stef On Apr 2, 2012, at 7:21 PM, phil(a)highoctane.be wrote: > Weird. > > Now, I got a warning and did a proceed and the VM froze. > > Then I did a new copy of a fresh 1.3 image. > > Loading again led to a VM crash after a long while. > > I am continuing to look. The system loads a ton of packages that's for sure. > > Phil > > 2012/4/2 Dale Henrichs <dhenrich(a)vmware.com> > Philippe, > > I'd like to understand where the '2' came from, could you look up the stack and find the source of the '2', the method and args that lead to to the 2 will help diagnose. > > Dale > > ----- Original Message ----- > | From: phil(a)highoctane.be > | To: pharo-project(a)lists.gforge.inria.fr > | Sent: Monday, April 2, 2012 7:03:32 AM > | Subject: [Pharo-project] Weird Error with loading Moose in Pharo 1.3 (latest) > | > | > | While fetching ConfigurationOfMoose > | > | MessageNotUnderstood SmallInteger>>doesNotUnderstand > | > | > | Coming from > | > | > | MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: > | > | > | reqd "print it" gives 2, a SmallInteger (but isEmpty on reqd isn't > | valid). > | > | > | > | > | > | > | > | resolveToLoadableSpecs: required map: packageMap > | > | > | | reqd allReqd map newReqd spec | > | reqd := required copy. > | allReqd := Set new. > | map := self packages map. > | [ reqd isEmpty ] whileFalse: [ > | newReqd := Set new. > | reqd do: [:req | > | (self resolveToLoadableSpec: req forMap: map packages: packageMap) > | do: [:loadableSpec | > | newReqd addAll: loadableSpec requires. > | newReqd addAll: loadableSpec includes ]]. > | allReqd addAll: reqd. > | newReqd removeAllFoundIn: allReqd. > | reqd := newReqd ]. > | packageMap keys do: [:pkgName | > | (spec := (packageMap at: pkgName) resolveToLoadableSpec) == nil > | ifTrue: [ packageMap removeKey: pkgName ] > | ifFalse: [ packageMap at: pkgName put: (packageMap at: pkgName) > | resolveToLoadableSpec ]] > | > | -- > | > | > | Philippe Back > | "Helping you hit the top 3 outcomes you really want to achieve" > | > | > | Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > | phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > | http://philippeback.be > | > | > | High Octane SPRL > | rue cour Boisacq 101 > | 1301 Bierges > | > > > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges >

April 2, 2012

Re: [Pharo-project] SciSmalltalk first commit

by StÃ©phane Ducasse

On Apr 2, 2012, at 7:36 PM, Serge Stinckwich wrote: > Dear all, > > i made the first commit for the SciSmalltalk project. The code is > available here: > https://github.com/SergeStinckwich/SciSmalltalk just a question why not ss3? > > As a test, i commit the random number generator available here: > http://www.squeaksource.com/Random.html > > I put here a list of potential existing code that could be integrated > in SciSmalltalk: > https://github.com/SergeStinckwich/SciSmalltalk/wiki/Existing-Math-packages… > I will asked the authors if they agree to package their code in SciSmalltalk. > > In order to have something coherent, every sub-librairies of > Sci-Smalltalk should be packaged as 'Math-XXX'. Right now, i have > Math-Random and Math-Random-Tests. > > SciSmalltalk will contain only code released under MIT licence. > > Any comments ? > Best regards, > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ >

April 2, 2012

Re: [Pharo-project] [Pharo-users] Vancouver Smalltalk Developer Meetup Group

by StÃ©phane Ducasse

Ah ok ToolBuilder is an old abstraction we removed. It was a visitor based way of building a UI using different builder. I was however incomplete and not really documented so we decided to simplify everything. On Apr 2, 2012, at 7:08 PM, phil(a)highoctane.be wrote: > No, ToolBuilder. > > ToolBuilder-Kernel > ToolBuilder-Morphic > > ToolBuilder cross-refs: > > MCWorkingCopyBrowser > and > ThreadSafeTranscript>>openAsMorphLabel: aString > > openAsMorphLabel: aString > ^ (self buildWith: ToolBuilder default labeled: aString) > openInWorld; > yourself > " ^UIManager default openTranscript: self asMorphLabel: aString it should a bug. Stef > > So? Looks like interesting but... what's meant in the spec? > > Phil > > > 2012/4/2 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > > How is this related to ToolBuilder in the image? > > You mean UIBuilder? > The idea is that this is quite strange that UIBUilder defines the logic of debugger and other tools building. > Now imagine (as this is done in VW) that a tools has a spec that defines how to populate and link its widgets, then > we would not need to have UIBuilder concentrating too much of the logic. > > stef > > > > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges >

April 2, 2012

Re: [Pharo-project] Weird Error with loading Moose in Pharo 1.3 (latest)

by phil＠highoctane.be

Moose loaded fine after proceeding through the warning (took ages to compile it all). I've got a workspace with: "Tools". MoosePanel open "browse Moose models in root". MooseModel browseMeta "browse metamodel and doc". MOEasel open. "Models". MooseScripts browse "some loading scripts, class-side". MooseModel installDefaultModels. PackageOrganizerCache resetDefault "reset package cache". "Metacello". MooseDevBrowser open "open Moose browser for Metacello". But "Tools". MoosePanel open. "browse Moose models in root". MooseModel browseMeta "browse metamodel and doc". do not work. (Error) MOEasel open. shows a window MooseModel installDefaultModels. isn't in (install... is in red) Next two classes are in red: PackageOrganizerCache resetDefault "reset package cache". "Metacello". MooseDevBrowser open "open Moose browser for Metacello". Phew. 2012/4/2 Dale Henrichs <dhenrich(a)vmware.com> > This warning indicates that there is an unresolved dependency in the Moose > specification ... GLMTreeMorphModel depends upon PaginatedMorphTreeModel > and PaginatedMorphTreeModel was not correctly loaded previously, so this is > a configuration issue of some sort ... > > Dale > > ----- Original Message ----- > | From: phil(a)highoctane.be > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Monday, April 2, 2012 10:25:18 AM > | Subject: Re: [Pharo-project] Weird Error with loading Moose in Pharo 1.3 > (latest) > | > | The warning: > | > | > | > | This package depends on the following classes: > | PaginatedMorphTreeModel > | You must resolve these dependencies before you will be able to load > | these definitions: > | GLMTreeMorphModel > | GLMTreeMorphModel>>acceptDroppingMorph:event:inMorph: > | GLMTreeMorphModel>>allKeystrokeActions > | GLMTreeMorphModel>>allMenuActions > | GLMTreeMorphModel>>amountToFilterBy > | GLMTreeMorphModel>>amountToFilterBy: > | GLMTreeMorphModel>>announce: > | GLMTreeMorphModel>>announcer > | GLMTreeMorphModel>>childrenBlock > | GLMTreeMorphModel>>childrenBlock: > | GLMTreeMorphModel>>defaultPageSize > | GLMTreeMorphModel>>defaultPageSize: > | GLMTreeMorphModel>>displayFormat > | GLMTreeMorphModel>>displayFormat: > | GLMTreeMorphModel>>doSearchOrFilter > | GLMTreeMorphModel>>dragEnabled > | GLMTreeMorphModel>>dragPassengerFor:inMorph: > | GLMTreeMorphModel>>dragTransferType > | GLMTreeMorphModel>>dragTransferTypeForMorph: > | GLMTreeMorphModel>>dropEnabled > | GLMTreeMorphModel>>executeFilter > | GLMTreeMorphModel>>executeSearch > | GLMTreeMorphModel>>explicitSelection: > | GLMTreeMorphModel>>explicitlySelectItem: > | GLMTreeMorphModel>>explicitlySelectMultipleItems: > | GLMTreeMorphModel>>filteredRoots > | GLMTreeMorphModel>>glamourPresentation > | GLMTreeMorphModel>>glamourPresentation: > | GLMTreeMorphModel>>inputText > | GLMTreeMorphModel>>inputText: > | GLMTreeMorphModel>>inputTextEnabled > | GLMTreeMorphModel>>keyStroke:from: > | GLMTreeMorphModel>>menu:shifted: > | GLMTreeMorphModel>>nodeModelFor: > | GLMTreeMorphModel>>onDoubleClick > | GLMTreeMorphModel>>resetChildrenContents > | GLMTreeMorphModel>>resetInput > | GLMTreeMorphModel>>resetTagsToFilterBy > | GLMTreeMorphModel>>rootNodes > | GLMTreeMorphModel>>roots > | GLMTreeMorphModel>>roots: > | GLMTreeMorphModel>>selection: > | GLMTreeMorphModel>>selectionPathItems > | GLMTreeMorphModel>>shouldFilterByAmount > | GLMTreeMorphModel>>shouldFilterByTag: > | GLMTreeMorphModel>>shouldFilterByTextInput > | GLMTreeMorphModel>>tagsToFilterBy > | GLMTreeMorphModel>>toggleAmountToFilterBy > | GLMTreeMorphModel>>toggleFilteringByTag: > | GLMTreeMorphModel>>updateRoots > | GLMTreeMorphModel>>wantsDroppedMorph:event:inMorph: > | GLMTreeMorphModel>>when:do: > | > | > | > | > | Select Proceed to continue, or close this window to cancel the > | operation. > | > | 2012/4/2 Dale Henrichs < dhenrich(a)vmware.com > > | > | > | Philippe, > | > | I'd like to understand where the '2' came from, could you look up the > | stack and find the source of the '2', the method and args that lead > | to to the 2 will help diagnose. > | > | Dale > | > | ----- Original Message ----- > | | From: phil(a)highoctane.be > | | To: pharo-project(a)lists.gforge.inria.fr > | | Sent: Monday, April 2, 2012 7:03:32 AM > | | Subject: [Pharo-project] Weird Error with loading Moose in Pharo > | | 1.3 (latest) > | | > | | > | | While fetching ConfigurationOfMoose > | | > | | MessageNotUnderstood SmallInteger>>doesNotUnderstand > | | > | | > | | Coming from > | | > | | > | | MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: > | | > | | > | | reqd "print it" gives 2, a SmallInteger (but isEmpty on reqd isn't > | | valid). > | | > | | > | | > | | > | | > | | > | | > | | resolveToLoadableSpecs: required map: packageMap > | | > | | > | | | reqd allReqd map newReqd spec | > | | reqd := required copy. > | | allReqd := Set new. > | | map := self packages map. > | | [ reqd isEmpty ] whileFalse: [ > | | newReqd := Set new. > | | reqd do: [:req | > | | (self resolveToLoadableSpec: req forMap: map packages: packageMap) > | | do: [:loadableSpec | > | | newReqd addAll: loadableSpec requires. > | | newReqd addAll: loadableSpec includes ]]. > | | allReqd addAll: reqd. > | | newReqd removeAllFoundIn: allReqd. > | | reqd := newReqd ]. > | | packageMap keys do: [:pkgName | > | | (spec := (packageMap at: pkgName) resolveToLoadableSpec) == nil > | | ifTrue: [ packageMap removeKey: pkgName ] > | | ifFalse: [ packageMap at: pkgName put: (packageMap at: pkgName) > | | resolveToLoadableSpec ]] > | | > | | -- > | | > | | > | | Philippe Back > | | "Helping you hit the top 3 outcomes you really want to achieve" > | | > | | > | | Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > | | phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > | | http://philippeback.be > | | > | | > | | High Octane SPRL > | | rue cour Boisacq 101 > | | 1301 Bierges > | | > | > | > | > | > | > | -- > | > | > | Philippe Back > | "Helping you hit the top 3 outcomes you really want to achieve" > | > | > | Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > | phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > | http://philippeback.be > | > | > | High Octane SPRL > | rue cour Boisacq 101 > | 1301 Bierges > | > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 2, 2012

Re: [Pharo-project] Weird Error with loading Moose in Pharo 1.3 (latest)

by phil＠highoctane.be

#('Croquet Closure Cog VM [CoInterpreter VMMaker-oscog-EstebanLorenzano.139]' 'Win32' 'Win32 built on Mar 12 2012 19:32:09 Compiler: 4.5.2' 'CoInterpreter VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Mar 12 2012' 'StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Mar 12 2012' ' https://git.gitorious.org/cogvm/blessed.git Commit: ca2091e70cfef485fa511935f51d8c91b1c3f185 Date: Mon Mar 12 19:07:33 2012 +0100 By: Igor Stasenko <siguctua(a)gmail.com>') 2012/4/2 Eliot Miranda <eliot.miranda(a)gmail.com> > Hi Phil, > > what version of the VM are you using? e.g. what are the values of > (1004 to: 1009) collect: [:a| Smalltalk getSystemAttribute: a] > > On Mon, Apr 2, 2012 at 10:21 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > >> Weird. >> >> Now, I got a warning and did a proceed and the VM froze. >> >> Then I did a new copy of a fresh 1.3 image. >> >> Loading again led to a VM crash after a long while. >> >> I am continuing to look. The system loads a ton of packages that's for >> sure. >> >> Phil >> >> >> 2012/4/2 Dale Henrichs <dhenrich(a)vmware.com> >> >>> Philippe, >>> >>> I'd like to understand where the '2' came from, could you look up the >>> stack and find the source of the '2', the method and args that lead to to >>> the 2 will help diagnose. >>> >>> Dale >>> >>> ----- Original Message ----- >>> | From: phil(a)highoctane.be >>> | To: pharo-project(a)lists.gforge.inria.fr >>> | Sent: Monday, April 2, 2012 7:03:32 AM >>> | Subject: [Pharo-project] Weird Error with loading Moose in Pharo 1.3 >>> (latest) >>> | >>> | >>> | While fetching ConfigurationOfMoose >>> | >>> | MessageNotUnderstood SmallInteger>>doesNotUnderstand >>> | >>> | >>> | Coming from >>> | >>> | >>> | MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: >>> | >>> | >>> | reqd "print it" gives 2, a SmallInteger (but isEmpty on reqd isn't >>> | valid). >>> | >>> | >>> | >>> | >>> | >>> | >>> | >>> | resolveToLoadableSpecs: required map: packageMap >>> | >>> | >>> | | reqd allReqd map newReqd spec | >>> | reqd := required copy. >>> | allReqd := Set new. >>> | map := self packages map. >>> | [ reqd isEmpty ] whileFalse: [ >>> | newReqd := Set new. >>> | reqd do: [:req | >>> | (self resolveToLoadableSpec: req forMap: map packages: packageMap) >>> | do: [:loadableSpec | >>> | newReqd addAll: loadableSpec requires. >>> | newReqd addAll: loadableSpec includes ]]. >>> | allReqd addAll: reqd. >>> | newReqd removeAllFoundIn: allReqd. >>> | reqd := newReqd ]. >>> | packageMap keys do: [:pkgName | >>> | (spec := (packageMap at: pkgName) resolveToLoadableSpec) == nil >>> | ifTrue: [ packageMap removeKey: pkgName ] >>> | ifFalse: [ packageMap at: pkgName put: (packageMap at: pkgName) >>> | resolveToLoadableSpec ]] >>> | >>> | -- >>> | >>> | >>> | Philippe Back >>> | "Helping you hit the top 3 outcomes you really want to achieve" >>> | >>> | >>> | Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>> | phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>> | http://philippeback.be >>> | >>> | >>> | High Octane SPRL >>> | rue cour Boisacq 101 >>> | 1301 Bierges >>> | >>> >>> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> >> > > > -- > best, > Eliot > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

April 2, 2012

Re: [Pharo-project] [gsoc-mentors] One more project proposal for GSoC

by Stephan Eggermont

On 2 apr 2012, at 19:41, Dennis Schetinin wrote: > The original idea is to build a two-tier Human-Machine Interface (HMI) system (which can be used in a wide range of projects) with Pharo image as back-end (where a model lives) and Amber-based client as a front-end. But this thing seems to be "a little bit" too large for GSoC, isn't it? As long as he's able to define value-delivering small, concrete steps it is ok to have big goals. Stephan

April 2, 2012