[Pharo-dev] [ANN] EventRecorder updated (import/export)

[Torsten Bergmann]

Hi,

I forgot to mention that for "EventRecorder" there was another
pass on the code together with Peter Uhnak.

It is now possible to import/export the recordings again and also the
UI was updated accordingly (see attached screenshot)

Works in Pharo 5.0 - you can load the tool from Catalog or by opening
Spotter and entering "EventRecorder".

Have fun
T.

Re: [Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

[stepharo]

May be it works for millions people.

So we can add EXTRA bindings to be compatible for them but I have 
something else to do that to learn


and use keys that can be removed from my keyboard.

For me there are to control volume output and nothing else.


Stef


Le 19/4/16 à 22:49, p...@highoctane.be a écrit :



On Tue, Apr 19, 2016 at 8:38 PM, Eliot Miranda 
> wrote:

>
>
>
> On Tue, Apr 19, 2016 at 6:52 AM, stepharo > wrote:

>>
>> This F keys suck!
>
>
> +1.  How do you remember which F key does what in the Debugger?  F10 
- fix my code to be a perfect 10??

>
Yeah, sure.

Visual Studio is standardized on that an millions of people are using it.
https://msdn.microsoft.com/en-us/library/aa239052%28v=vs.60%29.aspx?f=255=-2147217396

Same for PhpStorm, WebStorm, and Intellij IDEA, also used by millions.
Talk about keymaps: check this --> 
https://www.jetbrains.com/help/phpstorm/2016.1/function-keys.html?origin=old_help

(note the dropdown on the top right).

Let's talk Chrome devtools (just a litte user base of millions as well):

F8 -> Run
F10 -> Step over
F11 -> Step into

Let's talk Firefox (okay, a tad less users)

https://developer.mozilla.org/en-US/docs/Tools/Debugger/Keyboard_shortcuts

Resume execution when at a breakpoint F8
Step over F10
Step into F11
Step out Shift + F11

CodeBlocks IDE
http://wiki.codeblocks.org/index.php/Keyboard_Shortcuts

Debug

Function Shortcut Key
Debug F8
Continue debugging Ctrl + F7
Step over a code block F7
Step into a code block Shift + F7
Step out of a code block Ctrl + Shift + F7
Toggle breakpoint F5
Run to cursor F4
Previous error Alt + F1
Next error Alt + F2

Vim plugins for debugging Ruby:

You may find useful to override default shortcut commands by F5-F8 
shortcuts. Add these to your .vimrc:


  map   :call g:RubyDebugger.step()
  map   :call g:RubyDebugger.next()
  map   :call g:RubyDebugger.continue()

Even SAP uses F keys for that.


f5->step by step
f6->to skip the statements like perform,module,..
f7->to come out from the form,module,..
f8->run upto the cursor or run completely

R studio:

Toggle Breakpoint Shift+F9
Execute Next Line F10
Step Into Function Shift+F4
Finish Function/Loop Shift+F6
Continue Shift+F5
Stop Debugging Shift+F8


Delphi:

F4 Run program to current cursor position
F5 Toggle breakpoint
F7 Debugger step into
Shift - F7 Trace into next source line
F8 Debugger step over
Shift - F8 Run until return
F9 Run program under debugger


ActiveState Komodo IDE:

Step In F11
Step Over F10
Step Out Shift-F11
Start F5

CodeLite

Start/continue debugger F5
Step Into F11
Next F10
Step Out Shift-F11

Dolphin X6

Go F5
Step Into F11
Step Over F10
Step Out Shift-F11
Run to cursor Ctl-F10
Run Ctl-F5
Restart Ctl-Shift-F5

Toad debugger for PL/SQL

F11
Run (continue execution)
F12
Run to cursor
SHIFT+F5
Set or delete a breakpoint on the current line
SHIFT+F7
Trace into
SHIFT+F8
Step over
SHIFT+F10
Trace out

Visualworks debugger

Step Into: F5
Step: F6
Step Over: F7
Run: F9

World+dog uses F keys for debugging.

But Pharo? Nah!

We have a great debugger? Sure let's hide it under absconse shortcuts 
that only we know.


New debugger is nicer looking but more painful to use and I never used 
any shortcut on it as they aren't those standard things.


Anyway, I should be able to hack that the way I want, so, no real issue.

Remember, first impressions count.
This is a key one if we put "programming in the debugger" as a strong 
point of the environment.


Ok on a Mac, F keys do involve a 'Fn' press because they are hidden 
under volume, brightness etc.
So, on a Mac, that is more sucky than on Unix or Windows. Sure. 
There's a system preference to switch to normal.


I'll get a hotmilk and a walk now. Need to calm down. "Functions keys 
do suck" What ?!


Phil


>>
>>
>> Stef
>>
>> Le 17/4/16 18:00, Ben Coman a écrit :
>>
>>> Interesting. A search turned up... Quick Tip Debugger Shortcut Key 
Reference

>>> http://www.mularien.com/blog/category/eclipse/
>>>
>>> cheers -ben
>>>
>>> On Sun, Apr 17, 2016 at 11:15 PM, philippe.b...@highoctane.be 


>>> > wrote:

 Most of the world IDE use function keys for debugging.

 Additional benefit: easier for newcomers to use it.

 Having the buttons on the top is a pain as the code pane is at 
the bottom

 and requires travels all the time.

 Phil

 On Apr 17, 2016 4:57 PM, "Peter Uhnák" > wrote:

>
> Well, I've added a startup script for myself... but it would be 
nice to

> have it everywhere by default in some variant...
>
> ~~
> StartupPreferencesLoader default executeAtomicItems: {
> StartupAction
> name: 'Change debugger labels & shortcuts'
> code: [
> 

Re: [Pharo-dev] About PharoInProgress book

[Esteban A. Maringolo]

Thanks Damien! It is working again.

https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/101/changes
Esteban A. Maringolo


2016-05-03 15:17 GMT-03:00 Damien Pollet :
> I did the migration, now waiting for the CI to run a build. On my machine it
> looked fine.
>
> SBAbook is a LaTeX class I made for the Pharo books, that's what defines the
> new look of e.g. Enterprise Pharo
>
> On 3 May 2016 at 19:43, Esteban A. Maringolo  wrote:
>>
>> Hi Damien,
>>
>> Sorry, I don't know what SBABook is :)
>> Who maintains the CI?  Is it easily fixable?
>>
>> I could get TeX running locally following your advice, so I can build
>> the book's PDFs on my own machine. I guess doing the same on the build
>> slave should be as straightforward as that.
>>
>> Regards!
>> Esteban A. Maringolo
>>
>>
>> 2016-05-03 9:01 GMT-03:00 Damien Pollet :
>> > The interns updated the stable release of Pillar; there is a mention of
>> > the
>> > listings package in the log, which suggests that pillar outputs TeX code
>> > for
>> > the new sbabook class instead of the old one. That should be fixable by
>> > finding the correct version of Pillar to use, but the correct long-term
>> > fix
>> > is to migrate to sbabook.
>> >
>> > On 27 April 2016 at 22:28, Esteban A. Maringolo 
>> > wrote:
>> >>
>> >> I sent an email this morning about this issue, apparently it has to do
>> >> with a missing font.
>> >>
>> >> Esteban A. Maringolo
>> >>
>> >>
>> >> 2016-04-27 16:50 GMT-03:00 stepharo :
>> >> > Hi
>> >> >
>> >> > I tried to fix the build on jenkins but I failed. I do not know how
>> >> > to
>> >> > fix
>> >> > it.
>> >> >
>> >> > I do not know how to fix. Probably the changes in Pillar broke it.
>> >> >
>> >> > Now since Damien will quit our team, I wonder what will be the future
>> >> > of
>> >> > pillar, may be markdown and for me LaTeX
>> >> >
>> >> > Stef
>> >> >
>> >> >
>> >> >
>> >> > ./AWS.tex:40: LaTeX Error: Environment listing undefined.
>> >> >
>> >> > See the LaTeX manual or LaTeX Companion for explanation.
>> >> > Type  H   for immediate help.
>> >> > ...
>> >> >
>> >> > l.40 \begin{listing}
>> >> >  [language=smalltalk]
>> >> > Your command was ignored.
>> >> > Type  Ito replace it with another command,
>> >> > orto continue without it.
>> >> >
>> >> >
>> >> > ./AWS.tex:53: LaTeX Error: \begin{document} ended by \end{listing}.
>> >> >
>> >> > See the LaTeX manual or LaTeX Companion for explanation.
>> >> > Type  H   for immediate help.
>> >> > ...
>> >> >
>> >> > l.53 \end{listing}
>> >> >
>> >> > Your command was ignored.
>> >> > Type  Ito replace it with another command,
>> >> > orto continue without it.
>> >> >
>> >> > No file AWS.bbl.
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Damien Pollet
>> > type less, do more [ | ] http://people.untyped.org/damien.pollet
>>
>
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] About PharoInProgress book

[Damien Pollet]

I did the migration, now waiting for the CI to run a build. On my machine
it looked fine.

SBAbook is a LaTeX class I made for the Pharo books, that's what defines
the new look of e.g. Enterprise Pharo

On 3 May 2016 at 19:43, Esteban A. Maringolo  wrote:

> Hi Damien,
>
> Sorry, I don't know what SBABook is :)
> Who maintains the CI?  Is it easily fixable?
>
> I could get TeX running locally following your advice, so I can build
> the book's PDFs on my own machine. I guess doing the same on the build
> slave should be as straightforward as that.
>
> Regards!
> Esteban A. Maringolo
>
>
> 2016-05-03 9:01 GMT-03:00 Damien Pollet :
> > The interns updated the stable release of Pillar; there is a mention of
> the
> > listings package in the log, which suggests that pillar outputs TeX code
> for
> > the new sbabook class instead of the old one. That should be fixable by
> > finding the correct version of Pillar to use, but the correct long-term
> fix
> > is to migrate to sbabook.
> >
> > On 27 April 2016 at 22:28, Esteban A. Maringolo 
> > wrote:
> >>
> >> I sent an email this morning about this issue, apparently it has to do
> >> with a missing font.
> >>
> >> Esteban A. Maringolo
> >>
> >>
> >> 2016-04-27 16:50 GMT-03:00 stepharo :
> >> > Hi
> >> >
> >> > I tried to fix the build on jenkins but I failed. I do not know how to
> >> > fix
> >> > it.
> >> >
> >> > I do not know how to fix. Probably the changes in Pillar broke it.
> >> >
> >> > Now since Damien will quit our team, I wonder what will be the future
> of
> >> > pillar, may be markdown and for me LaTeX
> >> >
> >> > Stef
> >> >
> >> >
> >> >
> >> > ./AWS.tex:40: LaTeX Error: Environment listing undefined.
> >> >
> >> > See the LaTeX manual or LaTeX Companion for explanation.
> >> > Type  H   for immediate help.
> >> > ...
> >> >
> >> > l.40 \begin{listing}
> >> >  [language=smalltalk]
> >> > Your command was ignored.
> >> > Type  Ito replace it with another command,
> >> > orto continue without it.
> >> >
> >> >
> >> > ./AWS.tex:53: LaTeX Error: \begin{document} ended by \end{listing}.
> >> >
> >> > See the LaTeX manual or LaTeX Companion for explanation.
> >> > Type  H   for immediate help.
> >> > ...
> >> >
> >> > l.53 \end{listing}
> >> >
> >> > Your command was ignored.
> >> > Type  Ito replace it with another command,
> >> > orto continue without it.
> >> >
> >> > No file AWS.bbl.
> >> >
> >> >
> >>
> >
> >
> >
> > --
> > Damien Pollet
> > type less, do more [ | ] http://people.untyped.org/damien.pollet
>
>


-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] About PharoInProgress book

[Esteban A. Maringolo]

Hi Damien,

Sorry, I don't know what SBABook is :)
Who maintains the CI?  Is it easily fixable?

I could get TeX running locally following your advice, so I can build
the book's PDFs on my own machine. I guess doing the same on the build
slave should be as straightforward as that.

Regards!
Esteban A. Maringolo


2016-05-03 9:01 GMT-03:00 Damien Pollet :
> The interns updated the stable release of Pillar; there is a mention of the
> listings package in the log, which suggests that pillar outputs TeX code for
> the new sbabook class instead of the old one. That should be fixable by
> finding the correct version of Pillar to use, but the correct long-term fix
> is to migrate to sbabook.
>
> On 27 April 2016 at 22:28, Esteban A. Maringolo 
> wrote:
>>
>> I sent an email this morning about this issue, apparently it has to do
>> with a missing font.
>>
>> Esteban A. Maringolo
>>
>>
>> 2016-04-27 16:50 GMT-03:00 stepharo :
>> > Hi
>> >
>> > I tried to fix the build on jenkins but I failed. I do not know how to
>> > fix
>> > it.
>> >
>> > I do not know how to fix. Probably the changes in Pillar broke it.
>> >
>> > Now since Damien will quit our team, I wonder what will be the future of
>> > pillar, may be markdown and for me LaTeX
>> >
>> > Stef
>> >
>> >
>> >
>> > ./AWS.tex:40: LaTeX Error: Environment listing undefined.
>> >
>> > See the LaTeX manual or LaTeX Companion for explanation.
>> > Type  H   for immediate help.
>> > ...
>> >
>> > l.40 \begin{listing}
>> >  [language=smalltalk]
>> > Your command was ignored.
>> > Type  Ito replace it with another command,
>> > orto continue without it.
>> >
>> >
>> > ./AWS.tex:53: LaTeX Error: \begin{document} ended by \end{listing}.
>> >
>> > See the LaTeX manual or LaTeX Companion for explanation.
>> > Type  H   for immediate help.
>> > ...
>> >
>> > l.53 \end{listing}
>> >
>> > Your command was ignored.
>> > Type  Ito replace it with another command,
>> > orto continue without it.
>> >
>> > No file AWS.bbl.
>> >
>> >
>>
>
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Denis Kudriashov]

+1

2016-05-03 14:41 GMT+02:00 Peter Uhnák :

>
>
> On Tue, May 3, 2016 at 1:56 PM, Nicolai Hess 
> wrote:
>
>>
>>
>> 2016-05-03 13:26 GMT+02:00 Andrei Chis :
>>
>>>
>>>
>>> On Tue, May 3, 2016 at 10:26 AM, Peter Uhnák  wrote:
>>>
 the conclusion was to print the result on the next line.
>

 Well this isn't true for the last line.

>>>
>>> Yes, right now it only inserts it on the new line if there is a line.
>>>
>>>

 The problem isn't just that it prints on the next line for the
 intermediate results, but that it puts it before the next content.
 Even if it was on a line of it's own it would be much better.

>>>
>>> We could change it to always insert a new line and add the printed
>>> content to that line.
>>> But should it add an extra line if there already exists an empty line
>>> bellow?
>>>
>>
>> I would change it to "always print on the same line"
>>
>
> +1
>

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Peter Uhnák]

On Tue, May 3, 2016 at 1:56 PM, Nicolai Hess  wrote:

>
>
> 2016-05-03 13:26 GMT+02:00 Andrei Chis :
>
>>
>>
>> On Tue, May 3, 2016 at 10:26 AM, Peter Uhnák  wrote:
>>
>>> the conclusion was to print the result on the next line.

>>>
>>> Well this isn't true for the last line.
>>>
>>
>> Yes, right now it only inserts it on the new line if there is a line.
>>
>>
>>>
>>> The problem isn't just that it prints on the next line for the
>>> intermediate results, but that it puts it before the next content.
>>> Even if it was on a line of it's own it would be much better.
>>>
>>
>> We could change it to always insert a new line and add the printed
>> content to that line.
>> But should it add an extra line if there already exists an empty line
>> bellow?
>>
>
> I would change it to "always print on the same line"
>

+1

Re: [Pharo-dev] About PharoInProgress book

[Damien Pollet]

See https://github.com/SquareBracketAssociates/PharoInProgress/issues/24

On 3 May 2016 at 14:01, Damien Pollet  wrote:

> The interns updated the stable release of Pillar; there is a mention of
> the listings package in the log, which suggests that pillar outputs TeX
> code for the new sbabook class instead of the old one. That should be
> fixable by finding the correct version of Pillar to use, but the correct
> long-term fix is to migrate to sbabook.
>
> On 27 April 2016 at 22:28, Esteban A. Maringolo 
> wrote:
>
>> I sent an email this morning about this issue, apparently it has to do
>> with a missing font.
>>
>> Esteban A. Maringolo
>>
>>
>> 2016-04-27 16:50 GMT-03:00 stepharo :
>> > Hi
>> >
>> > I tried to fix the build on jenkins but I failed. I do not know how to
>> fix
>> > it.
>> >
>> > I do not know how to fix. Probably the changes in Pillar broke it.
>> >
>> > Now since Damien will quit our team, I wonder what will be the future of
>> > pillar, may be markdown and for me LaTeX
>> >
>> > Stef
>> >
>> >
>> >
>> > ./AWS.tex:40: LaTeX Error: Environment listing undefined.
>> >
>> > See the LaTeX manual or LaTeX Companion for explanation.
>> > Type  H   for immediate help.
>> > ...
>> >
>> > l.40 \begin{listing}
>> >  [language=smalltalk]
>> > Your command was ignored.
>> > Type  Ito replace it with another command,
>> > orto continue without it.
>> >
>> >
>> > ./AWS.tex:53: LaTeX Error: \begin{document} ended by \end{listing}.
>> >
>> > See the LaTeX manual or LaTeX Companion for explanation.
>> > Type  H   for immediate help.
>> > ...
>> >
>> > l.53 \end{listing}
>> >
>> > Your command was ignored.
>> > Type  Ito replace it with another command,
>> > orto continue without it.
>> >
>> > No file AWS.bbl.
>> >
>> >
>>
>>
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet
>



-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] About PharoInProgress book

[Damien Pollet]

The interns updated the stable release of Pillar; there is a mention of the
listings package in the log, which suggests that pillar outputs TeX code
for the new sbabook class instead of the old one. That should be fixable by
finding the correct version of Pillar to use, but the correct long-term fix
is to migrate to sbabook.

On 27 April 2016 at 22:28, Esteban A. Maringolo 
wrote:

> I sent an email this morning about this issue, apparently it has to do
> with a missing font.
>
> Esteban A. Maringolo
>
>
> 2016-04-27 16:50 GMT-03:00 stepharo :
> > Hi
> >
> > I tried to fix the build on jenkins but I failed. I do not know how to
> fix
> > it.
> >
> > I do not know how to fix. Probably the changes in Pillar broke it.
> >
> > Now since Damien will quit our team, I wonder what will be the future of
> > pillar, may be markdown and for me LaTeX
> >
> > Stef
> >
> >
> >
> > ./AWS.tex:40: LaTeX Error: Environment listing undefined.
> >
> > See the LaTeX manual or LaTeX Companion for explanation.
> > Type  H   for immediate help.
> > ...
> >
> > l.40 \begin{listing}
> >  [language=smalltalk]
> > Your command was ignored.
> > Type  Ito replace it with another command,
> > orto continue without it.
> >
> >
> > ./AWS.tex:53: LaTeX Error: \begin{document} ended by \end{listing}.
> >
> > See the LaTeX manual or LaTeX Companion for explanation.
> > Type  H   for immediate help.
> > ...
> >
> > l.53 \end{listing}
> >
> > Your command was ignored.
> > Type  Ito replace it with another command,
> > orto continue without it.
> >
> > No file AWS.bbl.
> >
> >
>
>


-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Nicolai Hess]

2016-05-03 13:26 GMT+02:00 Andrei Chis :

>
>
> On Tue, May 3, 2016 at 10:26 AM, Peter Uhnák  wrote:
>
>> the conclusion was to print the result on the next line.
>>>
>>
>> Well this isn't true for the last line.
>>
>
> Yes, right now it only inserts it on the new line if there is a line.
>
>
>>
>> The problem isn't just that it prints on the next line for the
>> intermediate results, but that it puts it before the next content.
>> Even if it was on a line of it's own it would be much better.
>>
>
> We could change it to always insert a new line and add the printed content
> to that line.
> But should it add an extra line if there already exists an empty line
> bellow?
>

I would change it to "always print on the same line"


>
> Andrei
>
>
>>
>> Peter
>>
>
>

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Andrei Chis]

On Tue, May 3, 2016 at 10:26 AM, Peter Uhnák  wrote:

> the conclusion was to print the result on the next line.
>>
>
> Well this isn't true for the last line.
>

Yes, right now it only inserts it on the new line if there is a line.


>
> The problem isn't just that it prints on the next line for the
> intermediate results, but that it puts it before the next content.
> Even if it was on a line of it's own it would be much better.
>

We could change it to always insert a new line and add the printed content
to that line.
But should it add an extra line if there already exists an empty line
bellow?

Andrei


>
> Peter
>

Re: [Pharo-dev] Paginated list view in GTInspector

[Denis Kudriashov]

2016-05-03 11:49 GMT+02:00 Tudor Girba :

> Yes, it is planned.


Perfect :) Thank's

Re: [Pharo-dev] Paginated list view in GTInspector

[Tudor Girba]

Yes, it is planned.

Cheers,
Doru


> On May 3, 2016, at 10:44 AM, Denis Kudriashov  wrote:
> 
> Hi.
> 
> Does FastTable will replace paginated list view in GTinspector? Is it planned?

--
www.tudorgirba.com
www.feenk.com

"Be rather willing to give than demanding to get."

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50748
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 408e40: 50748

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 408e4008df4a4e305c44347e2f3c44df3ea1350d
  
https://github.com/pharo-project/pharo-core/commit/408e4008df4a4e305c44347e2f3c44df3ea1350d
  Author: Jenkins Build Server 
  Date:   2016-05-03 (Tue, 03 May 2016)

  Changed paths:
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50747.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50748.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50747.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50748.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
A System-Localization.package/Locale.class/class/accessing/current.st
R 
System-Localization.package/Locale.class/class/instance-creation/current.st
R System-Localization.package/Locale.class/instance/accessing/country.st
R System-Localization.package/Locale.class/instance/accessing/encoder.st
R System-Localization.package/Locale.class/instance/accessing/language.st
M System-Localization.package/Locale.class/instance/printing/printOn_.st

  Log Message:
  ---
  50748
18156 restore all notifications for SystemAnnouncer 
https://pharo.fogbugz.com/f/cases/18156

18076 Locale broken
https://pharo.fogbugz.com/f/cases/18076

http://files.pharo.org/image/50/50748.zip

[Pharo-dev] [pharo-project/pharo-core] 3f8755: 50747

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 3f875585d1f8aea04c53a5c54bf2203356b5ac4a
  
https://github.com/pharo-project/pharo-core/commit/3f875585d1f8aea04c53a5c54bf2203356b5ac4a
  Author: Jenkins Build Server 
  Date:   2016-05-03 (Tue, 03 May 2016)

  Changed paths:
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50746.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50747.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50746.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50747.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
M 
System-OSEnvironments.package/OSEnvironment.class/instance/private/getEnv_.st

  Log Message:
  ---
  50747
18139 getenv() call on Ubuntu 14.04 (32 bit) fails in one-click image
https://pharo.fogbugz.com/f/cases/18139

http://files.pharo.org/image/50/50747.zip

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50747
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50746
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 619a43: 50746

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 619a43cc29c4db74eef442e345c6ecc5cbcc3b8e
  
https://github.com/pharo-project/pharo-core/commit/619a43cc29c4db74eef442e345c6ecc5cbcc3b8e
  Author: Jenkins Build Server 
  Date:   2016-05-03 (Tue, 03 May 2016)

  Changed paths:
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50745.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50746.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50745.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50746.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  50746
18150 AST-FFI-Pharo50Compatibility-EstebanLorenzano.1.mcz missing
https://pharo.fogbugz.com/f/cases/18150/

http://files.pharo.org/image/50/50746.zip

[Pharo-dev] Paginated list view in GTInspector

[Denis Kudriashov]

Hi.

Does FastTable will replace paginated list view in GTinspector? Is it
planned?

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Peter Uhnák]

>
> the conclusion was to print the result on the next line.
>

Well this isn't true for the last line.

The problem isn't just that it prints on the next line for the intermediate
results, but that it puts it before the next content.
Even if it was on a line of it's own it would be much better.

Peter

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Andrei Chis]

Hi Pavel,

>From what I remember there were some discussions last year when we added
this feature and the conclusion was to print the result on the next line.
Maybe we can find a better heuristic for placing the result.

Cheers,
Andrei

On Tue, May 3, 2016 at 9:44 AM, Pavel Krivanek 
wrote:

> Andrei,
>
> what is the reason for placing print-it result alway at the end of line?
> See atEndOfLineInsertAndSelect:.
>
> Cheers,
> -- Pavel
>
>
> 2016-05-03 9:27 GMT+02:00 Peter Uhnák :
>
>> Hi,
>>
>> currently when you print the last statement in the playground and press
>> enter (to insert the comment into the playground) it outputs it after,
>> which is good.
>>
>> However if I then go back and evaluate a line above, it places the output
>> on the _next_ line, just before the next statement, which is quite annoying.
>>
>>
>>
>>
>> ​
>> Can this be changed, so it keeps it in line like this?
>>
>>
>> ​
>> Thanks,
>> Peter
>>
>
>

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Pavel Krivanek]

ehm, always

2016-05-03 9:44 GMT+02:00 Pavel Krivanek :

> Andrei,
>
> what is the reason for placing print-it result alway at the end of line?
> See atEndOfLineInsertAndSelect:.
>
> Cheers,
> -- Pavel
>
>
> 2016-05-03 9:27 GMT+02:00 Peter Uhnák :
>
>> Hi,
>>
>> currently when you print the last statement in the playground and press
>> enter (to insert the comment into the playground) it outputs it after,
>> which is good.
>>
>> However if I then go back and evaluate a line above, it places the output
>> on the _next_ line, just before the next statement, which is quite annoying.
>>
>>
>>
>>
>> ​
>> Can this be changed, so it keeps it in line like this?
>>
>>
>> ​
>> Thanks,
>> Peter
>>
>
>

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

[Pavel Krivanek]

Andrei,

what is the reason for placing print-it result alway at the end of line?
See atEndOfLineInsertAndSelect:.

Cheers,
-- Pavel


2016-05-03 9:27 GMT+02:00 Peter Uhnák :

> Hi,
>
> currently when you print the last statement in the playground and press
> enter (to insert the comment into the playground) it outputs it after,
> which is good.
>
> However if I then go back and evaluate a line above, it places the output
> on the _next_ line, just before the next statement, which is quite annoying.
>
>
>
>
> ​
> Can this be changed, so it keeps it in line like this?
>
>
> ​
> Thanks,
> Peter
>

[Pharo-dev] Keep print-it output on the same line in GTPlayground

[Peter Uhnák]

Hi,

currently when you print the last statement in the playground and press
enter (to insert the comment into the playground) it outputs it after,
which is good.

However if I then go back and evaluate a line above, it places the output
on the _next_ line, just before the next statement, which is quite annoying.




​
Can this be changed, so it keeps it in line like this?


​
Thanks,
Peter