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

Re: [Pharo-dev] some questions about current GToolkit issues

by Nicolai Hess

Thank you Doru 2015-07-04 7:31 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi Nicolai, > > Please > > On Fri, Jul 3, 2015 at 10:53 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> 15102 <https://pharo.fogbugz.com/default.asp?15102> >> lost worldmenu >> Is anyone working on this, it is quite annoying, happens to me a couple >> of time - per day. >> Everytime I restart the image to get the menu back. Is there any other >> way to >> recreate the worldmenu? >> > > No, because we do not know how to reproduce it (like the message says). If > anyone knows how, this would help. > > >> >> 15772 <https://pharo.fogbugz.com/default.asp?15772> >> spotter is undebuggable >> Andrei said on the ML he knows what the problem is. Are you working on >> this? >> This makes it difficult to work/analyse other spotter bugs. >> > > I just added a note in the issue. Please provide a step-by-step situation. > thanks, done > > > >> 14569 <https://pharo.fogbugz.com/default.asp?14569> >> GTInspector should do live updates of objects and their slots >> This was considered a really important issue. Who works on this, any >> progress? >> > > We have a solution in the image, but it is not scalable (the rendering was > just too slow), so it is disabled by default (custom presentations can use > it if they want). > I know, I can read the bug tracker comments, the question was if this is going to be solved for the current release - apparently not. > > We are working on this in two ways: > - a new version of the inspector based on bloc and without glamour. This > will take a while to finish, but the goal is to make it until Pharo 6. > - as soon as we can hook on object-specific events we will use that > mechanism to identify the need for an update > Ok, I see, you alread commented the bug report, thanks! > > > >> There are some issues tagged for pharo 40. Who will take care of it? >> Backport the >> fixes or change the milestone >> > > As far as I am concerned, we should keep the backporting to critical cases > only. Right now, I see none of them as being critical. > can you add a note to that issues, or move the milestone, please > > > >> There are some more issues (for example about the >> displayString/printString) waiting for >> some feedback and comments. >> > > Ok. We will try to go over them. > > > I wasn't happy with the way spotter & co were pushed into the 4.0 release. >> To many changes and new features even during code freeze. I do understand >> that it was important to have this in the release to get feedback. >> But now I wish more support, we already have too many loose ends, >> unfinished projects >> and to few people working on them. >> > > I do not see the relation between adding spotter and the support. > I meant "some help", feedback on the open issues,anything that shows who is working on what. At the moment it looks as if the work had stopped. Some changes (like settings/menu morph preview) were added during the code freeze. But they don't work in the release. I filed a bug report and asked multiple times - no feedback. Looks like no one cares. The same for a couple of other issues. > > > Please help, and keep up working on this or give some feedback or comment >> the >> open issues. >> > > This is an unfortunate period simply because it is holidays time and there > are other things that prevented us to work on it. > holidays are ok :) this is the reason I waited so long before asking for help, but now, after two months of no progress, I just wanted to know. > > Cheers, > Doru > > > >> nicolai >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

July 4, 2015

In our quest to remove PluggableTextMorph :)

by stepharo

Hi as you saw we mainly Frank helped by Alain started a fight against PluggableTextMorph and started to replace PluggableTextMorph with Rub equivalent. It will help us also to migrate to Bloc. We have rewriten Workspace, TestRunner is on its way. So we will replace soon the old Workspace with a new ones (with most features kept - we just did not keep the broken ones). Stef and Franck

July 4, 2015

Re: [Pharo-dev] some questions about current GToolkit issues

by Tudor Girba

Hi, When I said that the goal for the new inspector is Pharo 6, I meant Pharo 5 - at least as an alternative to the existing one. Cheers, Doru On Sat, Jul 4, 2015 at 7:31 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Nicolai, > > Please > > On Fri, Jul 3, 2015 at 10:53 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> 15102 <https://pharo.fogbugz.com/default.asp?15102> >> lost worldmenu >> Is anyone working on this, it is quite annoying, happens to me a couple >> of time - per day. >> Everytime I restart the image to get the menu back. Is there any other >> way to >> recreate the worldmenu? >> > > No, because we do not know how to reproduce it (like the message says). If > anyone knows how, this would help. > > >> >> 15772 <https://pharo.fogbugz.com/default.asp?15772> >> spotter is undebuggable >> Andrei said on the ML he knows what the problem is. Are you working on >> this? >> This makes it difficult to work/analyse other spotter bugs. >> > > I just added a note in the issue. Please provide a step-by-step situation. > > > >> 14569 <https://pharo.fogbugz.com/default.asp?14569> >> GTInspector should do live updates of objects and their slots >> This was considered a really important issue. Who works on this, any >> progress? >> > > We have a solution in the image, but it is not scalable (the rendering was > just too slow), so it is disabled by default (custom presentations can use > it if they want). > > We are working on this in two ways: > - a new version of the inspector based on bloc and without glamour. This > will take a while to finish, but the goal is to make it until Pharo 6. > - as soon as we can hook on object-specific events we will use that > mechanism to identify the need for an update > > > >> There are some issues tagged for pharo 40. Who will take care of it? >> Backport the >> fixes or change the milestone >> > > As far as I am concerned, we should keep the backporting to critical cases > only. Right now, I see none of them as being critical. > > > >> There are some more issues (for example about the >> displayString/printString) waiting for >> some feedback and comments. >> > > Ok. We will try to go over them. > > > I wasn't happy with the way spotter & co were pushed into the 4.0 release. >> To many changes and new features even during code freeze. I do understand >> that it was important to have this in the release to get feedback. >> But now I wish more support, we already have too many loose ends, >> unfinished projects >> and to few people working on them. >> > > I do not see the relation between adding spotter and the support. > > > Please help, and keep up working on this or give some feedback or comment >> the >> open issues. >> > > This is an unfortunate period simply because it is holidays time and there > are other things that prevented us to work on it. > > Cheers, > Doru > > > >> nicolai >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

July 4, 2015

Re: [Pharo-dev] some questions about current GToolkit issues

by Tudor Girba

Hi Nicolai, Please On Fri, Jul 3, 2015 at 10:53 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 15102 <https://pharo.fogbugz.com/default.asp?15102> > lost worldmenu > Is anyone working on this, it is quite annoying, happens to me a couple of > time - per day. > Everytime I restart the image to get the menu back. Is there any other way > to > recreate the worldmenu? > No, because we do not know how to reproduce it (like the message says). If anyone knows how, this would help. > > 15772 <https://pharo.fogbugz.com/default.asp?15772> > spotter is undebuggable > Andrei said on the ML he knows what the problem is. Are you working on > this? > This makes it difficult to work/analyse other spotter bugs. > I just added a note in the issue. Please provide a step-by-step situation. > 14569 <https://pharo.fogbugz.com/default.asp?14569> > GTInspector should do live updates of objects and their slots > This was considered a really important issue. Who works on this, any > progress? > We have a solution in the image, but it is not scalable (the rendering was just too slow), so it is disabled by default (custom presentations can use it if they want). We are working on this in two ways: - a new version of the inspector based on bloc and without glamour. This will take a while to finish, but the goal is to make it until Pharo 6. - as soon as we can hook on object-specific events we will use that mechanism to identify the need for an update > There are some issues tagged for pharo 40. Who will take care of it? > Backport the > fixes or change the milestone > As far as I am concerned, we should keep the backporting to critical cases only. Right now, I see none of them as being critical. > There are some more issues (for example about the > displayString/printString) waiting for > some feedback and comments. > Ok. We will try to go over them. I wasn't happy with the way spotter & co were pushed into the 4.0 release. > To many changes and new features even during code freeze. I do understand > that it was important to have this in the release to get feedback. > But now I wish more support, we already have too many loose ends, > unfinished projects > and to few people working on them. > I do not see the relation between adding spotter and the support. Please help, and keep up working on this or give some feedback or comment > the > open issues. > This is an unfortunate period simply because it is holidays time and there are other things that prevented us to work on it. Cheers, Doru > nicolai > -- www.tudorgirba.com "Every thing has its own flow"

July 4, 2015

[pharo-project/pharo-core]

by GitHub

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

July 3, 2015

[pharo-project/pharo-core] 5d9ea0: 50152

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 5d9ea00183aef364b62935383bf278b307045e12 https://github.com/pharo-project/pharo-core/commit/5d9ea00183aef364b6293538… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-07-04 (Sat, 04 Jul 2015) Changed paths: R Kernel.package/SharedPool.class/class/enumerating/keysDo_.st M Refactoring-Core.package/RBExpandReferencedPoolsRefactoring.class/instance/transforming/poolVariableNamesIn_.st M Refactoring-Core.package/RBRefactoring.class/instance/utilities/poolVariableNamesFor_.st R Refactoring-Core.package/extension/SharedPool/class/keys.st A Reflectivity.package/HookGenerator.class/README.md A Reflectivity.package/HookGenerator.class/class/instance creation/node_.st A Reflectivity.package/HookGenerator.class/definition.st A Reflectivity.package/HookGenerator.class/instance/accessing/links.st A Reflectivity.package/HookGenerator.class/instance/accessing/plugins.st A Reflectivity.package/HookGenerator.class/instance/ast manipulation/encloseInBlock_.st A Reflectivity.package/HookGenerator.class/instance/ast manipulation/selectorForNode.st A Reflectivity.package/HookGenerator.class/instance/ast manipulation/wrapCondition_link_.st A Reflectivity.package/HookGenerator.class/instance/ast manipulation/wrapInContext_link_.st A Reflectivity.package/HookGenerator.class/instance/initialize/node_links_.st A Reflectivity.package/HookGenerator.class/instance/private/genReification_for_.st A Reflectivity.package/HookGenerator.class/instance/private/hookFor_.st A Reflectivity.package/HookGenerator.class/instance/results/afterHooks.st A Reflectivity.package/HookGenerator.class/instance/results/beforeHooks.st A Reflectivity.package/HookGenerator.class/instance/results/hook.st A Reflectivity.package/HookGenerator.class/instance/results/insteadHooks.st A Reflectivity.package/HookGenerator.class/instance/results/preamble.st R Reflectivity.package/HookGenerator2.class/README.md R Reflectivity.package/HookGenerator2.class/class/instance creation/node_.st R Reflectivity.package/HookGenerator2.class/definition.st R Reflectivity.package/HookGenerator2.class/instance/accessing/links.st R Reflectivity.package/HookGenerator2.class/instance/accessing/plugins.st R Reflectivity.package/HookGenerator2.class/instance/ast manipulation/encloseInBlock_.st R Reflectivity.package/HookGenerator2.class/instance/ast manipulation/selectorForNode.st R Reflectivity.package/HookGenerator2.class/instance/ast manipulation/wrapCondition_link_.st R Reflectivity.package/HookGenerator2.class/instance/ast manipulation/wrapInContext_link_.st R Reflectivity.package/HookGenerator2.class/instance/initialize/node_links_.st R Reflectivity.package/HookGenerator2.class/instance/private/genReification_for_.st R Reflectivity.package/HookGenerator2.class/instance/private/hookFor_.st R Reflectivity.package/HookGenerator2.class/instance/results/afterHooks.st R Reflectivity.package/HookGenerator2.class/instance/results/beforeHooks.st R Reflectivity.package/HookGenerator2.class/instance/results/hook.st R Reflectivity.package/HookGenerator2.class/instance/results/insteadHooks.st R Reflectivity.package/HookGenerator2.class/instance/results/preamble.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/analyseForLinks_.st M Reflectivity.package/extension/RBProgramNode/instance/afterHooks.st A Reflectivity.package/extension/RBProgramNode/instance/clearReflectivityAnnotations.st M Reflectivity.package/extension/RBProgramNode/instance/insteadHooks.st M Reflectivity.package/extension/RBProgramNode/instance/link_.st M Reflectivity.package/extension/RBProgramNode/instance/preambles.st M Reflectivity.package/extension/RBProgramNode/instance/removeLink_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50151.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50152.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50151.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50152.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/accessing/selectedMethods.st M Tool-Base.package/SearchFacade.class/class/class search/classSearchInEnvironment_.st M Traits.package/TClass.class/instance/compiling/possibleVariablesFor_continuedFrom_.st Log Message: ----------- 50152 7008 Shared Pools to be treated like dictionaries still necessary? https://pharo.fogbugz.com/f/cases/7008 15886 Find class dialog from a scope nautilus window shows all classes https://pharo.fogbugz.com/f/cases/15886 15889 do not call asOrderedCollection on compiled methods https://pharo.fogbugz.com/f/cases/15889 15892 Cleanups: clean annotation handling + rename HookGenerator2 https://pharo.fogbugz.com/f/cases/15892 http://files.pharo.org/image/50/50152.zip

July 3, 2015

Re: [Pharo-dev] can you explain that?

by Nicolai Hess

2015-07-04 0:27 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-07-04 0:08 GMT+02:00 Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com>: > >> >> >> 2015-07-03 21:22 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >> >>> you can save the image with the shortcut cmd+shift+s >>> the shortcut action is: >>> >>> [ Smalltalk snapshot: true andQuit: false. >>> UIManager default inform: 'Image saved' ] >>> >>> Save the image and show a notification. >>> >>> If you do this shortuct, the image is saved and you'll see the >>> notification - ok. >>> >>> If you close the image, without saving again and open the image again, >>> it starts with showing this notification again. >>> >>> How can this work? The notification was sent after the image was saved. >>> >>> >> It's the activeProcess that saves the image right? >> And the activeProcess is being part of the saved image... >> So guess which activeProcess will get restored when the image is >> restarted (resumed)? >> > > Ah, of course. That explains it. > > Thank you. > > >> >> Normally, snapshoting used to answer a boolean indicating whether the >> image is resuming or not. >> If this hasn't changed in Pharo, this should be something like: >> >> [ (Smalltalk snapshot: true andQuit: false) >> ifFalse: [ UIManager default inform: 'Image saved' ] ] >> > Yes, that works! > >> Nicolas >> > >

July 3, 2015

Re: [Pharo-dev] can you explain that?

by Nicolai Hess

2015-07-04 0:08 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > > > 2015-07-03 21:22 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> you can save the image with the shortcut cmd+shift+s >> the shortcut action is: >> >> [ Smalltalk snapshot: true andQuit: false. >> UIManager default inform: 'Image saved' ] >> >> Save the image and show a notification. >> >> If you do this shortuct, the image is saved and you'll see the >> notification - ok. >> >> If you close the image, without saving again and open the image again, >> it starts with showing this notification again. >> >> How can this work? The notification was sent after the image was saved. >> >> > It's the activeProcess that saves the image right? > And the activeProcess is being part of the saved image... > So guess which activeProcess will get restored when the image is restarted > (resumed)? > Ah, of course. That explains it. Thank you. > > Normally, snapshoting used to answer a boolean indicating whether the > image is resuming or not. > If this hasn't changed in Pharo, this should be something like: > > [ (Smalltalk snapshot: true andQuit: false) > ifFalse: [ UIManager default inform: 'Image saved' ] ] > > Nicolas >

July 3, 2015

Re: [Pharo-dev] can you explain that?

by Nicolas Cellier

2015-07-03 21:22 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > you can save the image with the shortcut cmd+shift+s > the shortcut action is: > > [ Smalltalk snapshot: true andQuit: false. > UIManager default inform: 'Image saved' ] > > Save the image and show a notification. > > If you do this shortuct, the image is saved and you'll see the > notification - ok. > > If you close the image, without saving again and open the image again, > it starts with showing this notification again. > > How can this work? The notification was sent after the image was saved. > > It's the activeProcess that saves the image right? And the activeProcess is being part of the saved image... So guess which activeProcess will get restored when the image is restarted (resumed)? Normally, snapshoting used to answer a boolean indicating whether the image is resuming or not. If this hasn't changed in Pharo, this should be something like: [ (Smalltalk snapshot: true andQuit: false) ifFalse: [ UIManager default inform: 'Image saved' ] ] Nicolas

July 3, 2015

some questions about current GToolkit issues

by Nicolai Hess

15102 <https://pharo.fogbugz.com/default.asp?15102> lost worldmenu Is anyone working on this, it is quite annoying, happens to me a couple of time - per day. Everytime I restart the image to get the menu back. Is there any other way to recreate the worldmenu? 15772 <https://pharo.fogbugz.com/default.asp?15772> spotter is undebuggable Andrei said on the ML he knows what the problem is. Are you working on this? This makes it difficult to work/analyse other spotter bugs. 14569 <https://pharo.fogbugz.com/default.asp?14569> GTInspector should do live updates of objects and their slots This was considered a really important issue. Who works on this, any progress? There are some issues tagged for pharo 40. Who will take care of it? Backport the fixes or change the milestone. There are some more issues (for example about the displayString/printString) waiting for some feedback and comments. I wasn't happy with the way spotter & co were pushed into the 4.0 release. To many changes and new features even during code freeze. I do understand that it was important to have this in the release to get feedback. But now I wish more support, we already have too many loose ends, unfinished projects and to few people working on them. Please help, and keep up working on this or give some feedback or comment the open issues. nicolai

July 3, 2015