[Pharo-dev] Playground and text evaluation printing result default.

Hi I would like to know if there is a setting to remove the "" when printing the result of an expression. I know that playground has been thought to help me, but today I watched myself removing the comments code so often that I would like to get a setting because such wrapping of results i

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi Stef, The quotes appear only when you add the result in the playground. The typical use case for this is to keep track of several results. In this situation you do not want to modify the code to not affect the highlighting and this is why it gets in a comment. If you want to copy the conten

Re: [Pharo-dev] Playground and text evaluation printing result default.

Le 5/6/16 à 23:00, Tudor Girba a écrit : Hi Stef, The quotes appear only when you add the result in the playground. No need to explain I'm not idiot and I know it. The typical use case for this is to keep track of several results. No need to explain I'm not idiot and I know it. In this si

Re: [Pharo-dev] Playground and text evaluation printing result default.

On Tue, Jun 7, 2016 at 2:09 PM, stepharo wrote: > > > Le 5/6/16 à 23:00, Tudor Girba a écrit : >> >> Hi Stef, >> >> The quotes appear only when you add the result in the playground. > > > No need to explain I'm not idiot and I know it. >> >> The typical use case for this is to keep track of severa

Re: [Pharo-dev] Playground and text evaluation printing result default.

The #printString of most objects is not valid Pharo syntax, it makes sense to put those into comments, so that the overall syntax of the workspace/playground is maintained and syntax highlighting can operate normally. A result printed as a comment is also easy to select (by double-clicking next

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi Stef, Thanks for the feedback. Sorry for the long email, but I you raised several issues and I thought it is worth addressing them. The feature we are talking about came into being after several suggestions on this mailing list (and quite some long discussions) that had the scenario of keep

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi Sven, If I understand correctly, Stef talks about the case of building tests in the debugger. There he tries an expression and then wants to capture the result of the expression as an assertion in the code so he wants to paste the result directly. It is a different scenario than the one of c

Re: [Pharo-dev] Playground and text evaluation printing result default.

On Wed, Jun 8, 2016 at 5:39 AM, Tudor Girba wrote: > Hi Sven, > > If I understand correctly, Stef talks about the case of building tests in the > debugger. There he tries an expression and then wants to capture the result > of the expression as an assertion in the code so he wants to paste the r

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi, > On Jun 8, 2016, at 2:04 AM, Ben Coman wrote: > > On Wed, Jun 8, 2016 at 5:39 AM, Tudor Girba wrote: >> Hi Sven, >> >> If I understand correctly, Stef talks about the case of building tests in >> the debugger. There he tries an expression and then wants to capture the >> result of the e

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi Stef, Thanks for the feedback. Sorry for the long email, but I you raised several issues and I thought it is worth addressing them. The feature we are talking about came into being after several suggestions on this mailing list (and quite some long discussions) that had the scenario of k

Re: [Pharo-dev] Playground and text evaluation printing result default.

You remember certainly this book that said that most users are looking at ui the same way that we see a bear dansing in tutu while it should be a classical dancer with grace. So users adapt to things even if some of them are hurting them. I don't. I do not like that I have to fight to get thi

Re: [Pharo-dev] Playground and text evaluation printing result default.

"La perfection n'est atteinte non pas quand il n'y a plus rien a ajouter mais plus rien a enlever" Saint Exupery. I'm curious to see the results of the data you collected about spotter usage. Because we have around 50 processors and may be we need more? Who knows. Personnally I succeeded to

Re: [Pharo-dev] Playground and text evaluation printing result default.

Le 8/6/16 à 09:04, stepharo a écrit : This is incorrect. If you would not complain aggressively, we would simply have a smoother conversation about solutions. My final point: Aggressivity is often the result of not being heard. So now you can argue that you listen :) But I decided that

Re: [Pharo-dev] Playground and text evaluation printing result default.

> On 08 Jun 2016, at 09:04, stepharo wrote: > > the fact that I cannot access Spotter without hurting my hand it is also > probably why I do not try more. yeah, shortcut has to be configurable, for people with big hands :)

Re: [Pharo-dev] Playground and text evaluation printing result default.

On Wed, Jun 8, 2016 at 2:01 PM, Tudor Girba wrote: > Hi, > >> On Jun 8, 2016, at 2:04 AM, Ben Coman wrote: >> >> On Wed, Jun 8, 2016 at 5:39 AM, Tudor Girba wrote: >>> Hi Sven, >>> >>> If I understand correctly, Stef talks about the case of building tests in >>> the debugger. There he tries an

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi, Thanks. Interesting. I do not yet see it yet, but there is something intriguing about it. It would be interesting to play with this in more details. Cheers, Tudor > On Jun 8, 2016, at 12:24 PM, Ben Coman wrote: > > On Wed, Jun 8, 2016 at 2:01 PM, Tudor Girba wrote: >> Hi, >> >>> On Ju

Re: [Pharo-dev] Playground and text evaluation printing result default.

Yes, we already agreed on that both for the debugger and for Spotter. We just did not get the chance to do it yet. Doru > On Jun 8, 2016, at 11:33 AM, Esteban Lorenzano wrote: > > >> On 08 Jun 2016, at 09:04, stepharo wrote: >> >> the fact that I cannot access Spotter without hurting my h

Re: [Pharo-dev] Playground and text evaluation printing result default.

2016-06-08 19:11 GMT+02:00 Tudor Girba : > Yes, we already agreed on that both for the debugger and for Spotter. We > just did not get the chance to do it yet. > Hey Doru, about your report https://pharo.fogbugz.com/f/cases/18455 Spotter shortcuts should be externalized as settings Please don't

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi nicolai Indeed we need on way to define "menuItem action" I do not know if it should be bound to shortcut but it should have a shortcut. I saw that Glamour has one way, the core other ways and probably Spec a third one. So this is really confusing. With guille we discussed a while ago

Re: [Pharo-dev] Playground and text evaluation printing result default.

Le 8/6/16 à 11:33, Esteban Lorenzano a écrit : On 08 Jun 2016, at 09:04, stepharo > wrote: the fact that I cannot access Spotter without hurting my hand it is also probably why I do not try more. yeah, shortcut has to be configurable, for people with big hands :)

Re: [Pharo-dev] Playground and text evaluation printing result default.

2016-06-08 19:45 GMT+02:00 stepharo : > Hi nicolai > > Indeed we need on way to define "menuItem action" > > I do not know if it should be bound to shortcut but it should have a > shortcut. > > I saw that Glamour has one way, the core other ways and probably Spec a > third one. > > So this is real

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi, > On Jun 8, 2016, at 9:12 AM, stepharo wrote: > > Le 8/6/16 à 09:04, stepharo a écrit : > >> This is incorrect. If you would not complain aggressively, we would simply >> have a smoother conversation about solutions. > My final point: > >Aggressivity is often the result of not being

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi, > On Jun 8, 2016, at 8:44 AM, stepharo wrote: > >> >> Hi Stef, >> >> Thanks for the feedback. Sorry for the long email, but I you raised several >> issues and I thought it is worth addressing them. >> >> The feature we are talking about came into being after several suggestions >> on th

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi Stef, Thanks for the feedback. Sorry for the long email, but I you raised several issues and I thought it is worth addressing them. The feature we are talking about came into being after several suggestions on this mailing list (and quite some long discussions) that had the scenario of k

Re: [Pharo-dev] Playground and text evaluation printing result default.

Hi, > On Jun 10, 2016, at 8:48 AM, stepharo wrote: > Hi Stef, Thanks for the feedback. Sorry for the long email, but I you raised several issues and I thought it is worth addressing them. The feature we are talking about came into being after several sugges