Re: [Pharo-dev] Resizing of the print block (Pharo 4.0)

2015-04-03 Thread Gaurav Singh
Thanks Tudor :)

On Fri, Apr 3, 2015 at 10:00 PM, Tudor Girba  wrote:

> No, the print popup dimension is not changeable at the moment.
>
> But, Ii you want, you can embed the print string in the Playground by
> pressing Enter.
>
> Cheers,
> Doru
>
>
> On Fri, Apr 3, 2015 at 2:31 PM, Gaurav Singh 
> wrote:
>
>> Is there a way to resize the print block in the playground? Sometimes
>> when the string is quite a bit long the print block never goes beyond a
>> specific dimension which is quite less and therefore we have to scroll down
>> more rows to check the output and the only way to see the better output is
>> the inspector whereas in Pharo 3.0 we saw that the output depended on the
>> size of the workspace.
>>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>


Re: [Pharo-dev] Resizing of the print block (Pharo 4.0)

2015-04-03 Thread Tudor Girba
No, the print popup dimension is not changeable at the moment.

But, Ii you want, you can embed the print string in the Playground by
pressing Enter.

Cheers,
Doru


On Fri, Apr 3, 2015 at 2:31 PM, Gaurav Singh  wrote:

> Is there a way to resize the print block in the playground? Sometimes when
> the string is quite a bit long the print block never goes beyond a specific
> dimension which is quite less and therefore we have to scroll down more
> rows to check the output and the only way to see the better output is the
> inspector whereas in Pharo 3.0 we saw that the output depended on the size
> of the workspace.
>



-- 
www.tudorgirba.com

"Every thing has its own flow"


[Pharo-dev] Resizing of the print block (Pharo 4.0)

2015-04-03 Thread Gaurav Singh
Is there a way to resize the print block in the playground? Sometimes when
the string is quite a bit long the print block never goes beyond a specific
dimension which is quite less and therefore we have to scroll down more
rows to check the output and the only way to see the better output is the
inspector whereas in Pharo 3.0 we saw that the output depended on the size
of the workspace.