Re: [Pharo-dev] SmartBreakpoints alpha release

[Sean P. DeNigris]

Tudor Girba-2 wrote
> TxText should be the future. Perhaps we can... make it a goal for the
> whole community to get it
> finished

+100. This is really important and doesn't seem fair/effective/safe to put
it all on one person's shoulders - even someone as good as Igor ;) Plus we
have gotten burned in the past by relying on one smart person...



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/SmartBreakpoints-alpha-release-tp4769266p4769711.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] SmartBreakpoints alpha release

[Tudor Girba]

Just a point. We should definitely not throw away TxText :).

My message was that we should stop investing in the TextMorph. I suggested
Rubric because it is available now and can be integrated with visible
improvements over what exists.

But, TxText should be the future. Perhaps we can already commit to it for
Pharo 4.0 and then we make it a goal for the whole community to get it
finished. I would be supportive for such a decision.

Doru


On Wed, Jul 23, 2014 at 11:46 AM, Tudor Girba  wrote:

> Hi,
>
> Not yet :(. It's the first thing after releasing the current
> implementation of GT and Moose.
>
> Doru
>
>
> On Wed, Jul 23, 2014 at 11:22 AM, stepharo  wrote:
>
>>
>> On 22/7/14 14:43, Tudor Girba wrote:
>>
>> 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 did you loaded TxText?
>> and TxViewContainer example2
>>
>>
>>  Doru
>>
>>
>> On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker 
>> wrote:
>>
>>>
>>>  On 22 Jul 2014, at 13:57, stepharo  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
>>>
>>>
>>
>>
>>  --
>> www.tudorgirba.com
>>
>>  "Every thing has its own flow"
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>



-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] SmartBreakpoints alpha release

[Tudor Girba]

Hi,

Not yet :(. It's the first thing after releasing the current implementation
of GT and Moose.

Doru


On Wed, Jul 23, 2014 at 11:22 AM, stepharo  wrote:

>
> On 22/7/14 14:43, Tudor Girba wrote:
>
> 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 did you loaded TxText?
> and TxViewContainer example2
>
>
>  Doru
>
>
> On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker 
> wrote:
>
>>
>>  On 22 Jul 2014, at 13:57, stepharo  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
>>
>>
>
>
>  --
> www.tudorgirba.com
>
>  "Every thing has its own flow"
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] SmartBreakpoints alpha release

[stepharo]

On 22/7/14 14:43, Tudor Girba wrote:

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 did you loaded TxText?
and TxViewContainer example2


Doru


On Tue, Jul 22, 2014 at 2:05 PM, Marcus Denker > wrote:



On 22 Jul 2014, at 13:57, stepharo mailto:steph...@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




--
www.tudorgirba.com 

"Every thing has its own flow"

Re: [Pharo-dev] SmartBreakpoints alpha release

[stepharo]

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…


We can also abandon TxText but after we should not cry that it does not 
scale (be prepared
to fork a lot of processes in the background). But I think that it would 
be stupid so we should push igor to deliver.

And if I'm alone pushing then this is not fun.

Have a look at TxViewContainer example2

Stef



Marcus

Re: [Pharo-dev] SmartBreakpoints alpha release

[Sean P. DeNigris]

Clara Allende wrote
> Finally the metaLink-based breakpoints are "ready"...

All sounds very exciting! Thank you!!



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/SmartBreakpoints-alpha-release-tp4769266p4769371.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] SmartBreakpoints alpha release

[Clara Allende]

Fixed!

Thanks for the feedback (and for spotting my bugs ^^)


2014-07-22 15:28 GMT+02:00 Clara Allende :

> Wow :O
> Ok, I will investigate it.
>
>
> 2014-07-22 15:23 GMT+02:00 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 :
>>
>> 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 :
>>>
>>> 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 :

 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 :
>
> 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 :
>>
>> 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 :
>>>
>>>
 On 22 Jul 2014, at 13:57, stepharo  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


>>>
>>
>

>>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[Clara Allende]

Wow :O
Ok, I will investigate it.


2014-07-22 15:23 GMT+02:00 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 :
>
> 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 :
>>
>> 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 :
>>>
>>> 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 :

 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 :
>
> 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 :
>>
>>
>>> On 22 Jul 2014, at 13:57, stepharo  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
>>>
>>>
>>
>

>>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 :

> 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 :
>
> 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 :
>>
>> 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 :
>>>
>>> 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 :

 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 :
>
>
>> On 22 Jul 2014, at 13:57, stepharo  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
>>
>>
>

>>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 :

> 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 :
>
> 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 :
>>
>> 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 :
>>>
>>> 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 :


> On 22 Jul 2014, at 13:57, stepharo  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
>
>

>>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 
wrote:

>
> On 22 Jul 2014, at 13:57, stepharo  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
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 :

> 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 :
>
> 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 :
>>
>> 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 :
>>>
>>>
 On 22 Jul 2014, at 13:57, stepharo  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


>>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 :

> 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 :
>
> 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 :
>>
>>
>>> On 22 Jul 2014, at 13:57, stepharo  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
>>>
>>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[Nicolai Hess]

2014-07-22 14:23 GMT+02:00 Clara Allende :

> 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 :
>
> 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 :
>>
>>
>>> On 22 Jul 2014, at 13:57, stepharo  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
>>>
>>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 :

> 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 :
>
>
>> On 22 Jul 2014, at 13:57, stepharo  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
>>
>>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 :

>
> On 22 Jul 2014, at 13:57, stepharo  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
>
>

Re: [Pharo-dev] SmartBreakpoints alpha release

[Marcus Denker]

On 22 Jul 2014, at 13:57, stepharo  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

Re: [Pharo-dev] SmartBreakpoints alpha release

[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 
, 
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

Re: [Pharo-dev] SmartBreakpoints alpha release

[Marcus Denker]

On 22 Jul 2014, at 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! 

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

[Pharo-dev] SmartBreakpoints alpha release

[Clara Allende]

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 ;)
* hide breakpoint-api contexts in the debugger stack