June 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60107 Home: https://github.com/pharo-project/pharo-core

June 22, 2016

Re: [Pharo-dev] senders seems broken

by Marcus Denker

There where bugs but they should be fixed in the latest version. (in 60105 it works for me again). > On 22 Jun 2016, at 15:53, stepharo <stepharo(a)free.fr> wrote: > > Hi marcus > > can you browse senders? Because I cannot anymore. > > Stef > >

June 22, 2016

<primitive: 79 error: ec> question

by stepharo

Hi I want to explain where ec is coming. I thought that the arguments of pragmas could only be literal and when I see ec it looks like a variable set by the VM newMethod: numberOfBytes header: headerWord "Primitive. Answer an instance of me. The number of literals (and other information) is specified by the headerWord (see my class comment). The first argument specifies the number of fields for bytecodes in the method. Fail if either argument is not a SmallInteger, or if numberOfBytes is negative, or if memory is low. Once the header of a method is set by this primitive, it cannot be changed to change the number of literals. Essential. See Object documentation whatIsAPrimitive." <primitive: 79 error: ec> ec == #'insufficient object memory' ifTrue: [^self handleFailingNewMethod: numberOfBytes header: headerWord]. ^self primitiveFailed Stef

June 22, 2016

Re: [Pharo-dev] NonInteractiveUIManager vs. Epicea

by stepharo

Le 22/6/16 Ã 14:35, Martin Dias a Ã©crit : > > > On Wed, Jun 22, 2016 at 4:31 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > > Le 22/6/16 Ã 00:23, Holger Freyther a Ã©crit : > > Hi, > > would fogbugz be the better place for reports like this? It > looks like the introduction of Epicea has broken my use of > headless images? > > Should >>#initialize use "Smalltalk ui theme" instead of > "UIManager default theme"? > > > Both loosk terrible. but Smalltalk ui theme is really a bad idea. > We should really remove this cancer XXX ff zz > > > I used it in a morph-builder visitor, that receives an epicea model > object and answers a morph. I only access the textColor, but I can > avoid it. > > If a tool need a theme, then it should have an instance variable > theme and this instance var should be well initialized. > This pattern sucks! > > > So, if a morph builder wants to know the textColor and other colors of > the current theme, how to access them? Normally the theme should be know by the builder. No global variable and the tool should register to the Theme and when the theme changed they should change too. Right now all the Smalltalk ui.... is a global variable. Stef > > Martin > > > Stef > > > > NonInteractiveUIManager>>theme > NonInteractiveUIManager(Object)>>doesNotUnderstand: #theme > EpDisplayMorphVisitor>>initialize > EpDisplayMorphVisitor class(Behavior)>>new > EpEntryItem>>displayWidget > [ :item | item displayWidget ] in > EpLogBrowser>>initializeItemsModel in Block: [ :item | item > displayWidget ] > BlockClosure>>cull: > BlockClosure>>cull:cull: > TreeModel>>wrapItem: > [ :node | self wrapItem: node content ] in > TreeModel>>initialize in Block: [ :node | self wrapItem: node > content ] > [ :node :cont | self rowMorphGetSelector value: node ] in > SpecTreeColumn(MorphTreeColumn)>>rowMorphGetterBlock in Block: > [ :node :cont | self rowMorphGetSelector value: no...etc... > SpecTreeColumn>>rowMorphFor: > [ :col | > | v | > v := col rowMorphFor: complexContents. > controls add: v. > col -> v ] in MorphTreeNodeMorph>>buildRowMorph in Block: [ > :col | ... > OrderedCollection>>collect: > MorphTreeNodeMorph>>buildRowMorph > MorphTreeNodeMorph>>initRow > MorphTreeNodeMorph>>initWithContents:prior:forList:indentLevel: > [ :item :idx | > priorMorph := self indentingItemClass new > initWithContents: item > prior: priorMorph > forList: self > indentLevel: newIndent. > firstAddition ifNil: [ firstAddition := priorMorph ]. > morphList add: priorMorph. > "Was this row expanded ? if true -> expand it > again " > ((item hasEquivalentIn: expandedItems) or: [ priorMorph > isExpanded ]) > ifTrue: [ priorMorph isExpanded: true. > priorMorph > addChildrenForList: self > addingTo: morphList > withExpandedItems: expandedItems ] ] > in MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: > in Block: [ :item :idx | ... > OrderedCollection(SequenceableCollection)>>withIndexDo: > OrderedCollection(SequenceableCollection)>>doWithIndex: > MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: > MorphTreeMorph>>addSubmorphsFromNodeList:previouslyExpanded: > MorphTreeMorph>>addSubmorphsFromNodeList > MorphTreeMorph>>buildContents > MorphicTreeAdapter>>buildWidget > MorphicTreeAdapter(AbstractAdapter)>>adapt: > SpecInterpreter>>actionToPerformWithSelector:arguments: > SpecInterpreter>>performNextSelectorAndIncrementIndex > SpecInterpreter>>interpretASpec:selector: > SpecInterpreter>>interpretASpec:model:selector: > SpecInterpreter class>>private_interpretASpec:model:selector: > > > >

June 22, 2016

Re: [Pharo-dev] FuelPlatform. Why we have all those platforms there?

by Max Leske

We already have an issue for that. Using the platform abstraction makes it much easier to maintain Fuel. That was the most important step. Once I have time I will refactor FuelPlatform so that legacy platforms need not be loaded (at least in Pharo). Cheers, Max > On 22 Jun 2016, at 15:30, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > I wonder why we have all those platforms in our system. Why we need them? > > Esteban >

June 22, 2016

Re: [Pharo-dev] shit + double click on a category :)

by stepharo

We should call a method rename and class rename refactoring for classes and methods and it will be gorgeous :) yes it is shift :) Setf Le 22/6/16 Ã 11:50, Denis Kudriashov a Ã©crit : > Really nice. And I found that double click on method opens new browser > on it. > > 2016-06-22 11:44 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Hi guys > > alain showed me that click + double click on a category is really > nice to rename a category. > > May be you knew it but this is nice. > > > Stef > > >

June 22, 2016

senders seems broken

by stepharo

Hi marcus can you browse senders? Because I cannot anymore. Stef

June 22, 2016

FuelPlatform. Why we have all those platforms there?

by Esteban Lorenzano

Hi, I wonder why we have all those platforms in our system. Why we need them? Esteban

June 22, 2016

Re: [Pharo-dev] NonInteractiveUIManager vs. Epicea

by Martin Dias

On Wed, Jun 22, 2016 at 4:31 AM, stepharo <stepharo(a)free.fr> wrote: > > > Le 22/6/16 Ã 00:23, Holger Freyther a Ã©crit : > >> Hi, >> >> would fogbugz be the better place for reports like this? It looks like >> the introduction of Epicea has broken my use of headless images? >> >> Should >>#initialize use "Smalltalk ui theme" instead of "UIManager >> default theme"? >> > > Both loosk terrible. but Smalltalk ui theme is really a bad idea. > We should really remove this cancer XXX ff zz > > I used it in a morph-builder visitor, that receives an epicea model object and answers a morph. I only access the textColor, but I can avoid it. > If a tool need a theme, then it should have an instance variable theme and > this instance var should be well initialized. > This pattern sucks! > So, if a morph builder wants to know the textColor and other colors of the current theme, how to access them? Martin > > Stef > > >> >> NonInteractiveUIManager>>theme >> NonInteractiveUIManager(Object)>>doesNotUnderstand: #theme >> EpDisplayMorphVisitor>>initialize >> EpDisplayMorphVisitor class(Behavior)>>new >> EpEntryItem>>displayWidget >> [ :item | item displayWidget ] in EpLogBrowser>>initializeItemsModel in >> Block: [ :item | item displayWidget ] >> BlockClosure>>cull: >> BlockClosure>>cull:cull: >> TreeModel>>wrapItem: >> [ :node | self wrapItem: node content ] in TreeModel>>initialize in >> Block: [ :node | self wrapItem: node content ] >> [ :node :cont | self rowMorphGetSelector value: node ] in >> SpecTreeColumn(MorphTreeColumn)>>rowMorphGetterBlock in Block: [ :node >> :cont | self rowMorphGetSelector value: no...etc... >> SpecTreeColumn>>rowMorphFor: >> [ :col | >> | v | >> v := col rowMorphFor: complexContents. >> controls add: v. >> col -> v ] in MorphTreeNodeMorph>>buildRowMorph in Block: [ :col | ... >> OrderedCollection>>collect: >> MorphTreeNodeMorph>>buildRowMorph >> MorphTreeNodeMorph>>initRow >> MorphTreeNodeMorph>>initWithContents:prior:forList:indentLevel: >> [ :item :idx | >> priorMorph := self indentingItemClass new >> initWithContents: item >> prior: priorMorph >> forList: self >> indentLevel: newIndent. >> firstAddition ifNil: [ firstAddition := priorMorph ]. >> morphList add: priorMorph. >> "Was this row expanded ? if true -> expand it >> again " >> ((item hasEquivalentIn: expandedItems) or: [ priorMorph isExpanded ]) >> ifTrue: [ priorMorph isExpanded: true. >> priorMorph >> addChildrenForList: self >> addingTo: morphList >> withExpandedItems: expandedItems ] ] in >> MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: in Block: [ >> :item :idx | ... >> OrderedCollection(SequenceableCollection)>>withIndexDo: >> OrderedCollection(SequenceableCollection)>>doWithIndex: >> MorphTreeMorph>>addMorphsTo:from:withExpandedItems:atLevel: >> MorphTreeMorph>>addSubmorphsFromNodeList:previouslyExpanded: >> MorphTreeMorph>>addSubmorphsFromNodeList >> MorphTreeMorph>>buildContents >> MorphicTreeAdapter>>buildWidget >> MorphicTreeAdapter(AbstractAdapter)>>adapt: >> SpecInterpreter>>actionToPerformWithSelector:arguments: >> SpecInterpreter>>performNextSelectorAndIncrementIndex >> SpecInterpreter>>interpretASpec:selector: >> SpecInterpreter>>interpretASpec:model:selector: >> SpecInterpreter class>>private_interpretASpec:model:selector: >> >> > >

June 22, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60106 Home: https://github.com/pharo-project/pharo-core

June 22, 2016