July 2014 - Pharo-dev - lists.pharo.org

Spotlight2 for Pharo40?

by stepharo

Hi sean and users of Spotlight2 I did not tried it yet but I would like to know - is it working the way you want? - is it working in 40? - what about replacing the old one with this one? Stef

July 19, 2014

Re: [Pharo-dev] New Cog VMs available

by stepharo

Thanks eliot. This is cool to see all these fixes and progress from the VM side. Stef On 19/7/14 04:04, Eliot Miranda wrote: > ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3048. > > CogVM source as per VMMaker.oscog-eem.826/r3048 > > Fix the ZipPlugin (InflatePlugin&DeflatePlugin) to no longer depend on > specific > instance sizes for ReadStream and WriteStream which allows some > leniency in > redefining these classes. Fixes occasionaly Monticello commit bugs with > large packages after loading Collections-eem.567. > > Fix compilation warnings in stringForCString: > > Add a -warnpid flag that causes warning to print the pid; > useful in debugging multi-image tests (i.e. magma). > > Reimplement the backward count in interpreted methods, storing the count > in IFrameFlags, hence eliminating the requirement that the jump happens > consecutively N times in a single method with no backward jumps in any > other > method. The Chameneos benchmark has this pattern and so two methods don't > get jitted. This eliminates lastBackwardJumpMethod & backwardJumpCount. > > Spur: > Fix bad bug in remapObj: that confused the test for old vs > new and hence tried to copyAndForward old objects. > > Fix bug in processWeaklings that could remember a weak object twice. > > Mark the methods used by SpurMemoryManager>>globalGarbageCollect as > inline: #never for profiling. > > Spur Newspeak: > Initialize numIRCs before checking for quick prims. > > > -- > best, > Eliot

July 19, 2014

Re: [Pharo-dev] UITheme experience (please read) :)

by stepharo

Hi doru I think that there are two points: - moving creation API from theme to classes (I'm doing this one to also create example of the widgets) Smalltalk ui theme newButton.... sucks :) - rethinking the theming architecture Stef On 19/7/14 14:16, Tudor Girba wrote: > Hi Stef, > > I do not have time right now to go into details, so take this just as > an acknowledgment that I have an interest in this topic :). > > My initial proposal that I sent to this list a while ago (some details > are provided here: > http://www.humane-assessment.com/blog/a-pharo-refactoring-story-adding-them…) > went exactly in the direction of a ThemeStrategy that I call Themer. > We used it already for several morphs around Glamour to play with the > boundaries and it works well. > > I still think we need the UITheme but that should only provide a list > of themers without any implementation. Like that we can package a > uniform look throughout the whole environment. However, we should > still be able to override the themer at the level of morph for quick > prototyping and custom needs. > > I will get back to you. > > Cheers, > Doru > > > > > On Sat, Jul 19, 2014 at 9:15 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi guys > > I want to lower the importance of UITheme > > - first the factory API should be pushed in the respective classes > ie: > > UItheme>>newButtonIn: aThemedMorph for: aModel getState: stateSel > action: actionSel arguments: args getEnabled: enabledSel getLabel: > labelSel help: helpText > "Answer a new button." > > |b| > b := PluggableButtonMorph > on: aModel > getState: stateSel > action: actionSel > label: labelSel. > b > theme: self; > label: ' ' font: self buttonFont; > update: labelSel; > arguments: (args ifNil: [{b}]); > getEnabledSelector: enabledSel; > cornerStyle: (self buttonCornerStyleIn: aThemedMorph); > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > setBalloonText: helpText; > extent: b minExtent; > removeProperty: #theme. > ^b > > > should be transformed into > > PluggableButtonMorph>>newButtonFor: aModel getState: stateSel > action: actionSel arguments: args getEnabled: enabledSel label: > label help: helpText > "Answer a new button." > > | b | > b := self on: aModel getState: stateSel action: actionSel. > b > arguments: (args ifNil: [{b}]); > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > label: label ; > getEnabledSelector: enabledSel; > setBalloonText: helpText; > extent: b minExtent; > hResizing: #rigid; > vResizing: #rigid. > ^b > > > Now I do not want to lose the theme so I'm working on that. > > - second I wanted to experiment with the theming architecture > > I did the following > > XPGrowlMorph > > Object < XPGrowlThemeStrategy > parentTheme := UITheme new > > XPGrowlThemeStrategy < XPGrowlDarkTheme > parentTheme := PharoDarkTheme new > growFillColor: > Color white > XPGrowlThemeStrategy < XPGrowlPharo30Theme > parentTheme := Pharo30Theme new > growFillColor: > Color red > minTextSize > ^ parentTheme minTextSize > > I did the same with XPSimpleButtonMorph > > > Conclusion: > > - Do we gain from object inheritance vs class? > I do not think that we want to change dynamical the theme chain > So I will make the widget strategy class from their theme > > PharoDarkTheme < XPGrowlDarkTheme > > Pharo30Theme < XPGrowlPharo30Theme > > - cons we may have duplicated behavior accross theme => traits? > > - Do we gain having widgets specific theming strategy > - cons this generate a lot of classes > so we will see > > + with inheritance we reuse a lot > + probably we can reduce the API of UItheme (see below) > > > - Can we reduce the API of UITheme > buttonBorderColor > listBorderColor > â¦. > > Yes probably doing > > Pharo3Theme>>buttonBorderColor > > => > > Pharo30ButtonStrategy>>borderColor > > -> but should be experimented > > > - From a widget point of view, if we want to have possibility to > see the same widgets in different theme at the same time > this raises the problem of the injection (or recomputation) of the > theme values. > Example below: > We want to specify a theme but the new is calling initialize and > the values are computed with a default/current theme. > > > XPGrowlMorph new > theme: XPPharo3ThemeStrategy new; > label: 'The time' contents: TimeStamp now; > skin; > openInWorld. > > XPGrowlMorph new > theme: XPDarkThemeStrategy new; > label: 'The time' contents: TimeStamp now; > openInWorld. > > => Question is it worth because with a default theme we would have > it nearly working. > > Stef > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

July 19, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 5197e7: 40101

by stepharo

Thanks a lot for these ones. stef On 19/7/14 08:57, GitHub wrote: > 13589 deprecated TimeStamp > https://pharo.fogbugz.com/f/cases/13589 > > 13590 TimeStamp has still instances > https://pharo.fogbugz.com/f/cases/13590

July 19, 2014

Re: [Pharo-dev] UITheme experience (please read) :)

by stepharo

On 19/7/14 14:16, Tudor Girba wrote: > Hi Stef, > > I do not have time right now to go into details, so take this just as > an acknowledgment that I have an interest in this topic :). > > My initial proposal that I sent to this list a while ago (some details > are provided here: > http://www.humane-assessment.com/blog/a-pharo-refactoring-story-adding-them…) > went exactly in the direction of a ThemeStrategy that I call Themer. > We used it already for several morphs around Glamour to play with the > boundaries and it works well. Thanks I will read it. I'm redoing the experience without object delegation but inheritance (but this is a "detail"). > > I still think we need the UITheme but that should only provide a list > of themers without any implementation. Like that we can package a > uniform look throughout the whole environment. However, we should > still be able to override the themer at the level of morph for quick > prototyping and custom needs. > > I will get back to you. OKi > > Cheers, > Doru > > > > > On Sat, Jul 19, 2014 at 9:15 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi guys > > I want to lower the importance of UITheme > > - first the factory API should be pushed in the respective classes > ie: > > UItheme>>newButtonIn: aThemedMorph for: aModel getState: stateSel > action: actionSel arguments: args getEnabled: enabledSel getLabel: > labelSel help: helpText > "Answer a new button." > > |b| > b := PluggableButtonMorph > on: aModel > getState: stateSel > action: actionSel > label: labelSel. > b > theme: self; > label: ' ' font: self buttonFont; > update: labelSel; > arguments: (args ifNil: [{b}]); > getEnabledSelector: enabledSel; > cornerStyle: (self buttonCornerStyleIn: aThemedMorph); > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > setBalloonText: helpText; > extent: b minExtent; > removeProperty: #theme. > ^b > > > should be transformed into > > PluggableButtonMorph>>newButtonFor: aModel getState: stateSel > action: actionSel arguments: args getEnabled: enabledSel label: > label help: helpText > "Answer a new button." > > | b | > b := self on: aModel getState: stateSel action: actionSel. > b > arguments: (args ifNil: [{b}]); > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > label: label ; > getEnabledSelector: enabledSel; > setBalloonText: helpText; > extent: b minExtent; > hResizing: #rigid; > vResizing: #rigid. > ^b > > > Now I do not want to lose the theme so I'm working on that. > > - second I wanted to experiment with the theming architecture > > I did the following > > XPGrowlMorph > > Object < XPGrowlThemeStrategy > parentTheme := UITheme new > > XPGrowlThemeStrategy < XPGrowlDarkTheme > parentTheme := PharoDarkTheme new > growFillColor: > Color white > XPGrowlThemeStrategy < XPGrowlPharo30Theme > parentTheme := Pharo30Theme new > growFillColor: > Color red > minTextSize > ^ parentTheme minTextSize > > I did the same with XPSimpleButtonMorph > > > Conclusion: > > - Do we gain from object inheritance vs class? > I do not think that we want to change dynamical the theme chain > So I will make the widget strategy class from their theme > > PharoDarkTheme < XPGrowlDarkTheme > > Pharo30Theme < XPGrowlPharo30Theme > > - cons we may have duplicated behavior accross theme => traits? > > - Do we gain having widgets specific theming strategy > - cons this generate a lot of classes > so we will see > > + with inheritance we reuse a lot > + probably we can reduce the API of UItheme (see below) > > > - Can we reduce the API of UITheme > buttonBorderColor > listBorderColor > â¦. > > Yes probably doing > > Pharo3Theme>>buttonBorderColor > > => > > Pharo30ButtonStrategy>>borderColor > > -> but should be experimented > > > - From a widget point of view, if we want to have possibility to > see the same widgets in different theme at the same time > this raises the problem of the injection (or recomputation) of the > theme values. > Example below: > We want to specify a theme but the new is calling initialize and > the values are computed with a default/current theme. > > > XPGrowlMorph new > theme: XPPharo3ThemeStrategy new; > label: 'The time' contents: TimeStamp now; > skin; > openInWorld. > > XPGrowlMorph new > theme: XPDarkThemeStrategy new; > label: 'The time' contents: TimeStamp now; > openInWorld. > > => Question is it worth because with a default theme we would have > it nearly working. > > Stef > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

July 19, 2014

Re: [Pharo-dev] [Pharo4] First Class Global Variables

by Marcus Denker

On 18 Jul 2014, at 09:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 18 Jul 2014, at 08:14, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >>>> >>>> I have added a first GlobalVar hierarchyâ¦ it has already the code generation methods but Opal is not yet forwarding >>>> code generation (and the compiler does not yet compile bindings with the subclass). >>>> >>> >>> update 40 095 contains changes to deeper integrate first class variables (Slots and first class Globals) int the system. >>> >>> 1) Both the binding in "Smalltalk globals" as well as all Class Variables are now instances of GlobalVariable. >>> (I want to have both GlobalVariable and ClassVariable, but that is for later) >>> >>> e.g. >>> >>> Object binding class >>> (SmalltalkImage classVariableNamed: 'ShutDownList') class >>> >>> all the Slots and Globals understand >>> >>> #definingClass -> returns the class defining the variable or "nil" for true globals >>> #usingMethods -> all methods reading or writing the variable >>> in Pharo4 #102: -> CompiledMethod now has working #readsSlot:, #writesSlot: besides #accessesSlot: (for speed we could dispatch them to the Slot so slots could use faster ways than AST searchingâ¦ but then, speed is fast after the AST is cachedâ¦ #usingMethods already does that for IvarSlot to avoid creating the AST for all methods of a class, which indeed is slow the first time) e.g. (Point>>#setX:setY:) writesSlot: (Point slotNamed: #y) â> true Point methodsWritingSlot: (Point slotNamed: #x) â> {Point>>#bitShiftPoint:. Point>>#setX:setY:. Point>>#setR:degrees:} (Point slotNamed: #x) usingMethods size â> 60 (SmalltalkImage classVariableNamed: 'ShutDownList') usingMethods size â> 7 -> after having fun with #usingMethods on variables, I added #senders and #implementors to Symbol. So now one can use (e.g. nice for doing Demos): #+ senders size. #+ implementors inspect Marcus

July 19, 2014

[pharo-project/pharo-core]

by GitHub

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

July 19, 2014

[pharo-project/pharo-core] e2a432: 40102

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: e2a432c82439b4b75e3bc6de399c348e51f4729a https://github.com/pharo-project/pharo-core/commit/e2a432c82439b4b75e3bc6de… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-19 (Sat, 19 Jul 2014) Changed paths: M Kernel.package/CompiledMethod.class/instance/scanning/readsSlot_.st M Kernel.package/CompiledMethod.class/instance/scanning/writesSlot_.st A KernelTests.package/BehaviorTest.class/instance/tests - queries/testMethodsAccessingSlot.st A KernelTests.package/BehaviorTest.class/instance/tests - queries/testMethodsReadingSlot.st A KernelTests.package/BehaviorTest.class/instance/tests - queries/testMethodsWritingSlot.st A KernelTests.package/CompiledMethodTest.class/instance/tests - slots/testAccessesSlot.st A KernelTests.package/CompiledMethodTest.class/instance/tests - slots/testReadsSlot.st A KernelTests.package/CompiledMethodTest.class/instance/tests - slots/testWritesSlot.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/README.md R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/definition.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/addPaneMorph_.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/closeWindowSelector.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/closeWindowSelector_.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/getChildrenSelector.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/getChildrenSelector_.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/getLabelSelector.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/getLabelSelector_.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/label.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/accessing/label_.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/initialization/delete.st R Morphic-Widgets-Windows.package/PluggableSystemWindow.class/instance/updating/update_.st R Nautilus.package/AbstractNautilusUI.class/instance/annotation pane/annotationSeparator.st R Nautilus.package/AbstractNautilusUI.class/instance/annotation pane/defaultAnnotationInfo.st R Nautilus.package/Nautilus.class/class/private/defaultAnnotationInfo.st M NautilusCommon.package/AnnotationRequest.class/instance/actions/annotationRequests.st A NautilusCommon.package/AnnotationRequest.class/instance/actions/defaultAnnotationInfo.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script102.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40102.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Settings-Tools.package/CodeHolderSystemSettings.class/class/settings/codeEditingSettingsOn_.st M Tool-Profilers.package/MessageTally.class/class/spying/spyAllOn_cutoff_.st M Tool-Profilers.package/MessageTally.class/class/spying/spyOnProcess_forMilliseconds_reportOtherProcesses_.st M Tool-Profilers.package/MessageTally.class/class/spying/spyOn_reportOtherProcesses_cutoff_openResultWindow_closeAfter_.st M Tool-Profilers.package/MessageTally.class/class/spying/tallySendsTo_inBlock_showTree_closeAfter_openResultWindow_.st A Tools.package/CodeHolder.class/class/annotationsreq/annotationRequests.st A Tools.package/CodeHolder.class/class/annotationsreq/defaultAnnotationInfo.st R Tools.package/CodeHolder.class/class/settings/annotationRequests.st R Tools.package/CodeHolder.class/class/settings/annotationRequests_.st R Tools.package/CodeHolder.class/class/settings/defaultAnnotationInfo.st R Tools.package/CodeHolder.class/class/settings/optionalButtons.st R Tools.package/CodeHolder.class/class/settings/optionalButtons_.st R Tools.package/CodeHolder.class/class/settings/smartUpdating.st R Tools.package/CodeHolder.class/class/settings/smartUpdating_.st M Tools.package/CodeHolder.class/definition.st M Tools.package/CodeHolder.class/instance/construction/addOptionalButtonsTo_at_plus_.st M Tools.package/CodeHolder.class/instance/self-updating/wantsStepsIn_.st R Tools.package/CodeHolder.class/instance/setting/wantsOptionalButtons.st Log Message: ----------- 40102 13594 Reduce references to CodeHolder https://pharo.fogbugz.com/f/cases/13594 13597 Implement #readsSlot and #writesSlot on CompiledMethod (and tests) https://pharo.fogbugz.com/f/cases/13597 13595 PluggableSystemWindow is dead code https://pharo.fogbugz.com/f/cases/13595 13596 remove package TT.cs https://pharo.fogbugz.com/f/cases/13596 http://files.pharo.org/image/40/40102.zip

July 19, 2014

Re: [Pharo-dev] UITheme experience (please read) :)

by Tudor Girba

Hi Stef, I do not have time right now to go into details, so take this just as an acknowledgment that I have an interest in this topic :). My initial proposal that I sent to this list a while ago (some details are provided here: http://www.humane-assessment.com/blog/a-pharo-refactoring-story-adding-them…) went exactly in the direction of a ThemeStrategy that I call Themer. We used it already for several morphs around Glamour to play with the boundaries and it works well. I still think we need the UITheme but that should only provide a list of themers without any implementation. Like that we can package a uniform look throughout the whole environment. However, we should still be able to override the themer at the level of morph for quick prototyping and custom needs. I will get back to you. Cheers, Doru On Sat, Jul 19, 2014 at 9:15 AM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > I want to lower the importance of UITheme > > - first the factory API should be pushed in the respective classes > ie: > > UItheme>>newButtonIn: aThemedMorph for: aModel getState: stateSel action: > actionSel arguments: args getEnabled: enabledSel getLabel: labelSel help: > helpText > "Answer a new button." > > |b| > b := PluggableButtonMorph > on: aModel > getState: stateSel > action: actionSel > label: labelSel. > b > theme: self; > label: ' ' font: self buttonFont; > update: labelSel; > arguments: (args ifNil: [{b}]); > getEnabledSelector: enabledSel; > cornerStyle: (self buttonCornerStyleIn: aThemedMorph); > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > setBalloonText: helpText; > extent: b minExtent; > removeProperty: #theme. > ^b > > > should be transformed into > > PluggableButtonMorph>>newButtonFor: aModel getState: stateSel action: > actionSel arguments: args getEnabled: enabledSel label: label help: helpText > "Answer a new button." > > | b | > b := self on: aModel getState: stateSel action: actionSel. > b > arguments: (args ifNil: [{b}]); > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > label: label ; > getEnabledSelector: enabledSel; > setBalloonText: helpText; > extent: b minExtent; > hResizing: #rigid; > vResizing: #rigid. > ^b > > > Now I do not want to lose the theme so I'm working on that. > > - second I wanted to experiment with the theming architecture > > I did the following > > XPGrowlMorph > > Object < XPGrowlThemeStrategy > parentTheme := UITheme new > > XPGrowlThemeStrategy < XPGrowlDarkTheme > parentTheme := PharoDarkTheme new > growFillColor: > Color white > XPGrowlThemeStrategy < XPGrowlPharo30Theme > parentTheme := Pharo30Theme new > growFillColor: > Color red > minTextSize > ^ parentTheme minTextSize > > I did the same with XPSimpleButtonMorph > > > Conclusion: > > - Do we gain from object inheritance vs class? > I do not think that we want to change dynamical the theme chain > So I will make the widget strategy class from their theme > > PharoDarkTheme < XPGrowlDarkTheme > > Pharo30Theme < XPGrowlPharo30Theme > > - cons we may have duplicated behavior accross theme => traits? > > - Do we gain having widgets specific theming strategy > - cons this generate a lot of classes > so we will see > > + with inheritance we reuse a lot > + probably we can reduce the API of UItheme (see below) > > > - Can we reduce the API of UITheme > buttonBorderColor > listBorderColor > â¦. > > Yes probably doing > > Pharo3Theme>>buttonBorderColor > > => > > Pharo30ButtonStrategy>>borderColor > > -> but should be experimented > > > - From a widget point of view, if we want to have possibility to see the > same widgets in different theme at the same time > this raises the problem of the injection (or recomputation) of the theme > values. > Example below: > We want to specify a theme but the new is calling initialize and the > values are computed with a default/current theme. > > > XPGrowlMorph new > theme: XPPharo3ThemeStrategy new; > label: 'The time' contents: TimeStamp now; > skin; > openInWorld. > > XPGrowlMorph new > theme: XPDarkThemeStrategy new; > label: 'The time' contents: TimeStamp now; > openInWorld. > > => Question is it worth because with a default theme we would have it > nearly working. > > Stef > > > -- www.tudorgirba.com "Every thing has its own flow"

July 19, 2014

UITheme experience (please read) :)

by stepharo

Hi guys I want to lower the importance of UITheme - first the factory API should be pushed in the respective classes ie: UItheme>>newButtonIn: aThemedMorph for: aModel getState: stateSel action: actionSel arguments: args getEnabled: enabledSel getLabel: labelSel help: helpText "Answer a new button." |b| b := PluggableButtonMorph on: aModel getState: stateSel action: actionSel label: labelSel. b theme: self; label: ' ' font: self buttonFont; update: labelSel; arguments: (args ifNil: [{b}]); getEnabledSelector: enabledSel; cornerStyle: (self buttonCornerStyleIn: aThemedMorph); hResizing: #shrinkWrap; vResizing: #shrinkWrap; setBalloonText: helpText; extent: b minExtent; removeProperty: #theme. ^b should be transformed into PluggableButtonMorph>>newButtonFor: aModel getState: stateSel action: actionSel arguments: args getEnabled: enabledSel label: label help: helpText "Answer a new button." | b | b := self on: aModel getState: stateSel action: actionSel. b arguments: (args ifNil: [{b}]); hResizing: #shrinkWrap; vResizing: #shrinkWrap; label: label ; getEnabledSelector: enabledSel; setBalloonText: helpText; extent: b minExtent; hResizing: #rigid; vResizing: #rigid. ^b Now I do not want to lose the theme so I'm working on that. - second I wanted to experiment with the theming architecture I did the following XPGrowlMorph Object < XPGrowlThemeStrategy parentTheme := UITheme new XPGrowlThemeStrategy < XPGrowlDarkTheme parentTheme := PharoDarkTheme new growFillColor: Color white XPGrowlThemeStrategy < XPGrowlPharo30Theme parentTheme := Pharo30Theme new growFillColor: Color red minTextSize ^ parentTheme minTextSize I did the same with XPSimpleButtonMorph Conclusion: - Do we gain from object inheritance vs class? I do not think that we want to change dynamical the theme chain So I will make the widget strategy class from their theme PharoDarkTheme < XPGrowlDarkTheme Pharo30Theme < XPGrowlPharo30Theme - cons we may have duplicated behavior accross theme => traits? - Do we gain having widgets specific theming strategy - cons this generate a lot of classes so we will see + with inheritance we reuse a lot + probably we can reduce the API of UItheme (see below) - Can we reduce the API of UITheme buttonBorderColor listBorderColor â¦. Yes probably doing Pharo3Theme>>buttonBorderColor => Pharo30ButtonStrategy>>borderColor -> but should be experimented - From a widget point of view, if we want to have possibility to see the same widgets in different theme at the same time this raises the problem of the injection (or recomputation) of the theme values. Example below: We want to specify a theme but the new is calling initialize and the values are computed with a default/current theme. XPGrowlMorph new theme: XPPharo3ThemeStrategy new; label: 'The time' contents: TimeStamp now; skin; openInWorld. XPGrowlMorph new theme: XPDarkThemeStrategy new; label: 'The time' contents: TimeStamp now; openInWorld. => Question is it worth because with a default theme we would have it nearly working. Stef

July 19, 2014