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

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

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