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

Re: [Pharo-project] [COTDC] 2 - SmalltalkEditingState

by StÃ©phane Ducasse

I'm the logic behind a texteditor. I'm a kind of strategy object responsible of handling edit operations of an editor such as undo, text emphasis, mouse handle actions. On Feb 5, 2011, at 5:40 PM, laurent laffont wrote: > SmalltalkEditingState

Feb. 5, 2011

Re: [Pharo-project] [COTDC] MCFileRepositoryInspector

by StÃ©phane Ducasse

Gorgeous :) Stef > So I propose a mix of the three propositons: > > I'm a monticello tool composed of three panes to browse repositories and the packages they contain. You get an instance of me when you click on a repository in Monticello browser and press open. > > My left pane presents the packages, my right one their versions and the bottom one the commit log of the selected package versions. > > I underline the packages you already loaded, and highlight the ones you don't have updated to the last version. I also highlight the versions you did not load yet. > > Example: I can browse packages of PharoInbox with: > (MCFileRepositoryInspector > repository: (MCHttpRepository > location: 'http://www.squeaksource.com/PharoInbox' > user: '' > password: '') > workingCopy: nil) show. > > > Laurent. > > > On Sat, Feb 5, 2011 at 1:36 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Let's give it a try: > > I am a Monticello Tool used to inspect the packages and their versions and version summary, for a given repository. > I underline the packages you already loaded, and highlight the ones you don't have updated to the last version. > I also highlight the versions you did not load yet. > > > On Fri, Feb 4, 2011 at 6:41 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > On Fri, Feb 4, 2011 at 9:01 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok after some investigations.... > > I'm a monticello tool composed of three panes to browse repositories and the packages they contain. You get an instance > of me when you click on a repository and press open. My left pane presents the packages, my right one their versions and the > bottom one the commit log of the selected package versions. > > > Indeed I don't understand why MCFileRepositoryInspector is a subclass of MCVersionInspector. MCVersionInspector is a tool to work on one version of a package, while MCFileRepositoryInspector is a browser of all packages and repositories. > > Seems to me that MCFileRepositoryInspector should be a subclass of MCTool directly. > > Laurent > > > > Stef > > > On Feb 4, 2011, at 7:57 PM, laurent laffont wrote: > > > ** 1st Comment Of The Day Contest - One Day One Comment ** > > Rules: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > > > > The first round is for: MCFileRepositoryInspector > > > > GO GO !! > > > > Laurent Laffont - @lolgzs > > > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > > Blog: http://magaloma.blogspot.com/ > > > > >

Feb. 5, 2011

[Pharo-project] [COTDC] 2 - SmalltalkEditingState

by laurent laffont

Comment Of The Day Contest - One Day One Comment Rules: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). Today: SmalltalkEditingState Laurent

Feb. 5, 2011

Re: [Pharo-project] [COTDC] MCFileRepositoryInspector

by laurent laffont

In Inbox: SLICE-Issue-1-COTDC-MCFileRepositoryInspector-LaurentLaffont.1 On Sat, Feb 5, 2011 at 5:28 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > So I propose a mix of the three propositons: > > I'm a monticello tool composed of three panes to browse repositories and > the packages they contain. You get an instance of me when you click on a > repository in Monticello browser and press open. > > My left pane presents the packages, my right one their versions and > the bottom one the commit log of the selected package versions. > > I underline the packages you already loaded, and highlight the ones you > don't have updated to the last version. I also highlight the versions you > did not load yet. > > Example: I can browse packages of PharoInbox with: > (MCFileRepositoryInspector > repository: (MCHttpRepository > location: 'http://www.squeaksource.com/PharoInbox' > user: '' > password: '') > workingCopy: nil) show. > > > Laurent. > > > On Sat, Feb 5, 2011 at 1:36 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Let's give it a try: >> >> I am a Monticello Tool used to inspect the packages and their versions and >> version summary, for a given repository. >> I underline the packages you already loaded, and highlight the ones you >> don't have updated to the last version. >> I also highlight the versions you did not load yet. >> >> >> On Fri, Feb 4, 2011 at 6:41 PM, laurent laffont < >> laurent.laffont(a)gmail.com> wrote: >> >>> On Fri, Feb 4, 2011 at 9:01 PM, StÃ©phane Ducasse < >>> stephane.ducasse(a)inria.fr> wrote: >>> >>>> Ok after some investigations.... >>>> >>>> I'm a monticello tool composed of three panes to browse repositories and >>>> the packages they contain. You get an instance >>>> of me when you click on a repository and press open. My left pane >>>> presents the packages, my right one their versions and the >>>> bottom one the commit log of the selected package versions. >>>> >>> >>> >>> Indeed I don't understand why MCFileRepositoryInspector is a subclass >>> of MCVersionInspector. MCVersionInspector is a tool to work on one version >>> of a package, while MCFileRepositoryInspector is a browser of all packages >>> and repositories. >>> >>> Seems to me that MCFileRepositoryInspector should be a subclass of MCTool >>> directly. >>> >>> Laurent >>> >>> >>> >>>> >>>> Stef >>>> >>>> >>>> On Feb 4, 2011, at 7:57 PM, laurent laffont wrote: >>>> >>>> > ** 1st Comment Of The Day Contest - One Day One Comment ** >>>> > Rules: Each day a not commented class is elected. Each day the best >>>> comment will be integrated with name of the author(s). >>>> > >>>> > The first round is for: MCFileRepositoryInspector >>>> > >>>> > GO GO !! >>>> > >>>> > Laurent Laffont - @lolgzs >>>> > >>>> > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>>> > Blog: http://magaloma.blogspot.com/ >>>> >>>> >>>> >>> >> >

Feb. 5, 2011

Re: [Pharo-project] Build failed in Hudson: Pharo 1.1 #82

by Marcus Denker

.... Lukas fileserver is not reliably online... so all builds fail. Sometimes I really do not like distributed versioning systems... Marcus On Feb 5, 2011, at 5:24 PM, hudson(a)pharo-ic.lille.inria.fr wrote: > See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.1/82/> > > ------------------------------------------ > [...truncated 408 lines...] > > > MetacelloLoaderPolicy>>load > Receiver: a MetacelloLoaderPolicy > Arguments and temporary variables: > > Receiver's instance variables: > overrideRepositories: an Array(a MCDictionaryRepository(cache)) > repositoryMap: a Dictionary('AST-Core-lr.79'->a MCHttpRepository(http://www.squ...etc... > ensuredMap: a Dictionary('AutomaticMethodCategorizer'->#present 'Gofer Core'->#...etc... > cacheRepository: a MCDictionaryRepository(cache) > cacheGofer: nil > ignoreImage: false > loadData: a MetacelloLoadData > loadDirective: linear load : > explicit load : 1.1 [ConfigurationOfPharo] > loa...etc... > silently: true > > > MetacelloFetchingMCSpecLoader>>doLoad > Receiver: a MetacelloFetchingMCSpecLoader(linear load : > explicit load : 1.1 [ConfigurationOfPharo]...etc... > Arguments and temporary variables: > > Receiver's instance variables: > spec: a MetacelloMCVersionSpecLoader > operator: nil > loaderPolicy: a MetacelloLoaderPolicy > disablePackageCache: false > > > [] in [] in MetacelloMCVersion>>doLoadRequiredFromArray: > Receiver: >=1.1 [ConfigurationOfPharo] > Arguments and temporary variables: > fetchLoader: a MetacelloFetchingMCSpecLoader(linear load : > explicit load : 1....etc... > Receiver's instance variables: > spec: spec blessing: #'release'. > spec description: ''. > spec preLoadDoIt: #'prel...etc... > versionNumber: 1.1 > importedVersions: an OrderedCollection('1.1-rc2-baseline') > versionStatus: #loadedMatchConstraints > loaderPolicy: a MetacelloLoaderPolicy > > > MetacelloPharoPlatform(MetacelloPlatform)>>do:displaying: > Receiver: a MetacelloPharoPlatform > Arguments and temporary variables: > aBlock: [fetchLoader doLoad] > aString: 'Loading 1.1 of ConfigurationOfPharo' > Receiver's instance variables: > bypassProgressBars: true > bypassGoferLoadUpdateCategories: false > > > MetacelloPharoPlatform>>do:displaying: > Receiver: a MetacelloPharoPlatform > Arguments and temporary variables: > aBlock: [fetchLoader doLoad] > aString: 'Loading 1.1 of ConfigurationOfPharo' > Receiver's instance variables: > bypassProgressBars: true > bypassGoferLoadUpdateCategories: false > > > [] in MetacelloMCVersion>>doLoadRequiredFromArray: > Receiver: >=1.1 [ConfigurationOfPharo] > Arguments and temporary variables: > anArray: #('default') > displayString: '1.1 of ConfigurationOfPharo' > fetchLoader: a MetacelloFetchingMCSpecLoader(linear load : > explicit load : 1....etc... > Receiver's instance variables: > spec: spec blessing: #'release'. > spec description: ''. > spec preLoadDoIt: #'prel...etc... > versionNumber: 1.1 > importedVersions: an OrderedCollection('1.1-rc2-baseline') > versionStatus: #loadedMatchConstraints > loaderPolicy: a MetacelloLoaderPolicy > > > BlockClosure>>ensure: > Receiver: [| fetchLoader | > fetchLoader := self fetchRequiredFromArray: anArray. > MetacelloPlatform c...etc... > Arguments and temporary variables: > aBlock: [MetacelloPlatform current bypassProgressBars: oldBypassProgress. > load...etc... > complete: nil > returnValue: nil > Receiver's instance variables: > outerContext: MetacelloMCVersion>>doLoadRequiredFromArray: > startpc: 144 > numArgs: 0 > > > MetacelloMCVersion>>doLoadRequiredFromArray: > Receiver: >=1.1 [ConfigurationOfPharo] > Arguments and temporary variables: > anArray: #('default') > displayString: '1.1 of ConfigurationOfPharo' > oldPolicy: a MetacelloLoaderPolicy > oldBypassProgress: false > Receiver's instance variables: > spec: spec blessing: #'release'. > spec description: ''. > spec preLoadDoIt: #'prel...etc... > versionNumber: 1.1 > importedVersions: an OrderedCollection('1.1-rc2-baseline') > versionStatus: #loadedMatchConstraints > loaderPolicy: a MetacelloLoaderPolicy > > > MetacelloMCVersion>>load > Receiver: >=1.1 [ConfigurationOfPharo] > Arguments and temporary variables: > > Receiver's instance variables: > spec: spec blessing: #'release'. > spec description: ''. > spec preLoadDoIt: #'prel...etc... > versionNumber: 1.1 > importedVersions: an OrderedCollection('1.1-rc2-baseline') > versionStatus: #loadedMatchConstraints > loaderPolicy: a MetacelloLoaderPolicy > > > UndefinedObject>>DoIt > Receiver: nil > Arguments and temporary variables: > > Receiver's instance variables: > nil > > Compiler>>evaluate:in:to:notifying:ifFail:logged: > Receiver: a Compiler > Arguments and temporary variables: > textOrStream: '"Dev image" > Gofer new > squeaksource: ''MetacelloRepository''; > p...etc... > aContext: nil > receiver: nil > aRequestor: nil > failBlock: [^ nil] > logFlag: true > methodNode: DoIt > "Dev image" > Gofer new squeaksource: 'MetacelloRepository'; > ...etc... > method: (UndefinedObject>>#DoIt "a CompiledMethod(969408512)") > value: nil > toLog: nil > itsSelection: nil > itsSelectionString: nil > Receiver's instance variables: > sourceStream: a ReadStream '"Dev image" > Gofer new > squeaksource: ''MetacelloRep...etc... > requestor: nil > class: UndefinedObject > category: nil > context: nil > parser: a Parser > > > > --- The full stack --- > RBInternalSpellChecker(Object)>>error: > RBInternalSpellChecker>>loadData > RBInternalSpellChecker>>initialize > RBInternalSpellChecker class(Behavior)>>new > ConfigurationOfRefactoringBrowser>>postLoadRBSpelling > [] in MetacelloPackageSpec(MetacelloSpec)>>doItBlock: > BlockClosure>>valueWithPossibleArgs: > [] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPostloadDirective: > MetacelloPostLoadDirective(MetacelloPrePostLoadDirective)>>evaluateSupplyingAnswers: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPostloadDirective: > MetacelloPostLoadDirective>>loadUsing:gofer: > [] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > OrderedCollection>>do: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > MetacelloLinearLoadDirective>>loadUsing:gofer: > [] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > OrderedCollection>>do: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > MetacelloLinearLoadDirective>>loadUsing:gofer: > [] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > OrderedCollection>>do: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > MetacelloLinearLoadDirective>>loadUsing:gofer: > [] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > OrderedCollection>>do: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > MetacelloLinearLoadDirective>>loadUsing:gofer: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadWithPolicy: > MetacelloLoaderPolicy>>load > MetacelloFetchingMCSpecLoader>>doLoad > [] in [] in MetacelloMCVersion>>doLoadRequiredFromArray: > MetacelloPharoPlatform(MetacelloPlatform)>>do:displaying: > MetacelloPharoPlatform>>do:displaying: > [] in MetacelloMCVersion>>doLoadRequiredFromArray: > BlockClosure>>ensure: > MetacelloMCVersion>>doLoadRequiredFromArray: > MetacelloMCVersion>>load > UndefinedObject>>DoIt > Compiler>>evaluate:in:to:notifying:ifFail:logged: > - - - - - - - - - - - - - - - > - - - - - - - - - - - - - - - - - - > Compiler class>>evaluate:for:notifying:logged: > Compiler class>>evaluate:for:logged: > Compiler class>>evaluate:logged: > [] in [] in RWBinaryOrTextStream(PositionableStream)>>fileInAnnouncing: > BlockClosure>>on:do: > [] in RWBinaryOrTextStream(PositionableStream)>>fileInAnnouncing: > [] in [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>on:do: > [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>ensure: > ProgressInitiationException>>defaultMorphicAction > ProgressInitiationException>>defaultAction > UndefinedObject>>handleSignal: > ProgressInitiationException(Exception)>>signal > ProgressInitiationException>>display:at:from:to:during: > ProgressInitiationException class>>display:at:from:to:during: > ByteString(String)>>displayProgressAt:from:to:during: > RWBinaryOrTextStream(PositionableStream)>>fileInAnnouncing: > RWBinaryOrTextStream(PositionableStream)>>fileIn > CodeLoader>>installSourceFile: > [] in CodeLoader>>installSourceFiles > Array(SequenceableCollection)>>do: > CodeLoader>>installSourceFiles > ProjectLauncher>>startUpAfterLogin > ProjectLauncher>>startUp > [] in [] in AutoStart class>>startUp: > WorldState>>runStepMethodsIn: > PasteUpMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > PasteUpMorph>>doOneCycle > [] in Project class>>spawnNewProcess > [] in BlockClosure>>newProcess > ------------------------------------------------------------ > > Archiving artifacts > Enregistrement des rÃ©sultats des tests > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 5, 2011

Re: [Pharo-project] [COTDC] MCFileRepositoryInspector

by laurent laffont

So I propose a mix of the three propositons: I'm a monticello tool composed of three panes to browse repositories and the packages they contain. You get an instance of me when you click on a repository in Monticello browser and press open. My left pane presents the packages, my right one their versions and the bottom one the commit log of the selected package versions. I underline the packages you already loaded, and highlight the ones you don't have updated to the last version. I also highlight the versions you did not load yet. Example: I can browse packages of PharoInbox with: (MCFileRepositoryInspector repository: (MCHttpRepository location: 'http://www.squeaksource.com/PharoInbox' user: '' password: '') workingCopy: nil) show. Laurent. On Sat, Feb 5, 2011 at 1:36 AM, Guillermo Polito <guillermopolito(a)gmail.com>wrote: > Let's give it a try: > > I am a Monticello Tool used to inspect the packages and their versions and > version summary, for a given repository. > I underline the packages you already loaded, and highlight the ones you > don't have updated to the last version. > I also highlight the versions you did not load yet. > > > On Fri, Feb 4, 2011 at 6:41 PM, laurent laffont <laurent.laffont(a)gmail.com > > wrote: > >> On Fri, Feb 4, 2011 at 9:01 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> Ok after some investigations.... >>> >>> I'm a monticello tool composed of three panes to browse repositories and >>> the packages they contain. You get an instance >>> of me when you click on a repository and press open. My left pane >>> presents the packages, my right one their versions and the >>> bottom one the commit log of the selected package versions. >>> >> >> >> Indeed I don't understand why MCFileRepositoryInspector is a subclass >> of MCVersionInspector. MCVersionInspector is a tool to work on one version >> of a package, while MCFileRepositoryInspector is a browser of all packages >> and repositories. >> >> Seems to me that MCFileRepositoryInspector should be a subclass of MCTool >> directly. >> >> Laurent >> >> >> >>> >>> Stef >>> >>> >>> On Feb 4, 2011, at 7:57 PM, laurent laffont wrote: >>> >>> > ** 1st Comment Of The Day Contest - One Day One Comment ** >>> > Rules: Each day a not commented class is elected. Each day the best >>> comment will be integrated with name of the author(s). >>> > >>> > The first round is for: MCFileRepositoryInspector >>> > >>> > GO GO !! >>> > >>> > Laurent Laffont - @lolgzs >>> > >>> > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>> > Blog: http://magaloma.blogspot.com/ >>> >>> >>> >> >

Feb. 5, 2011

Re: [Pharo-project] Issue 3154 in pharo: FSMemoryFileSystem does not store timestamps

by pharo＠googlecode.com

Comment #2 on issue 3154 by damien.p...(a)gmail.com: FSMemoryFileSystem does not store timestamps http://code.google.com/p/pharo/issues/detail?id=3154 Work in progress in PharoTaskForces. Previously existing tests are green but the new functionality is not explicitly tested yet.

Feb. 5, 2011

[Pharo-project] Issue 3659 in pharo: Task bar appearance does not make sense

by pharo＠googlecode.com

Status: Accepted Owner: damien.p...(a)gmail.com Labels: Type-RequestForEnhancement Importance-Low New issue 3659 by damien.p...(a)gmail.com: Task bar appearance does not make sense http://code.google.com/p/pharo/issues/detail?id=3659 Pharo 1.2rc2 Pharo core version: 12330 The buttons in the task bar are: - frontmost window: gray background + black text - background windows: gray background + gray text - hidden windows: blue gradient + gray text To me these are bad affordances, because gray text signifies "inactive or hidden" and color background means "active" or "current" (see the instance/class side buttons in the browser. So I'd change the appearances to reflect that: - window visibility = text color (black = visible, gray = hidden) - gradient color = blue for the frontmost window\

Feb. 5, 2011

Re: [Pharo-project] [squeak-dev] [ANN] New article on using callbacks in Reef

by StÃ©phane Ducasse

thanks! On Feb 5, 2011, at 2:38 PM, Esteban Lorenzano wrote: > Hi, > I just published an article on using callbacks in Reef framework. > You can read it here: http://smallworks.com.ar/en/community/Reef/reefSimpleTutorialPart2 > > I know, it is very delayed with my latest promises, but there are a "deadline collision" with this and Reef documentation it's coming out as soon as possible :) > > well... enjoy and any observation is really well-welcome. > > best, > Esteban >

Feb. 5, 2011

[Pharo-project] Issue 3658 in pharo: Dictionaries corrupt when loaded from image segment

by pharo＠googlecode.com

Status: Accepted Owner: adrian.l...(a)gmail.com New issue 3658 by adrian.l...(a)gmail.com: Dictionaries corrupt when loaded from image segment http://code.google.com/p/pharo/issues/detail?id=3658 Set and Dictionary were refactored and a common superclass HashedCollection introduced. All existing code that assumes that Dictionary is a subclass of Set must be fixed. One such case that was overseen is in image segment where ... isKindOf: Set fails to capture dictionaries. This leads to potentially corrupted instances once dictionaries are loaded into the image through an image segment. The attached changeset fixes this instance of the problem. Attachments: FixImgSegHashedCollections.1.cs 2.1 KB

Feb. 5, 2011