- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] future of Nautilus (the non package tree version)

by Esteban Lorenzano

On 22 Jul 2014, at 14:26, Nicolai Hess <nicolaihess(a)web.de> wrote: > From time to time it happens that we introduce bugs in the "old" Nautilus > browser if we do changes for the default browser (PackageTreeNautilus) > For example: > 13640 > no menu on package pane in Nautilus (the non package tree nautilus) > > Is a working "old" Nautilus on high priority? Or should we consider > PackageTreeNautilus as a replacement for Nautilus? yes. I made the PackageTreeNautilus as a replacement, but an extension because I was using Nautilus to develop Nautilus. Now we should merge it. Esteban > > nicolai > >

July 22, 2014

future of Nautilus (the non package tree version)

by Nicolai Hess

>From time to time it happens that we introduce bugs in the "old" Nautilus browser if we do changes for the default browser (PackageTreeNautilus) For example: 13640 <https://pharo.fogbugz.com/default.asp?13640> no menu on package pane in Nautilus (the non package tree nautilus) Is a working "old" Nautilus on high priority? Or should we consider PackageTreeNautilus as a replacement for Nautilus? nicolai

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Clara Allende

Weird, I tried loading it in 40111 and it was working. Was it a fresh image? 2014-07-22 14:16 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > The current version from > Gofer it > smalltalkhubUser: 'ClaraAllende' project: 'SmartBreakpoints'; > configurationOf: 'SmartBreakpoints'; > loadStable . > > raises some deprecation warnings and missing classOrMetaClass selector > with pharo 40111 > can you put a link on your blog for a working pharo 4.0 image? > > > > > 2014-07-22 14:05 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > >> On 22 Jul 2014, at 13:57, stepharo <stepharo(a)free.fr> wrote: >> >> >> On 22/7/14 10:41, Clara Allende wrote: >> >> Hi guys! >> Finally the metaLink-based breakpoints are "ready". I have made some >> explanations on my blog >> <https://clariallende.wordpress.com/2014/07/21/smartbreakpoints-alpha-releas…>, >> but basically now you have the option "break here" in SmartSuggestions menu. >> So it's still experimental, and even though I have some tests, it would >> be nice if you can test it, because I can't cover all possible use cases :) >> And any feedback is most appreciated! >> >> Specially, since eventually we will have several kinds of breakpoints, >> I would like to ask in which way would you like to choose them (a pop menu? >> a sublist?) >> >> Thanks in advance! >> >> PS: The script for downloading the code is in the blog post :P >> PS2: After talking with Anne and Baptiste, things that are not there >> *yet* but I want to have: >> * a highlight on the method/messageSend where the breakpoint is inserted >> * expose persistent breakpoints (it is there but the default is to halt >> once) >> * line breakpoints (not sure when, for now the breakpoints are AST based) >> * integration with TextEditor, once it is done ;) >> >> >> Can you grab igor and sit with him to get this point? >> >> Another idea would be to use the editor in Moose (Rubrik?). >> Better a solution now than to wait forever for perfectionâ¦ >> >> Marcus >> >> >

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Nicolai Hess

The current version from Gofer it smalltalkhubUser: 'ClaraAllende' project: 'SmartBreakpoints'; configurationOf: 'SmartBreakpoints'; loadStable . raises some deprecation warnings and missing classOrMetaClass selector with pharo 40111 can you put a link on your blog for a working pharo 4.0 image? 2014-07-22 14:05 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 22 Jul 2014, at 13:57, stepharo <stepharo(a)free.fr> wrote: > > > On 22/7/14 10:41, Clara Allende wrote: > > Hi guys! > Finally the metaLink-based breakpoints are "ready". I have made some > explanations on my blog > <https://clariallende.wordpress.com/2014/07/21/smartbreakpoints-alpha-releas…>, > but basically now you have the option "break here" in SmartSuggestions menu. > So it's still experimental, and even though I have some tests, it would be > nice if you can test it, because I can't cover all possible use cases :) > And any feedback is most appreciated! > > Specially, since eventually we will have several kinds of breakpoints, I > would like to ask in which way would you like to choose them (a pop menu? a > sublist?) > > Thanks in advance! > > PS: The script for downloading the code is in the blog post :P > PS2: After talking with Anne and Baptiste, things that are not there *yet* > but I want to have: > * a highlight on the method/messageSend where the breakpoint is inserted > * expose persistent breakpoints (it is there but the default is to halt > once) > * line breakpoints (not sure when, for now the breakpoints are AST based) > * integration with TextEditor, once it is done ;) > > > Can you grab igor and sit with him to get this point? > > Another idea would be to use the editor in Moose (Rubrik?). > Better a solution now than to wait forever for perfectionâ¦ > > Marcus > >

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Marcus Denker

On 22 Jul 2014, at 13:57, stepharo <stepharo(a)free.fr> wrote: > > On 22/7/14 10:41, Clara Allende wrote: >> Hi guys! >> Finally the metaLink-based breakpoints are "ready". I have made some explanations on my blog, but basically now you have the option "break here" in SmartSuggestions menu. >> So it's still experimental, and even though I have some tests, it would be nice if you can test it, because I can't cover all possible use cases :) >> And any feedback is most appreciated! >> >> Specially, since eventually we will have several kinds of breakpoints, I would like to ask in which way would you like to choose them (a pop menu? a sublist?) >> >> Thanks in advance! >> >> PS: The script for downloading the code is in the blog post :P >> PS2: After talking with Anne and Baptiste, things that are not there yet but I want to have: >> * a highlight on the method/messageSend where the breakpoint is inserted >> * expose persistent breakpoints (it is there but the default is to halt once) >> * line breakpoints (not sure when, for now the breakpoints are AST based) >> * integration with TextEditor, once it is done ;) > > Can you grab igor and sit with him to get this point? Another idea would be to use the editor in Moose (Rubrik?). Better a solution now than to wait forever for perfectionâ¦ Marcus

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by stepharo

On 22/7/14 10:41, Clara Allende wrote: > Hi guys! > Finally the metaLink-based breakpoints are "ready". I have made some > explanations on my blog > <https://clariallende.wordpress.com/2014/07/21/smartbreakpoints-alpha-releas…>, > but basically now you have the option "break here" in SmartSuggestions > menu. > So it's still experimental, and even though I have some tests, it > would be nice if you can test it, because I can't cover all possible > use cases :) > And any feedback is most appreciated! > > Specially, since eventually we will have several kinds of breakpoints, > I would like to ask in which way would you like to choose them (a pop > menu? a sublist?) > > Thanks in advance! > > PS: The script for downloading the code is in the blog post :P > PS2: After talking with Anne and Baptiste, things that are not there > *yet* but I want to have: > * a highlight on the method/messageSend where the breakpoint is inserted > * expose persistent breakpoints (it is there but the default is to > halt once) > * line breakpoints (not sure when, for now the breakpoints are AST based) > * integration with TextEditor, once it is done ;) Can you grab igor and sit with him to get this point? > * hide breakpoint-api contexts in the debugger stack

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Marcus Denker

On 22 Jul 2014, at 10:41, Clara Allende <clari.allende(a)gmail.com> wrote: > Hi guys! > Finally the metaLink-based breakpoints are "ready". I have made some explanations on my blog, but basically now you have the option "break here" in SmartSuggestions menu. > So it's still experimental, and even though I have some tests, it would be nice if you can test it, because I can't cover all possible use cases :) > And any feedback is most appreciated! Very niceâ¦ as this is based on the Link/Metaobject model, we will later be able to put BreakPoints (and Watchpoints) not only on a single variable access in a method, but on the Varaible itself. âbreak when you store next time into this variableâ, for example. Marcus

July 22, 2014

[pharo-project/pharo-core]

by GitHub

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

July 22, 2014

[pharo-project/pharo-core] 73be77: 40114

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 73be77d747679c87bceacf48434fc66f9df1f589 https://github.com/pharo-project/pharo-core/commit/73be77d747679c87bceacf48… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-22 (Tue, 22 Jul 2014) Changed paths: M Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/README.md M Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/definition.st M Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/initialization/initialize.st A Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/initialize-release/anInstVar.st A Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/initialize-release/anInstVar_.st A Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/initialize-release/classBlock.st R Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/instance/initialize-release/classBlock_.st M Refactoring-Tests-Core.package/RBRenameInstanceVariableTest.class/instance/tests/testRenameInstVar.st A Refactoring-Tests-Core.package/RBRenameInstanceVariableTest.class/instance/tests/testRenameInstVarAccessorsReferences.st R SUnit-Utilities.package/SUnitUnloader.class/README.md R SUnit-Utilities.package/SUnitUnloader.class/definition.st R SUnit-Utilities.package/SUnitUnloader.class/instance/private/sortedForRemoveClasses_.st R SUnit-Utilities.package/SUnitUnloader.class/instance/private/sortedForRemovePackages_.st R SUnit-Utilities.package/SUnitUnloader.class/instance/private/sunitPackages.st R SUnit-Utilities.package/SUnitUnloader.class/instance/private/unloadPackages_.st R SUnit-Utilities.package/SUnitUnloader.class/instance/private/unloadSUnit.st R SUnit-Utilities.package/SUnitUnloader.class/instance/unloading/testPackages.st R SUnit-Utilities.package/SUnitUnloader.class/instance/unloading/unloadAll.st R SUnit-Utilities.package/SUnitUnloader.class/instance/unloading/unloadTestCases.st R SUnit-Utilities.package/SUnitUnloader.class/instance/unloading/unloadTestPackages.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script114.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40114.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40114 13638 remove SUnitUnloader https://pharo.fogbugz.com/f/cases/13638 13588 Rename inst var should rename accessors too https://pharo.fogbugz.com/f/cases/13588 http://files.pharo.org/image/40/40114.zip

July 22, 2014

Re: [Pharo-dev] Updated DrGeo page on wikipedia

by Nicolai Hess

2014-07-22 9:44 GMT+02:00 kilon alios <kilon.alios(a)gmail.com>: > Why this guilty ? who is better to talk about a software than its best > contributor or one of the best / most active contributors ? > > Been biased is a choice. You can choose to be biased , which means > letting your emotions overcome your reasoning. The fact that you are the > author of the project does not make you biased, you choose to be or not be > biased. > > DrGeo first release was back in 1995 ? wow , thats 2 decades of work :) > > You need to add some pictures, the application is meant to appeal to > students, students love pictures. More information also would not hurt, > show people what makes Dr Geo special . Thats the beauty of wikipedia you > start with a summary and then if you are interested you go to the relevant > section to find all the juicy details about the parts that interest you. > Maybe the Logo and one image showing the user interface. I would remove the "sugar" entry from "operating systems". Is DrGeo II installable for OLPC? Force on the "teaching and learning" aspect. I like this text from the user guide more than the current introduction on wikipedia: The Dr. Geo user interface, under the form of great simplicity, allows the beginner to get acquainted very quickly with the basic functions of the software. Then, as the user progresses, the more advanced aspects of the interface and the capabilities of Dr. Geo will become apparent, such as multiple methods of construction of each kind of object,1 macro construction, multiple recording, scripts, Smalltalk sketches, and inheritance of Smalltalk in Dr. Geo. These advanced features generate little overload on the interface, which is why Dr. Geo is very pleasant for use in primary education; however they also make it very interesting for use in high school and university. > > > On Tue, Jul 22, 2014 at 10:16 AM, stepharo <stepharo(a)free.fr> wrote: > >> I got the same feeling about Pharo :) >> >> Stef >> >> >> On 22/7/14 06:29, Hilaire wrote: >> >>> Hi, >>> >>> I finally decided to update myself the Dr. Geo wikipedia page, although >>> I don't really like doing so, as the author I may not have the appropriate >>> neutral tone needed for wikipedia articles. Anyway I was sick to see out of >>> date information related to Dr. Geo (mostly C++ version based). If any >>> comment or additional information should be added, please tell me. >>> >>> Thanks >>> >>> https://en.wikipedia.org/wiki/DrGeo >>> >>> >> >> >

July 22, 2014