- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

July 22, 2014

[pharo-project/pharo-core] f357ce: 40115

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f357ceecd7294ab27f3af5569c580ab70e3f2e87 https://github.com/pharo-project/pharo-core/commit/f357ceecd7294ab27f3af556… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-22 (Tue, 22 Jul 2014) Changed paths: R Compiler.package/extension/Context/class/isContextClass.st R Compiler.package/extension/InstructionStream/class/instVarNamesAndOffsetsDo_.st R Compiler.package/extension/InstructionStream/class/isContextClass.st A Kernel.package/Context.class/class/testing/isContextClass.st A Kernel.package/InstructionStream.class/class/compiling/instVarNamesAndOffsetsDo_.st A Kernel.package/InstructionStream.class/class/testing/isContextClass.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson01.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson02.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson03.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson04.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson05.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson06.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson07.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson08.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson10.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson11.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson11Author.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson11Blessing.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson11Descripton.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson11Timestamp.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson12DoIts.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart1.class/instance/lessons/lesson13.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart2.class/instance/lessons/lesson07.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart2.class/instance/lessons/lesson10.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart2.class/instance/lessons/lesson11.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart2.class/instance/lessons/lesson12.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart2.class/instance/lessons/lesson13.st M Metacello-ProfStef.package/MetacelloConfigurationTutorialPart2.class/instance/lessons/lesson14.st M Metacello-ProfStef.package/MetacelloDevelopmentProcess.class/instance/intro/introductionText.st M Metacello-ProfStef.package/MetacelloDevelopmentProcess.class/instance/lessons/createConfigurationAndBaseline.st M Metacello-ProfStef.package/MetacelloDevelopmentProcess.class/instance/lessons/createDevelopmentVersion.st M Network-MIME.package/Base64MimeConverter.class/class/encoding/decodeInteger_.st M Network-MIME.package/Base64MimeConverter.class/definition.st M Network-MIME.package/Base64MimeConverter.class/instance/conversion/mimeEncode.st R Network-MIME.package/MIMELocalFileDocument.class/README.md R Network-MIME.package/MIMELocalFileDocument.class/class/instance creation/contentType_contentStream_.st R Network-MIME.package/MIMELocalFileDocument.class/definition.st R Network-MIME.package/MIMELocalFileDocument.class/instance/accessing/content.st R Network-MIME.package/MIMELocalFileDocument.class/instance/accessing/contentStream.st R Network-MIME.package/MIMELocalFileDocument.class/instance/accessing/contentStream_.st M Network-MIME.package/extension/String/instance/decodeMimeHeader.st M Network-Mail.package/MIMEHeaderValue.class/instance/printing/asHeaderValue.st M Network-Mail.package/MailAddressParser.class/instance/building address list/startNewAddress.st M Network-Mail.package/MailAddressTokenizer.class/instance/stream protocol/atEnd.st M Network-Mail.package/MailComposition.class/instance/interface/addAttachment.st M Network-Mail.package/MailComposition.class/instance/private/breakLinesInMessage_.st M Network-Mail.package/MailMessage.class/class/instance creation/from_to_about_asFollows_.st M Network-Mail.package/MailMessage.class/class/preferences/omittedHeaderFields.st R Network-Mail.package/MailMessage.class/instance/multipart/addPart_contentType_.st R Network-Mail.package/MailMessage.class/instance/multipart/save.st M Network-Mail.package/MailMessage.class/instance/parsing/fieldsFrom_do_.st M Network-Mail.package/MailMessage.class/instance/parsing/skipWeekdayName_.st M Network-Mail.package/MailMessage.class/instance/printing%2Fformatting/cleanedHeader.st A Network-Mail.package/TextMessageLink.class/instance/accessing/message.st R Network-Mail.package/TextMessageLink.class/instance/acting/mayActOnClick_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script115.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40115.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R UserManager-Core.package/UserManager.class/class/initialization/initialize.st R UserManager-Core.package/UserManager.class/class/tool registration/registerToolsOn_.st Log Message: ----------- 40115 13645 Small CodeCritique Cleanup of Network-Mail https://pharo.fogbugz.com/f/cases/13645 13643 Move extensions of Package Compiler to Kernel https://pharo.fogbugz.com/f/cases/13643 13642 remove registration of #userManager from ToolsRegistry https://pharo.fogbugz.com/f/cases/13642 12975 Metacello ProfStef use inexistant browse:selector: https://pharo.fogbugz.com/f/cases/12975 13644 Small Codecritic cleanup of Network-MIME https://pharo.fogbugz.com/f/cases/13644 13646 MIMELocalFileDocument seems to be dead code https://pharo.fogbugz.com/f/cases/13646 http://files.pharo.org/image/40/40115.zip

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Clara Allende

Wow :O Ok, I will investigate it. 2014-07-22 15:23 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > Yes, this works now. > > > But I just found out, that a methods version list is empty after adding a > break point. > Just go to a method (for example FileList>>initialize). Show the version > of this methdo. > Add a break point. > Now the version list is empty. > > > > 2014-07-22 14:53 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > > Ok, same that I did :) >> >> So I've spotted this one: I was using an old version of Spec-Debugger, >> which uses a deprecated method. >> Can you try again now? I've just commited the fix and updated the >> configuration. >> >> Thanks again :D >> >> >> 2014-07-22 14:40 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >> >> No real use case, I just read your blog entry, installed your package >>> and choosed a random method and add a breakpoint :) >>> >>> >>> >>> >>> >>> >>> 2014-07-22 14:32 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >>> >>> I have downloaded a new fresh image (40114) and I get a deprecation >>>> warning. So I will check it out, but could you tell me your use case as >>>> well (maybe send me an email so we don't spam the list)? >>>> >>>> Thanks! >>>> >>>> >>>> 2014-07-22 14:23 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >>>> >>>> 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

Yes, this works now. But I just found out, that a methods version list is empty after adding a break point. Just go to a method (for example FileList>>initialize). Show the version of this methdo. Add a break point. Now the version list is empty. 2014-07-22 14:53 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > Ok, same that I did :) > > So I've spotted this one: I was using an old version of Spec-Debugger, > which uses a deprecated method. > Can you try again now? I've just commited the fix and updated the > configuration. > > Thanks again :D > > > 2014-07-22 14:40 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > No real use case, I just read your blog entry, installed your package and >> choosed a random method and add a breakpoint :) >> >> >> >> >> >> >> 2014-07-22 14:32 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >> >> I have downloaded a new fresh image (40114) and I get a deprecation >>> warning. So I will check it out, but could you tell me your use case as >>> well (maybe send me an email so we don't spam the list)? >>> >>> Thanks! >>> >>> >>> 2014-07-22 14:23 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >>> >>> 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 Clara Allende

Ok, same that I did :) So I've spotted this one: I was using an old version of Spec-Debugger, which uses a deprecated method. Can you try again now? I've just commited the fix and updated the configuration. Thanks again :D 2014-07-22 14:40 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > No real use case, I just read your blog entry, installed your package and > choosed a random method and add a breakpoint :) > > > > > > > 2014-07-22 14:32 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > > I have downloaded a new fresh image (40114) and I get a deprecation >> warning. So I will check it out, but could you tell me your use case as >> well (maybe send me an email so we don't spam the list)? >> >> Thanks! >> >> >> 2014-07-22 14:23 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: >> >> 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 Tudor Girba

First of all: Excellent job! About the editor: I would indeed suggest adopting Rubric as a solution for now (until the new Text widget comes around). We use it extensively in GT and I can attest that it is better than PluggableTextMorph. Doru On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 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 > > -- www.tudorgirba.com "Every thing has its own flow"

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Nicolai Hess

No real use case, I just read your blog entry, installed your package and choosed a random method and add a breakpoint :) 2014-07-22 14:32 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > I have downloaded a new fresh image (40114) and I get a deprecation > warning. So I will check it out, but could you tell me your use case as > well (maybe send me an email so we don't spam the list)? > > Thanks! > > > 2014-07-22 14:23 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > > 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] future of Nautilus (the non package tree version)

by Nicolai Hess

2014-07-22 14:28 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > 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 <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? > > > yes. > I made the PackageTreeNautilus as a replacement, but an extension because > I was using Nautilus to develop Nautilus. > Now we should merge it. > This might be a big effort, but this also gives us the opportunity to clean up. > > Esteban > > > nicolai > > > >

July 22, 2014

Re: [Pharo-dev] SmartBreakpoints alpha release

by Nicolai Hess

2014-07-22 14:23 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > Weird, I tried loading it in 40111 and it was working. > Was it a fresh image? > Yes, the deprecation warning is: ToolRegistry>>userManager has been deprecated. > > > 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 Clara Allende

I have downloaded a new fresh image (40114) and I get a deprecation warning. So I will check it out, but could you tell me your use case as well (maybe send me an email so we don't spam the list)? Thanks! 2014-07-22 14:23 GMT+02:00 Clara Allende <clari.allende(a)gmail.com>: > 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