March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

by stepharong

+1 On Tue, 07 Mar 2017 14:58:33 +0100, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Thank you, Andrei, for your continued efforts ! > >> On 7 Mar 2017, at 14:47, denker <marcus.denker(a)inria.fr> wrote: >> >> >>> Log Message: >>> ----------- >>> 60436 >>> Moose >>> >>> http://files.pharo.org/image/60/60436.zip >>> >> >> >> This brings changes to the inspector, debugger and fast table renderer >> for glamour. >> Detailed changes: >> >> - added support for refresh in the Inspector/Playground. The refresh >> uses the stepping mechanism from Morphic. There exists a setting to >> start/stop the refresh. Each presentation can decide if it wants >> refresh or not. >> >> - the Glamour renderer for fast table uses now a LRUCache for storing >> the string representation returned by the #format: block. This is >> disabled by default and configureable per presentation. By default it >> is enabled for the Raw presentation and the collection presentations. >> >> - the debugger now offers access to variables defined in the playground >> when debugging code from the playground >> >> - the inspector uses GTInspectorVariableNode to model variables in the >> Raw view. >> >> - fixed inspector issues with collections >> >> Also fixes issues: >> - case 18899 Raw presentation from the debugger inspector raises error >> when the rawSelection comes from another presentation >> - case 17949 Missing evaluator presentation for the current context in >> debugger >> - case 19753 Disappearing content in the context inspector from >> GTDebugger when tags are used >> - case 19720 Add method scoped [Evaluator] tab to debugger >> - case 14569 GTInspector should do live updates of objects and their >> slots >> >> >> > > -- Using Opera's mail client: http://www.opera.com/mail/

March 7, 2017

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by stepharong

> This is not only when teaching. > > I was at a conference today and showcased some Grafoscopio. > > Spotty wifi and crowded bandwith makes it bad looking. > > We need an "Airplane mode" switch. > > Maybe can we have that available in the session from the settings. :) I think that just having a setting and turning it on in the preferences is the way to go. Stef

March 7, 2017

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by phil＠highoctane.be

I see you are not teaching to people or running demos in a crowd with Pharo. Otherwise, you would get the point I can tell you 100% Phil On Tue, Mar 7, 2017 at 3:19 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Frankly I fail to see the problem, if a tool connects to the internet and > does not have some sort of timeout or speed check then is the obligation of > the tool to fix that and not of Pharo to offer an airplane mode. Its would > make an already complex pharo environment even more complex. Not to exclude > the fact that having two mode will create useless confusion for beginners. > > Offer a new mode for Pharo ? No > Offer methods that check internet connectivity and internet speed for > pharo tool developers to use ? Yes > > I feel that Pharo can be simplified down to 1% without the need for a big > compromise on features. Maybe it does not matter for us that are used to > working with Blender but its a huge deal for beginners and if we want to > attract a lot more new users. > > My dream is that version 8 be dedicated ONLY to simplifying the Pharo > code, by removing all the extra fat. No new bug fixes (unless created by > the removal of the code), no new features. I know we have bootstrap , but > thats a completely different thing. > > On Tue, Mar 7, 2017 at 3:15 PM phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> https://pharo.fogbugz.com/f/cases/19818/Support-for- >> Airplane-mode-in-Pharo for keeping track of this >> >> On Tue, Mar 7, 2017 at 1:02 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >> On Tue, Mar 7, 2017 at 6:35 AM, phil(a)highoctane.be <phil(a)highoctane.be> >> wrote: >> > This is not only when teaching. >> > >> > I was at a conference today and showcased some Grafoscopio. >> > >> > Spotty wifi and crowded bandwith makes it bad looking. >> > >> > We need an "Airplane mode" switch. >> >> That is a cool way to describe it. A well know paradigm. >> Its a setting that probably would change daya to day more than any other, >> so perhaps it would even be reasonable to have this as a permanent >> mode button on the background, >> or the task bar much like MS Windows taskbar status icons. >> >> cheers -ben >> >> > >> > Maybe can we have that available in the session from the settings. >> > >> > Phil >> > >> > On Mon, Mar 6, 2017 at 10:55 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >> >> >> The problem is that there are people who give lectures in universities >> >> with bad internet (internet is bad in most of the universities I >> tried) and >> >> they done want freezes. On the other hand we have people who sit in >> their >> >> offices with fast machines, fast internet and they want features. >> Until now >> >> we were looking at how to satisfy one of the groups and which one >> exactly. >> >> Why not to try finding a solution for both. For example we can have the >> >> plugging enabled by default and have Spotter measuring the time needed >> to do >> >> a query. Whenever the time surpasses frustration limit (10 sec? I duno) >> >> Spotter will ask if the user wants to turn off the plugin, of turns it >> of >> >> automatically and tells where to re-enable it. The other way would be >> to >> >> have known plugins to appear at the bottom of Spotter, and a user can >> >> install/enable them with one click. So when you search but there is >> nothing >> >> you know that there are more plugins that may solve your problem. >> >> >> >> Yes it is more complicated to implement in in a smart way rather them >> just >> >> set the default boolean value of a setting, but we spend too much time >> >> anyway convincing the other side that we are rightâ¦ >> >> >> >> Uko >> >> >> >> > On 6 Mar 2017, at 21:30, stepharong <stepharong(a)free.fr> wrote: >> >> > >> >> > One day I would like to invite you to give a lecture in a not that >> bad >> >> > french university >> >> > with a not that good network. Each time Pharo freezes you pay me 5 >> Euros >> >> > only and we can >> >> > go and pay some really expensive restaurant with your money. >> >> > Simple on my machine it times out every five minutes. >> >> > >> >> > <sorry I could not resist> >> >> > >> >> >> >> >> >>> On 6 Mar 2017, at 19:51, stepharong <stepharong(a)free.fr> wrote: >> >> >>> >> >> >>> We should make it available from the catalog :) >> >> >> >> >> >> Yes, it most certainly should be. >> >> >> >> >> >> If only we could then tell user to type >> >> >> >> >> >> Shift-Enter Sublimish Enter >> >> >> >> >> >> to install it using Spotter right from the catalog ;-) >> >> >> >> >> >> Sorry, I couldn't resist ... <ducking> >> >> >> >> >> >>> 2017-03-06 9:29 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> >>> >> >> >>>> On 6 Mar 2017, at 09:22, Pavel Krivanek <pavel.krivanek(a)gmail.com >> > >> >> >>>> wrote: >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> 2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com >> >: >> >> >>>> >> >> >>>>> On 6 Mar 2017, at 07:57, phil(a)highoctane.be wrote: >> >> >>>>> >> >> >>>>> >> >> >>>>> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator- >> simple/7294/artifact/report.html >> >> >>>>> is not integrated for some Monkey reason anyway - still should >> b/c if you >> >> >>>>> put sublimish, you need a decent matching Spotter. >> >> >>>>> >> >> >>>>> Also, I see >> >> >>>>> https://pharo.fogbugz.com/f/cases/19796/Remove-duplicate- >> code-from-SublimishTheme >> >> >>>>> on 5/3. If this moves forward, why not the other one? >> >> >>>>> >> >> >>>>> BTW Sublimish was an extra thing. Who got that in image? >> >> >>>> >> >> >>>> I donât know. >> >> >>>> It shouldnât :) >> >> >>>> >> >> >>>> What we should do is to create a page for themes and links to it >> (and >> >> >>>> they should be in catalog) :) >> >> >>>> >> >> >>>> Well, it was me who proposed the slice and yes, I was aware of the >> >> >>>> fact that I should not do it because of code freeze (I was not >> aware of the >> >> >>>> two themes policy). >> >> >>> >> >> >>> it is not a policy, it is just the idea I have :) >> >> >>> >> >> >>>> >> >> >>>> We can remove it again, I will prepare a slice. >> >> >>> >> >> >>> problem with it is that is makes ripples. >> >> >>> If community want it (is nice), we can include it, but I would wait >> >> >>> for P7, yes. >> >> >>> >> >> >>> https://pharo.fogbugz.com/f/cases/19801/Remove-SublimishTheme >> >> >>> At least it was an advertisement for this theme that moved it >> forward >> >> >>> and the integration of it helped to improve the dark theme too. >> And showed >> >> >>> again how much we need the concept of palettes used strictly in >> the system. >> >> >>> >> >> >>> -- Pavel >> >> >>> >> >> >>> >> >> >>> >> >> >>> Esteban >> >> >>> >> >> >>>> >> >> >>>> -- Pavel >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> Esteban >> >> >>>> >> >> >>>>> >> >> >>>>> Phil >> >> >>>>> >> >> >>>>> On Mon, Mar 6, 2017 at 7:43 AM, Esteban Lorenzano >> >> >>>>> <estebanlm(a)gmail.com> wrote: >> >> >>>>> >> >> >>>>>> On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm(a)gmail.com >> > >> >> >>>>>> wrote: >> >> >>>>>> >> >> >>>>>> Hi, >> >> >>>>>> >> >> >>>>>> First, let me be clear: I *like* sublimish theme (not for my >> use, >> >> >>>>>> but I like it), and I like (a lot) the windows list on spotter, >> and I like >> >> >>>>>> in general all this new additions. >> >> >>>>> >> >> >>>>> By the way, even if I like it, I would not have integrated >> >> >>>>> SublimishTheme. For same reason I didnât integrated >> DarkMetalTheme: My idea >> >> >>>>> is to have just two themes *in image*: one white, one dark, and >> allow people >> >> >>>>> to install other themes from catalog. >> >> >>>>> >> >> >>>>> Why? Because each class inside image becomes our responsibility >> and >> >> >>>>> then a maintainability issue. With themes in particular already >> happened >> >> >>>>> that existing themes became abandonware inside the image and we >> needed to >> >> >>>>> clean up, not without problems. >> >> >>>>> >> >> >>>>> cheers, >> >> >>>>> Esteban >> >> >>>>> >> >> >>>>> ps: which means also yes: that issue got integrated because I >> failed >> >> >>>>> to control the flow of issues... >> >> >>>>> >> >> >>>>>> >> >> >>>>>> And I know, most of those additions are usability enhancements >> so a >> >> >>>>>> good thing. >> >> >>>>>> >> >> >>>>>> But can you guys stop pushing new features into a (in theory) >> >> >>>>>> frozen version? >> >> >>>>>> >> >> >>>>>> Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. >> If I >> >> >>>>>> can suggest an orientation, it would be good, for those that >> use linux and >> >> >>>>>> mac (windows is not ready), to test and help fix 64bits version. >> >> >>>>>> >> >> >>>>>> There are still plenty of bugs to fix there, like for example >> why >> >> >>>>>> Spotter does not shows search line. >> >> >>>>>> >> >> >>>>>> Last week I added support to Athens and SDL2 in 64bits but that >> >> >>>>>> meant: >> >> >>>>>> >> >> >>>>>> - some important changes in UFFI >> >> >>>>>> - discover something that seems is failing on callbacks for >> Cairo >> >> >>>>>> (no idea if it is a callbacks problem or an image problem that >> causes a >> >> >>>>>> callback problem). >> >> >>>>>> >> >> >>>>>> I would say all this and the fact we are working on 64bits in >> >> >>>>>> general deserves a lot of testing. >> >> >>>>>> >> >> >>>>>> I will add links in Pharo page to download 64bits (Iâm at the >> train >> >> >>>>>> now), but in the mean time you can download all from here: >> >> >>>>>> >> >> >>>>>> http://files.pharo.org/get-files/60/pharo-64.zip >> >> >>>>>> http://files.pharo.org/get-files/60/pharo64-linux-latest.zip >> >> >>>>>> (linux) >> >> >>>>>> http://files.pharo.org/get-files/60/pharo64-mac-latest.zip >> (mac) >> >> >>>>>> http://files.pharo.org/get-files/60/sources.zip (in case you >> need >> >> >>>>>> them) >> >> >>>>>> >> >> >>>>>> cheers, >> >> >>>>>> Esteban >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> -- >> >> >>> Using Opera's mail client: http://www.opera.com/mail/ >> >> >> >> >> >> >> >> > >> >> > >> >> > -- >> >> > Using Opera's mail client: http://www.opera.com/mail/ >> >> > >> >> >> >> >> > >> >> >>

March 7, 2017

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by Dimitris Chloupis

Frankly I fail to see the problem, if a tool connects to the internet and does not have some sort of timeout or speed check then is the obligation of the tool to fix that and not of Pharo to offer an airplane mode. Its would make an already complex pharo environment even more complex. Not to exclude the fact that having two mode will create useless confusion for beginners. Offer a new mode for Pharo ? No Offer methods that check internet connectivity and internet speed for pharo tool developers to use ? Yes I feel that Pharo can be simplified down to 1% without the need for a big compromise on features. Maybe it does not matter for us that are used to working with Blender but its a huge deal for beginners and if we want to attract a lot more new users. My dream is that version 8 be dedicated ONLY to simplifying the Pharo code, by removing all the extra fat. No new bug fixes (unless created by the removal of the code), no new features. I know we have bootstrap , but thats a completely different thing. On Tue, Mar 7, 2017 at 3:15 PM phil(a)highoctane.be <phil(a)highoctane.be> wrote: > https://pharo.fogbugz.com/f/cases/19818/Support-for-Airplane-mode-in-Pharo > for keeping track of this > > On Tue, Mar 7, 2017 at 1:02 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Tue, Mar 7, 2017 at 6:35 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > > This is not only when teaching. > > > > I was at a conference today and showcased some Grafoscopio. > > > > Spotty wifi and crowded bandwith makes it bad looking. > > > > We need an "Airplane mode" switch. > > That is a cool way to describe it. A well know paradigm. > Its a setting that probably would change daya to day more than any other, > so perhaps it would even be reasonable to have this as a permanent > mode button on the background, > or the task bar much like MS Windows taskbar status icons. > > cheers -ben > > > > > Maybe can we have that available in the session from the settings. > > > > Phil > > > > On Mon, Mar 6, 2017 at 10:55 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> > >> The problem is that there are people who give lectures in universities > >> with bad internet (internet is bad in most of the universities I tried) > and > >> they done want freezes. On the other hand we have people who sit in > their > >> offices with fast machines, fast internet and they want features. Until > now > >> we were looking at how to satisfy one of the groups and which one > exactly. > >> Why not to try finding a solution for both. For example we can have the > >> plugging enabled by default and have Spotter measuring the time needed > to do > >> a query. Whenever the time surpasses frustration limit (10 sec? I duno) > >> Spotter will ask if the user wants to turn off the plugin, of turns it > of > >> automatically and tells where to re-enable it. The other way would be to > >> have known plugins to appear at the bottom of Spotter, and a user can > >> install/enable them with one click. So when you search but there is > nothing > >> you know that there are more plugins that may solve your problem. > >> > >> Yes it is more complicated to implement in in a smart way rather them > just > >> set the default boolean value of a setting, but we spend too much time > >> anyway convincing the other side that we are rightâ¦ > >> > >> Uko > >> > >> > On 6 Mar 2017, at 21:30, stepharong <stepharong(a)free.fr> wrote: > >> > > >> > One day I would like to invite you to give a lecture in a not that bad > >> > french university > >> > with a not that good network. Each time Pharo freezes you pay me 5 > Euros > >> > only and we can > >> > go and pay some really expensive restaurant with your money. > >> > Simple on my machine it times out every five minutes. > >> > > >> > <sorry I could not resist> > >> > > >> >> > >> >>> On 6 Mar 2017, at 19:51, stepharong <stepharong(a)free.fr> wrote: > >> >>> > >> >>> We should make it available from the catalog :) > >> >> > >> >> Yes, it most certainly should be. > >> >> > >> >> If only we could then tell user to type > >> >> > >> >> Shift-Enter Sublimish Enter > >> >> > >> >> to install it using Spotter right from the catalog ;-) > >> >> > >> >> Sorry, I couldn't resist ... <ducking> > >> >> > >> >>> 2017-03-06 9:29 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >>> > >> >>>> On 6 Mar 2017, at 09:22, Pavel Krivanek <pavel.krivanek(a)gmail.com> > >> >>>> wrote: > >> >>>> > >> >>>> > >> >>>> > >> >>>> 2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >>>> > >> >>>>> On 6 Mar 2017, at 07:57, phil(a)highoctane.be wrote: > >> >>>>> > >> >>>>> > >> >>>>> > https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator-simple/7294/artifac… > >> >>>>> is not integrated for some Monkey reason anyway - still should > b/c if you > >> >>>>> put sublimish, you need a decent matching Spotter. > >> >>>>> > >> >>>>> Also, I see > >> >>>>> > https://pharo.fogbugz.com/f/cases/19796/Remove-duplicate-code-from-Sublimis… > >> >>>>> on 5/3. If this moves forward, why not the other one? > >> >>>>> > >> >>>>> BTW Sublimish was an extra thing. Who got that in image? > >> >>>> > >> >>>> I donât know. > >> >>>> It shouldnât :) > >> >>>> > >> >>>> What we should do is to create a page for themes and links to it > (and > >> >>>> they should be in catalog) :) > >> >>>> > >> >>>> Well, it was me who proposed the slice and yes, I was aware of the > >> >>>> fact that I should not do it because of code freeze (I was not > aware of the > >> >>>> two themes policy). > >> >>> > >> >>> it is not a policy, it is just the idea I have :) > >> >>> > >> >>>> > >> >>>> We can remove it again, I will prepare a slice. > >> >>> > >> >>> problem with it is that is makes ripples. > >> >>> If community want it (is nice), we can include it, but I would wait > >> >>> for P7, yes. > >> >>> > >> >>> https://pharo.fogbugz.com/f/cases/19801/Remove-SublimishTheme > >> >>> At least it was an advertisement for this theme that moved it > forward > >> >>> and the integration of it helped to improve the dark theme too. And > showed > >> >>> again how much we need the concept of palettes used strictly in the > system. > >> >>> > >> >>> -- Pavel > >> >>> > >> >>> > >> >>> > >> >>> Esteban > >> >>> > >> >>>> > >> >>>> -- Pavel > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> Esteban > >> >>>> > >> >>>>> > >> >>>>> Phil > >> >>>>> > >> >>>>> On Mon, Mar 6, 2017 at 7:43 AM, Esteban Lorenzano > >> >>>>> <estebanlm(a)gmail.com> wrote: > >> >>>>> > >> >>>>>> On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm(a)gmail.com> > >> >>>>>> wrote: > >> >>>>>> > >> >>>>>> Hi, > >> >>>>>> > >> >>>>>> First, let me be clear: I *like* sublimish theme (not for my use, > >> >>>>>> but I like it), and I like (a lot) the windows list on spotter, > and I like > >> >>>>>> in general all this new additions. > >> >>>>> > >> >>>>> By the way, even if I like it, I would not have integrated > >> >>>>> SublimishTheme. For same reason I didnât integrated > DarkMetalTheme: My idea > >> >>>>> is to have just two themes *in image*: one white, one dark, and > allow people > >> >>>>> to install other themes from catalog. > >> >>>>> > >> >>>>> Why? Because each class inside image becomes our responsibility > and > >> >>>>> then a maintainability issue. With themes in particular already > happened > >> >>>>> that existing themes became abandonware inside the image and we > needed to > >> >>>>> clean up, not without problems. > >> >>>>> > >> >>>>> cheers, > >> >>>>> Esteban > >> >>>>> > >> >>>>> ps: which means also yes: that issue got integrated because I > failed > >> >>>>> to control the flow of issues... > >> >>>>> > >> >>>>>> > >> >>>>>> And I know, most of those additions are usability enhancements > so a > >> >>>>>> good thing. > >> >>>>>> > >> >>>>>> But can you guys stop pushing new features into a (in theory) > >> >>>>>> frozen version? > >> >>>>>> > >> >>>>>> Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If > I > >> >>>>>> can suggest an orientation, it would be good, for those that use > linux and > >> >>>>>> mac (windows is not ready), to test and help fix 64bits version. > >> >>>>>> > >> >>>>>> There are still plenty of bugs to fix there, like for example why > >> >>>>>> Spotter does not shows search line. > >> >>>>>> > >> >>>>>> Last week I added support to Athens and SDL2 in 64bits but that > >> >>>>>> meant: > >> >>>>>> > >> >>>>>> - some important changes in UFFI > >> >>>>>> - discover something that seems is failing on callbacks for Cairo > >> >>>>>> (no idea if it is a callbacks problem or an image problem that > causes a > >> >>>>>> callback problem). > >> >>>>>> > >> >>>>>> I would say all this and the fact we are working on 64bits in > >> >>>>>> general deserves a lot of testing. > >> >>>>>> > >> >>>>>> I will add links in Pharo page to download 64bits (Iâm at the > train > >> >>>>>> now), but in the mean time you can download all from here: > >> >>>>>> > >> >>>>>> http://files.pharo.org/get-files/60/pharo-64.zip > >> >>>>>> http://files.pharo.org/get-files/60/pharo64-linux-latest.zip > >> >>>>>> (linux) > >> >>>>>> http://files.pharo.org/get-files/60/pharo64-mac-latest.zip (mac) > >> >>>>>> http://files.pharo.org/get-files/60/sources.zip (in case you > need > >> >>>>>> them) > >> >>>>>> > >> >>>>>> cheers, > >> >>>>>> Esteban > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> Using Opera's mail client: http://www.opera.com/mail/ > >> >> > >> >> > >> > > >> > > >> > -- > >> > Using Opera's mail client: http://www.opera.com/mail/ > >> > > >> > >> > > > > >

March 7, 2017

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

by Sven Van Caekenberghe

Thank you, Andrei, for your continued efforts ! > On 7 Mar 2017, at 14:47, denker <marcus.denker(a)inria.fr> wrote: > > >> Log Message: >> ----------- >> 60436 >> Moose >> >> http://files.pharo.org/image/60/60436.zip >> > > > This brings changes to the inspector, debugger and fast table renderer for glamour. > Detailed changes: > > - added support for refresh in the Inspector/Playground. The refresh uses the stepping mechanism from Morphic. There exists a setting to start/stop the refresh. Each presentation can decide if it wants refresh or not. > > - the Glamour renderer for fast table uses now a LRUCache for storing the string representation returned by the #format: block. This is disabled by default and configureable per presentation. By default it is enabled for the Raw presentation and the collection presentations. > > - the debugger now offers access to variables defined in the playground when debugging code from the playground > > - the inspector uses GTInspectorVariableNode to model variables in the Raw view. > > - fixed inspector issues with collections > > Also fixes issues: > - case 18899 Raw presentation from the debugger inspector raises error when the rawSelection comes from another presentation > - case 17949 Missing evaluator presentation for the current context in debugger > - case 19753 Disappearing content in the context inspector from GTDebugger when tags are used > - case 19720 Add method scoped [Evaluator] tab to debugger > - case 14569 GTInspector should do live updates of objects and their slots > > >

March 7, 2017

Re: [Pharo-dev] [pharo-project/pharo-core] 1b4c50: 60436

by denker

> Log Message: > ----------- > 60436 > Moose > > http://files.pharo.org/image/60/60436.zip > This brings changes to the inspector, debugger and fast table renderer for glamour. Detailed changes: - added support for refresh in the Inspector/Playground. The refresh uses the stepping mechanism from Morphic. There exists a setting to start/stop the refresh. Each presentation can decide if it wants refresh or not. - the Glamour renderer for fast table uses now a LRUCache for storing the string representation returned by the #format: block. This is disabled by default and configureable per presentation. By default it is enabled for the Raw presentation and the collection presentations. - the debugger now offers access to variables defined in the playground when debugging code from the playground - the inspector uses GTInspectorVariableNode to model variables in the Raw view. - fixed inspector issues with collections Also fixes issues: - case 18899 Raw presentation from the debugger inspector raises error when the rawSelection comes from another presentation - case 17949 Missing evaluator presentation for the current context in debugger - case 19753 Disappearing content in the context inspector from GTDebugger when tags are used - case 19720 Add method scoped [Evaluator] tab to debugger - case 14569 GTInspector should do live updates of objects and their slots

March 7, 2017

[pharo-project/pharo-core]

by GitHub

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

March 7, 2017

[pharo-project/pharo-core] 1b4c50: 60436

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 1b4c50f198562b693fc81806b4e434a35d506cf9 https://github.com/pharo-project/pharo-core/commit/1b4c50f198562b693fc81806… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-07 (Tue, 07 Mar 2017) Changed paths: M ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/symbolic versions/stable_.st A ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/versions/version310_.st M ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/symbolic versions/stable_.st A ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/versions/version17_.st M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version328_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version324_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version226_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version336_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version436_.st R GT-BytecodeDebugger.package/GTBytecodeDebuggerVariablesBrowser.class/instance/as yet unclassified/variableTypeOf_in_.st A GT-BytecodeDebugger.package/GTBytecodeDebuggerVariablesBrowser.class/instance/private building/buildVariablesFromContext_.st R GT-BytecodeDebugger.package/GTBytecodeDebuggerVariablesBrowser.class/instance/private building/variablesFromContext_.st M GT-BytecodeDebugger.package/extension/Context/instance/gtBytecodeDebuggerRetrieveContextValues.st M GT-Debugger.package/GTDebuggerVariablesBrowser.class/definition.st A GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/accessing/selectedVariableForContext_.st A GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/actions/restoreSettings.st A GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/actions/updateVariablesForContext.st M GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/building/compose.st R GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/building/selectedVariableForContext_.st R GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/building/variableTypeOf_in_.st A GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/private building/buildVariablesFromContext_.st A GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/private building/contextEvaluatorIn_.st R GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/private building/tagsForVariable_from_.st M GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/private building/variablesFromContext_.st M GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/private building/variablesIn_.st R GT-Debugger.package/GTDebuggerVariablesBrowser.class/instance/testing/compareVariableTypeOf_withVariable_in_.st M GT-Debugger.package/GTGenericStackDebugger.class/definition.st A GT-Debugger.package/GTGenericStackDebugger.class/instance/accessing/cache.st M GT-Debugger.package/GTGenericStackDebugger.class/instance/accessing/selectedVariableName.st M GT-Debugger.package/GTGenericStackDebugger.class/instance/accessing/selectedVariableName_.st A GT-Debugger.package/GTGenericStackDebugger.class/instance/building presentations/installBindingsForDoItIn_from_.st M GT-Debugger.package/GTGenericStackDebugger.class/instance/building presentations/methodCodeIn_forContext_.st M GT-Debugger.package/GTGenericStackDebugger.class/instance/building presentations/methodCodeWidgetIn_forContext_.st M GT-Debugger.package/GTGenericStackDebugger.class/instance/building presentations/stackWidgetIn_.st M GT-Debugger.package/extension/Context/instance/gtConstructDebuggerInspectorIn_for_.st A GT-Debugger.package/extension/Context/instance/gtDebuggerDoItBindings.st M GT-Debugger.package/extension/Context/instance/gtDebuggerRetrieveVariableValuePairs.st R GT-Debugger.package/extension/DebugContext/instance/gtDebuggerRetrieveVariableValuePairs.st A GT-Inspector.package/GTInspector.class/class/settings/disableStepRefresh.st A GT-Inspector.package/GTInspector.class/class/settings/enableStepRefresh.st A GT-Inspector.package/GTInspector.class/class/settings/indexableDisplayLimit.st A GT-Inspector.package/GTInspector.class/class/settings/indexableDisplayLimit_.st A GT-Inspector.package/GTInspector.class/class/settings/isStepRefreshEnabled.st A GT-Inspector.package/GTInspector.class/class/settings/setEnabledStepRefreshStatus_.st M GT-Inspector.package/GTInspector.class/class/settings/settingsOn_.st A GT-Inspector.package/GTInspector.class/class/settings/stepRefreshRate.st A GT-Inspector.package/GTInspector.class/class/settings/stepRefreshRate_.st M GT-Inspector.package/GTInspector.class/definition.st M GT-Inspector.package/GTInspector.class/instance/building/compose.st A GT-Inspector.package/GTInspector.class/instance/stepping/step.st A GT-Inspector.package/GTInspector.class/instance/updating/refreshPanes.st A GT-Inspector.package/GTInspector.class/instance/updating/requestRefresh.st A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/README.md A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/class/as yet unclassified/hostObject_tempIndex_.st A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/definition.st A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/instance/accessing/label.st A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/instance/accessing/rawValue.st A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/instance/accessing/tempIndex.st A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/instance/accessing/tempIndex_.st A GT-Inspector.package/GTInspectorContextIndexedTempNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/README.md A GT-Inspector.package/GTInspectorContextNamedTempNode.class/class/instance creation/hostObject_tempName_tempIndex_.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/definition.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/errorMessage.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/key.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/label.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/rawValue.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/tempIndex.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/tempIndex_.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/tempName.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/tempName_.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorContextNamedTempNode.class/instance/accessing/variableTag_.st M GT-Inspector.package/GTInspectorDynamicNode.class/class/instance creation/hostObject_label_value_.st M GT-Inspector.package/GTInspectorDynamicNode.class/definition.st A GT-Inspector.package/GTInspectorDynamicNode.class/instance/accessing/rawValue.st A GT-Inspector.package/GTInspectorDynamicNode.class/instance/accessing/rawValue_.st R GT-Inspector.package/GTInspectorDynamicNode.class/instance/accessing/value.st R GT-Inspector.package/GTInspectorDynamicNode.class/instance/accessing/value_.st A GT-Inspector.package/GTInspectorDynamicNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorDynamicNode.class/instance/accessing/variableTag_.st M GT-Inspector.package/GTInspectorIndexedNode.class/README.md M GT-Inspector.package/GTInspectorIndexedNode.class/definition.st A GT-Inspector.package/GTInspectorIndexedNode.class/instance/accessing/errorMessage.st M GT-Inspector.package/GTInspectorIndexedNode.class/instance/accessing/index_.st A GT-Inspector.package/GTInspectorIndexedNode.class/instance/accessing/rawValue.st R GT-Inspector.package/GTInspectorIndexedNode.class/instance/accessing/value.st A GT-Inspector.package/GTInspectorIndexedNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorIndexedNode.class/instance/actions/save_.st M GT-Inspector.package/GTInspectorProtoObjectNode.class/README.md M GT-Inspector.package/GTInspectorProtoObjectNode.class/definition.st M GT-Inspector.package/GTInspectorProtoObjectNode.class/instance/accessing/index_slotName_.st A GT-Inspector.package/GTInspectorProtoObjectNode.class/instance/accessing/rawValue.st R GT-Inspector.package/GTInspectorProtoObjectNode.class/instance/accessing/value.st A GT-Inspector.package/GTInspectorProtoObjectNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorSelfNode.class/instance/accessing/rawValue.st R GT-Inspector.package/GTInspectorSelfNode.class/instance/accessing/value.st M GT-Inspector.package/GTInspectorSlotNode.class/README.md M GT-Inspector.package/GTInspectorSlotNode.class/definition.st R GT-Inspector.package/GTInspectorSlotNode.class/instance/accessing/editingActionForNode.st A GT-Inspector.package/GTInspectorSlotNode.class/instance/accessing/errorMessage.st M GT-Inspector.package/GTInspectorSlotNode.class/instance/accessing/inspectorActionsForNode.st A GT-Inspector.package/GTInspectorSlotNode.class/instance/accessing/rawValue.st M GT-Inspector.package/GTInspectorSlotNode.class/instance/accessing/slot_.st R GT-Inspector.package/GTInspectorSlotNode.class/instance/accessing/value.st A GT-Inspector.package/GTInspectorSlotNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorSlotNode.class/instance/actions/save_.st M GT-Inspector.package/GTInspectorVariableNode.class/README.md A GT-Inspector.package/GTInspectorVariableNode.class/instance/accessing/errorMessage.st A GT-Inspector.package/GTInspectorVariableNode.class/instance/accessing/rawValue.st M GT-Inspector.package/GTInspectorVariableNode.class/instance/accessing/value.st A GT-Inspector.package/GTInspectorVariableNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorVariableNode.class/instance/actions/save_.st M GT-Inspector.package/GTInspectorVariableNode.class/instance/composition/childrenNodesFor_.st A GT-Inspector.package/GTInspectorWrapperNode.class/README.md A GT-Inspector.package/GTInspectorWrapperNode.class/class/instance creation/hostObject_label_.st A GT-Inspector.package/GTInspectorWrapperNode.class/definition.st A GT-Inspector.package/GTInspectorWrapperNode.class/instance/accessing/errorMessage.st A GT-Inspector.package/GTInspectorWrapperNode.class/instance/accessing/inspectorActionsForNode.st A GT-Inspector.package/GTInspectorWrapperNode.class/instance/accessing/key.st A GT-Inspector.package/GTInspectorWrapperNode.class/instance/accessing/label_.st A GT-Inspector.package/GTInspectorWrapperNode.class/instance/accessing/rawValue.st A GT-Inspector.package/GTInspectorWrapperNode.class/instance/accessing/variableTag.st A GT-Inspector.package/GTInspectorWrapperNode.class/instance/composition/childrenNodesFor_.st M GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/building/compose.st A GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/private building/childrenVariableNodesForNode_.st M GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/private building/iconFor_.st R GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/private building/updateInstanceVariable_from_basedOn_.st A GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/private building/updateVariableNode_basedOn_.st M GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/private building/variablesIn_.st A GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/stepping/requestRefresh.st A GT-Inspector.package/extension/Morph/instance/gtInspectorIcon.st A GT-Inspector.package/extension/Object/instance/gtInspectorIcon.st M GT-Inspector.package/extension/Object/instance/gtInspectorVariableNodesIn_.st A GT-Inspector.package/extension/ProtoObject/instance/gtInspectorIcon.st M GT-InspectorExtensions-Core.package/extension/Collection/instance/gtInspectorItemsIn_.st A GT-InspectorExtensions-Core.package/extension/Context/instance/gtInspectorTempNodes.st M GT-InspectorExtensions-Core.package/extension/Context/instance/gtInspectorVariableNodesIn_.st M GT-InspectorExtensions-Core.package/extension/Dictionary/instance/gtInspectorItemsIn_.st M GT-InspectorExtensions-Core.package/extension/Dictionary/instance/gtInspectorKeysIn_.st M GT-InspectorExtensions-Core.package/extension/OrderedDictionary/instance/gtInspectorItemsIn_.st M GT-InspectorExtensions-Core.package/extension/SequenceableCollection/instance/gtInspectorItemsIn_.st M GT-InspectorExtensions-Core.package/extension/SharedQueue/instance/gtInspectorItemsIn_.st M GT-InspectorExtensions-Core.package/extension/SmallDictionary/instance/gtInspectorItemsIn_.st M GT-Playground.package/GTPlayBook.class/class/private/reset.st M GT-Playground.package/GTPlayground.class/instance/building/compose.st A GT-Playground.package/GTPlayground.class/instance/stepping/step.st A GT-Playground.package/GTPlayground.class/instance/updating/requestRefresh.st A GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/context/testContextNodes.st R GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/context/testContextPairs.st R GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/object/testArrayPairs41.st R GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/object/testArrayPairs42.st R GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/object/testArrayPairs43.st A GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/object/testArrayPairsEqualLimit.st M GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/object/testArrayPairsLong.st A GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/object/testArrayPairsOverLimit.st A GT-Tests-Inspector.package/GTInspectorVariableValuePairsTest.class/instance/object/testArrayPairsUnderLimit.st M Glamour-Announcements.package/GLMContextChanged.class/instance/printing/printOn_.st A Glamour-Announcements.package/GLMPresentationRefreshRequest.class/README.md A Glamour-Announcements.package/GLMPresentationRefreshRequest.class/definition.st A Glamour-Announcements.package/GLMPresentationRefreshRequest.class/instance/accessing/presentation.st A Glamour-Announcements.package/GLMPresentationRefreshRequest.class/instance/accessing/presentation_.st M Glamour-Core.package/GLMAction.class/instance/accessing/help_.st M Glamour-Core.package/GLMPresentation.class/definition.st A Glamour-Core.package/GLMPresentation.class/instance/accessing/wantsAutomaticRefresh.st A Glamour-Core.package/GLMPresentation.class/instance/accessing/wantsAutomaticRefresh_.st A Glamour-Core.package/GLMPresentation.class/instance/scripting actions/selectionAct_entitled_condition_.st A Glamour-Core.package/GLMPresentation.class/instance/stepping/step.st M Glamour-Core.package/GLMPresentation.class/instance/stepping/wantsSteps.st A Glamour-Core.package/GLMPresentation.class/instance/updating/requestRefresh.st M Glamour-Core.package/GLMTransmission.class/instance/transmitting/value.st M Glamour-FastTable.package/GLMFastListDataSource.class/definition.st M Glamour-FastTable.package/GLMFastListDataSource.class/instance/accessing/resetElements.st A Glamour-FastTable.package/GLMFastListDataSource.class/instance/cache/dataCache.st A Glamour-FastTable.package/GLMFastListDataSource.class/instance/cache/resetDataCache.st M Glamour-FastTable.package/GLMFastListDataSource.class/instance/factory/rowMorphForElement_.st M Glamour-FastTable.package/GLMFastListDataSource.class/instance/private/resetChildrenContent.st M Glamour-FastTable.package/GLMFastListOutlineDataSource.class/definition.st A Glamour-FastTable.package/GLMFastListOutlineDataSource.class/instance/cache/dataCache.st A Glamour-FastTable.package/GLMFastListOutlineDataSource.class/instance/cache/resetDataCache.st M Glamour-FastTable.package/GLMFastListOutlineDataSource.class/instance/factory/rowMorphForElement_.st M Glamour-FastTable.package/GLMFastListOutlineDataSource.class/instance/private/resetChildrenContent.st M Glamour-FastTable.package/GLMFastTableDataSource.class/instance/accessing/rowMorphElementsForFirstColumn_item_in_.st M Glamour-FastTable.package/GLMFastTreeDataSource.class/definition.st M Glamour-FastTable.package/GLMFastTreeDataSource.class/instance/accessing/resetElements.st A Glamour-FastTable.package/GLMFastTreeDataSource.class/instance/cache/dataCache.st A Glamour-FastTable.package/GLMFastTreeDataSource.class/instance/cache/resetDataCache.st M Glamour-FastTable.package/GLMFastTreeDataSource.class/instance/private/resetChildrenContent.st M Glamour-FastTable.package/GLMFastTreeDataSource.class/instance/private/rowMorphForItem_.st A Glamour-FastTable.package/GLMFastTreeTableDataSource.class/instance/accessing/dataFromPresentationItem_.st M Glamour-FastTable.package/GLMFastTreeTableDataSource.class/instance/accessing/rowMorphElementsForFirstColumn_item_in_.st R Glamour-FastTable.package/GLMFastTreeTableDataSource.class/instance/as yet unclassified/dataFromPresentationItem_.st A Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/callbacks/actOnContextChanged_.st A Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/callbacks/actOnPresentationRefreshRequest_.st A Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/callbacks/actOnUpdatedPresentation_.st M Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/private/initializeAnnoucementForPresentation_.st R Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/rendering/actOnContextChanged_.st R Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/rendering/actOnUpdatedPresentation_.st A Glamour-FastTable.package/TGLMFastTable.class/class/accessing - cache/defaultCache.st A Glamour-FastTable.package/TGLMFastTable.class/instance/accessing - cache/cacheAt_for_ifAbsentPut_.st A Glamour-FastTable.package/TGLMFastTable.class/instance/accessing - cache/formatedDisplayValueOf_.st A Glamour-FastTable.package/TGLMFastTable.class/instance/accessing - cache/iconFor_.st A Glamour-FastTable.package/TGLMFastTable.class/instance/accessing - cache/shouldUseCache.st A Glamour-FastTable.package/TGLMFastTable.class/instance/cache/dataCache.st A Glamour-FastTable.package/TGLMFastTable.class/instance/cache/dataCacheFor_.st A Glamour-FastTable.package/TGLMFastTable.class/instance/cache/resetDataCache.st A Glamour-FastTable.package/TGLMFastTableColumnsRenderer.class/instance/accessing - cache/valueFor_withIndex_in_.st R Glamour-FastTable.package/TGLMFastTableColumnsRenderer.class/instance/accessing/valueFor_in_.st M Glamour-FastTable.package/TGLMFastTableColumnsRenderer.class/instance/rendering/editRowMorphForColumn_element_withIndex_.st M Glamour-FastTable.package/TGLMFastTableColumnsRenderer.class/instance/rendering/viewRowMorphForColumn_element_withIndex_.st A Glamour-FastTable.package/TGLMFastTableFunctionsPresentation.class/instance/public api/shouldUseCache.st A Glamour-FastTable.package/TGLMFastTableFunctionsPresentation.class/instance/public api/shouldUseCache_.st A Glamour-FastTable.package/TGLMFastTableFunctionsPresentation.class/instance/public api/useCache.st M Glamour-Morphic-Brick.package/GLMTabLabelBrick.class/instance/brick-interactable-actions/select.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/rendering/modelFor_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoMethodRenderer.class/instance/rendering/modelFor_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoMethodRenderer.class/instance/rendering/morph.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoScriptRenderer.class/instance/rendering/modelFor_.st M Glamour-Morphic-Widgets.package/GLMRubricSmalltalkTextModel.class/instance/bindings/appendVariableBinding_.st M Glamour-Morphic-Widgets.package/GLMSystemWindow.class/definition.st M Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/initialization/initialize.st A Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/stepping/stepAt_.st A Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/stepping/stepTime.st A Glamour-Morphic-Widgets.package/GLMSystemWindow.class/instance/stepping/wantsSteps.st M Glamour-Rubric-Presentations.package/GLMPharoScriptPresentation.class/definition.st R Glamour-Rubric-Presentations.package/GLMPharoScriptPresentation.class/instance/accessing/variableBindings.st R Glamour-Rubric-Presentations.package/GLMPharoScriptPresentation.class/instance/accessing/variableBindings_.st M Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/definition.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/accessing/variableBindings.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/accessing/variableBindings_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60435.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60436.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60435.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60436.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60436 Moose http://files.pharo.org/image/60/60436.zip

March 7, 2017

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by phil＠highoctane.be

https://pharo.fogbugz.com/f/cases/19818/Support-for-Airplane-mode-in-Pharo for keeping track of this On Tue, Mar 7, 2017 at 1:02 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Tue, Mar 7, 2017 at 6:35 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > > This is not only when teaching. > > > > I was at a conference today and showcased some Grafoscopio. > > > > Spotty wifi and crowded bandwith makes it bad looking. > > > > We need an "Airplane mode" switch. > > That is a cool way to describe it. A well know paradigm. > Its a setting that probably would change daya to day more than any other, > so perhaps it would even be reasonable to have this as a permanent > mode button on the background, > or the task bar much like MS Windows taskbar status icons. > > cheers -ben > > > > > Maybe can we have that available in the session from the settings. > > > > Phil > > > > On Mon, Mar 6, 2017 at 10:55 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> > >> The problem is that there are people who give lectures in universities > >> with bad internet (internet is bad in most of the universities I tried) > and > >> they done want freezes. On the other hand we have people who sit in > their > >> offices with fast machines, fast internet and they want features. Until > now > >> we were looking at how to satisfy one of the groups and which one > exactly. > >> Why not to try finding a solution for both. For example we can have the > >> plugging enabled by default and have Spotter measuring the time needed > to do > >> a query. Whenever the time surpasses frustration limit (10 sec? I duno) > >> Spotter will ask if the user wants to turn off the plugin, of turns it > of > >> automatically and tells where to re-enable it. The other way would be to > >> have known plugins to appear at the bottom of Spotter, and a user can > >> install/enable them with one click. So when you search but there is > nothing > >> you know that there are more plugins that may solve your problem. > >> > >> Yes it is more complicated to implement in in a smart way rather them > just > >> set the default boolean value of a setting, but we spend too much time > >> anyway convincing the other side that we are rightâ¦ > >> > >> Uko > >> > >> > On 6 Mar 2017, at 21:30, stepharong <stepharong(a)free.fr> wrote: > >> > > >> > One day I would like to invite you to give a lecture in a not that bad > >> > french university > >> > with a not that good network. Each time Pharo freezes you pay me 5 > Euros > >> > only and we can > >> > go and pay some really expensive restaurant with your money. > >> > Simple on my machine it times out every five minutes. > >> > > >> > <sorry I could not resist> > >> > > >> >> > >> >>> On 6 Mar 2017, at 19:51, stepharong <stepharong(a)free.fr> wrote: > >> >>> > >> >>> We should make it available from the catalog :) > >> >> > >> >> Yes, it most certainly should be. > >> >> > >> >> If only we could then tell user to type > >> >> > >> >> Shift-Enter Sublimish Enter > >> >> > >> >> to install it using Spotter right from the catalog ;-) > >> >> > >> >> Sorry, I couldn't resist ... <ducking> > >> >> > >> >>> 2017-03-06 9:29 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >>> > >> >>>> On 6 Mar 2017, at 09:22, Pavel Krivanek <pavel.krivanek(a)gmail.com> > >> >>>> wrote: > >> >>>> > >> >>>> > >> >>>> > >> >>>> 2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >>>> > >> >>>>> On 6 Mar 2017, at 07:57, phil(a)highoctane.be wrote: > >> >>>>> > >> >>>>> > >> >>>>> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator- > simple/7294/artifact/report.html > >> >>>>> is not integrated for some Monkey reason anyway - still should > b/c if you > >> >>>>> put sublimish, you need a decent matching Spotter. > >> >>>>> > >> >>>>> Also, I see > >> >>>>> https://pharo.fogbugz.com/f/cases/19796/Remove-duplicate- > code-from-SublimishTheme > >> >>>>> on 5/3. If this moves forward, why not the other one? > >> >>>>> > >> >>>>> BTW Sublimish was an extra thing. Who got that in image? > >> >>>> > >> >>>> I donât know. > >> >>>> It shouldnât :) > >> >>>> > >> >>>> What we should do is to create a page for themes and links to it > (and > >> >>>> they should be in catalog) :) > >> >>>> > >> >>>> Well, it was me who proposed the slice and yes, I was aware of the > >> >>>> fact that I should not do it because of code freeze (I was not > aware of the > >> >>>> two themes policy). > >> >>> > >> >>> it is not a policy, it is just the idea I have :) > >> >>> > >> >>>> > >> >>>> We can remove it again, I will prepare a slice. > >> >>> > >> >>> problem with it is that is makes ripples. > >> >>> If community want it (is nice), we can include it, but I would wait > >> >>> for P7, yes. > >> >>> > >> >>> https://pharo.fogbugz.com/f/cases/19801/Remove-SublimishTheme > >> >>> At least it was an advertisement for this theme that moved it > forward > >> >>> and the integration of it helped to improve the dark theme too. And > showed > >> >>> again how much we need the concept of palettes used strictly in the > system. > >> >>> > >> >>> -- Pavel > >> >>> > >> >>> > >> >>> > >> >>> Esteban > >> >>> > >> >>>> > >> >>>> -- Pavel > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> Esteban > >> >>>> > >> >>>>> > >> >>>>> Phil > >> >>>>> > >> >>>>> On Mon, Mar 6, 2017 at 7:43 AM, Esteban Lorenzano > >> >>>>> <estebanlm(a)gmail.com> wrote: > >> >>>>> > >> >>>>>> On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm(a)gmail.com> > >> >>>>>> wrote: > >> >>>>>> > >> >>>>>> Hi, > >> >>>>>> > >> >>>>>> First, let me be clear: I *like* sublimish theme (not for my use, > >> >>>>>> but I like it), and I like (a lot) the windows list on spotter, > and I like > >> >>>>>> in general all this new additions. > >> >>>>> > >> >>>>> By the way, even if I like it, I would not have integrated > >> >>>>> SublimishTheme. For same reason I didnât integrated > DarkMetalTheme: My idea > >> >>>>> is to have just two themes *in image*: one white, one dark, and > allow people > >> >>>>> to install other themes from catalog. > >> >>>>> > >> >>>>> Why? Because each class inside image becomes our responsibility > and > >> >>>>> then a maintainability issue. With themes in particular already > happened > >> >>>>> that existing themes became abandonware inside the image and we > needed to > >> >>>>> clean up, not without problems. > >> >>>>> > >> >>>>> cheers, > >> >>>>> Esteban > >> >>>>> > >> >>>>> ps: which means also yes: that issue got integrated because I > failed > >> >>>>> to control the flow of issues... > >> >>>>> > >> >>>>>> > >> >>>>>> And I know, most of those additions are usability enhancements > so a > >> >>>>>> good thing. > >> >>>>>> > >> >>>>>> But can you guys stop pushing new features into a (in theory) > >> >>>>>> frozen version? > >> >>>>>> > >> >>>>>> Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If > I > >> >>>>>> can suggest an orientation, it would be good, for those that use > linux and > >> >>>>>> mac (windows is not ready), to test and help fix 64bits version. > >> >>>>>> > >> >>>>>> There are still plenty of bugs to fix there, like for example why > >> >>>>>> Spotter does not shows search line. > >> >>>>>> > >> >>>>>> Last week I added support to Athens and SDL2 in 64bits but that > >> >>>>>> meant: > >> >>>>>> > >> >>>>>> - some important changes in UFFI > >> >>>>>> - discover something that seems is failing on callbacks for Cairo > >> >>>>>> (no idea if it is a callbacks problem or an image problem that > causes a > >> >>>>>> callback problem). > >> >>>>>> > >> >>>>>> I would say all this and the fact we are working on 64bits in > >> >>>>>> general deserves a lot of testing. > >> >>>>>> > >> >>>>>> I will add links in Pharo page to download 64bits (Iâm at the > train > >> >>>>>> now), but in the mean time you can download all from here: > >> >>>>>> > >> >>>>>> http://files.pharo.org/get-files/60/pharo-64.zip > >> >>>>>> http://files.pharo.org/get-files/60/pharo64-linux-latest.zip > >> >>>>>> (linux) > >> >>>>>> http://files.pharo.org/get-files/60/pharo64-mac-latest.zip (mac) > >> >>>>>> http://files.pharo.org/get-files/60/sources.zip (in case you > need > >> >>>>>> them) > >> >>>>>> > >> >>>>>> cheers, > >> >>>>>> Esteban > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> Using Opera's mail client: http://www.opera.com/mail/ > >> >> > >> >> > >> > > >> > > >> > -- > >> > Using Opera's mail client: http://www.opera.com/mail/ > >> > > >> > >> > > > >

March 7, 2017

[pharo-project/pharo-core] d21a9b: 60435

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d21a9b5e04605614e6058aa214dbb804245f5a31 https://github.com/pharo-project/pharo-core/commit/d21a9b5e04605614e6058aa2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-03-07 (Tue, 07 Mar 2017) Changed paths: M BaselineOfBasicTools.package/BaselineOfBasicTools.class/instance/actions/postload_package_.st M Metacello-TestsCommonMC.package/MetacelloTestsPackageSet.class/README.md M Metacello-TestsPlatform.package/MetacelloRepositorySqueakCommonTestCase.class/README.md M SUnit-Rules.package/AssertEqualSignIntoAssertEquals.class/definition.st A SUnit-Rules.package/AssertEqualSignIntoAssertEquals.class/instance/hooks/afterCheck_mappings_.st M SUnit-Rules.package/AssertEqualSignIntoAssertEquals.class/instance/initialization/initialize.st M SUnit-Rules.package/ShouldTransformedIntoAssert.class/definition.st M SUnit-Rules.package/ShouldTransformedIntoAssert.class/instance/initialization/initialize.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60434.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60435.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60434.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60435.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60435 19816 Packages postfix must be removed https://pharo.fogbugz.com/f/cases/19816 19815 BaselineOfBasicTools still loads Polymorph-TaskbarIcons https://pharo.fogbugz.com/f/cases/19815 19807 Assert:equals: rule should target only tests https://pharo.fogbugz.com/f/cases/19807 http://files.pharo.org/image/60/60435.zip

March 7, 2017