improving print-it in playground

Hi Doru,
works nicely and makes the playground for the first time actually usable
for me. i like the way it works: the automatic commenting and that i
only need to press enter.
werner

one thing, i guess it could eventually be preferable if the comment
would go on the next line so that one can repeatedly evaluate or print
that line. this is at least a common use case for me.
werner

On 01/19/2015 10:01 AM, Werner Kassens wrote:
> Hi Doru,
> works nicely and makes the playground for the first time actually usable
> for me. i like the way it works: the automatic commenting and that i
> only need to press enter.
> werner
>
>
>

On 01/19/2015 10:07 AM, Tudor Girba wrote:
> I am still looking for concrete use cases why people need to see the
> printout in the editor. Could you provide an example of when you need it?
for example for making documentation like
https://github.com/SergeStinckwich/SciSmalltalk/wiki/Math-DHB-wk
werne

> Aha. So, you want to compare multiple runs of the same code?
very often, yes
werner

For me, you nailed it.
It makes Playgrounds even more useful.
I also want this in every code pane, including all browsers.

> On 19 Jan 2015, at 06:07, Tudor Girba <[hidden email]> wrote:
>
> Thanks for the feedback.
>
> I am still looking for concrete use cases why people need to see the printout in the editor. Could you provide an example of when you need it?

I like to construct expressions step by step, printing the result inbetween.

        Marcus

Yes, the print-it now is much better than the classic ST behavior! I appreciate the latest feature of being able to get the response as commented text. I have needed that in the past, sporadically. (But I don’t remember specific cases, sorry.)

Le 19/1/15 10:01, Werner Kassens a écrit :
> Hi Doru,
> works nicely and makes the playground for the first time actually
> usable for me. i like the way it works: the automatic commenting and
> that i only need to press enter.

:)
I suggested to put it on the next line in addition :)
> werner
>
>
>

Le 19/1/15 14:18, Marcus Denker a écrit :
>> On 19 Jan 2015, at 06:07, Tudor Girba <[hidden email]> wrote:
>>
>> Thanks for the feedback.
>>
>> I am still looking for concrete use cases why people need to see the printout in the editor. Could you provide an example of when you need it?
> I like to construct expressions step by step, printing the result inbetween.

but you have to remove them after.
Normally for inbteween I look and discard it with esc then continue to
the next one.
>
> Marcus
>
>
>

Le 19/1/15 10:15, Werner Kassens a écrit :
> one thing, i guess it could eventually be preferable if the comment
> would go on the next line so that one can repeatedly evaluate or print
> that line. this is at least a common use case for me.

yes me too.

Hi Werner,

Aha. So, you want to compare multiple runs of the same code?

not necessarily

Do you use the print-it for anything else?

keep trace.

Cheers,

Doru

On Mon, Jan 19, 2015 at 10:15 AM, Werner Kassens <[hidden email]> wrote:

one thing, i guess it could eventually be preferable if the comment would go on the next line so that one can repeatedly evaluate or print that line. this is at least a common use case for me.
werner

On 01/19/2015 10:01 AM, Werner Kassens wrote:

Hi Doru,
works nicely and makes the playground for the first time actually usable
for me. i like the way it works: the automatic commenting and that i
only need to press enter.
werner

--

www.tudorgirba.com

"Every thing has its own flow"

Excerpts from Tudor Girba's message of 2015-01-19 08:33:04 +0100:
> I worked with Andrei to find a solution for improving the print-it support.
> You can take a look here:
> http://www.humane-assessment.com/blog/improving-print-it-support-in-gtplayground

have not tried it yet, but i wondered about this problem.
as mentioned elsewhere, i too would like this in every textbox.

most notably in the debugger where i do a lot of print-it to find out the value
of some expression.

i'd also like to pick up on the idea that when there is no selection the whole
line will be evaluated (btw, there is a typo, you wrote like), and that line
will only be highlighted.

the idea is great, but what about if i do evaluate a selection?
could in that case the selection be turned into a highlight?
there is no way around to make a selection in order to evaluate it, (unless
some form of shift-control-whatver-key+mouse selection is introduced) but once
evaluated it is clear that i didn't intend to select to replace the text, and
i'd like to avoid doing so accidentally.

also, would it make sense to keep the highlight until another piece of code is
evaluated?

greetings, martin.

--
eKita                   -   the online platform for your entire academic life
--
chief engineer                                                       eKita.co
pike programmer      pike.lysator.liu.se    caudium.net     societyserver.org
secretary                                                      beijinglug.org
mentor                                                           fossasia.org
foresight developer  foresightlinux.org                            realss.com
unix sysadmin
Martin Bähr          working in china        http://societyserver.org/mbaehr/

Hi,

I worked with Andrei to find a solution for improving the print-it support. You can take a look here:

http://www.humane-assessment.com/blog/improving-print-it-support-in-gtplayground

The current solution can be found in the latest Pharo image.

Cheers,

Doru

--

www.tudorgirba.com

"Every thing has its own flow"

can you send a screen shot?

A two-column UI similar to the Swift playground may be useful. Everything would be printed in parallel in a separate column. (The aforementioned output may be partially visually obscured by half a dozen means for output "typically" considered irrelevant — for example, perhaps a disclosure triangle for excessive lines.) And if one did a Do It on a selection in the "print" column, it would echo (copy) the selection over in the "workspace" column and show the printed action in the "print" column accordingly. There are many, many ways to implement all the details for smooth workflow behavior. 

On Jan 19, 2015, at 1:33 AM, Tudor Girba <[hidden email]> wrote:

Hi,

I worked with Andrei to find a solution for improving the print-it support. You can take a look here:

http://www.humane-assessment.com/blog/improving-print-it-support-in-gtplayground

The current solution can be found in the latest Pharo image.

Cheers,

Doru

--

www.tudorgirba.com

"Every thing has its own flow"

Excerpts from Ben Coman's message of 2015-01-25 04:55:45 +0100:
> > I am still looking for concrete use cases why people need to see the
> > printout in the editor. Could you provide an example of when you need it?
> Here is one I just had.  I wanted to select the result of this...
>      Object allMethods detect: [ :m | m senders size = 1 ]
> so that I could press the shortcut key for "all senders" on it to view that
> code.

shortcuts and mouse-clicks should work on the popup as they work on a selection.

i had a case where the popup was to on the right edge partly off the screen
that the inspect icon was not accessible. a problem in itself, but being able
to use short-cuts as normal would have helped.

greetings, martin.

--
eKita                   -   the online platform for your entire academic life
--
chief engineer                                                       eKita.co
pike programmer      pike.lysator.liu.se    caudium.net     societyserver.org
secretary                                                      beijinglug.org
mentor                                                           fossasia.org
foresight developer  foresightlinux.org                            realss.com
unix sysadmin
Martin Bähr          working in china        http://societyserver.org/mbaehr/