[Pharo-dev] Importing a GNU Smalltalk project into Pharo

Very interesting question, especially since we want people to move to Pharo. http://stackoverflow.com/questions/37690985/importing-a-gnu-smalltalk-project-into-pharo Cheers, Max

Re: [Pharo-dev] Do we want AST-Debugger?

Hi Denis, On Mon, Jun 6, 2016 at 1:45 AM, Denis Kudriashov wrote: > Hi Eliot. > > 2016-06-06 1:13 GMT+02:00 Eliot Miranda : > >> That's simply not true. In fact the amount known of the VM in both the >> bytecode debugger and the AST debugger is

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

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

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

[Pharo-dev] [pharo-project/pharo-core] 0d38cd: 60068

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 0d38cdebda872a2ab4016524f089ee578b99319e https://github.com/pharo-project/pharo-core/commit/0d38cdebda872a2ab4016524f089ee578b99319e Author: Jenkins Build Server Date:

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

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

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] [ANN] Ephemeron Support is Ready

<3 > On 07 Jun 2016, at 11:32, Guille Polito wrote: > > Hi All, > > Since this morning, in Pharo #60065, Ephemeron support is in the image. Most > of the changes are infrastructural, so far transparent for the users. It is > important to notice that even while the

Re: [Pharo-dev] GT-Spotter dive in shortcut

For coherence, the vast majority of shortcuts should follow the standard in all applications. Most shortcuts use cmd in mac, and ctrl in unix/win. Then there are exceptions of course. I'd like exceptions to be that, exceptions, and well documented. I'm not against using #alt for particular

Re: [Pharo-dev] GT-Spotter dive in shortcut

2016-06-07 16:12 GMT+02:00 Andrei Chis : > We can, but I remember there were some discussions and it was decided to > use meta everywhere. > but using meta everywhere does not help if there are conflicts with other shortcuts. > > Cheers, > Andrei > > On Tue, Jun 7,

Re: [Pharo-dev] GT-Spotter dive in shortcut

We can, but I remember there were some discussions and it was decided to use meta everywhere. Cheers, Andrei On Tue, Jun 7, 2016 at 3:49 PM, Nicolai Hess wrote: > > > 2016-06-07 15:08 GMT+02:00 Andrei Chis : > >> During Pharo 5 most shortcuts

Re: [Pharo-dev] GT-Spotter dive in shortcut

2016-06-07 15:08 GMT+02:00 Andrei Chis : > During Pharo 5 most shortcuts from tools were changed to use "meta" > instead of cmd. > > Cheers, > Andrei > Can we change this for spotter ? cmd instead of meta ctrl left/right is often used for text components to move to

Re: [Pharo-dev] GT-Spotter dive in shortcut

During Pharo 5 most shortcuts from tools were changed to use "meta" instead of cmd. Cheers, Andrei On Tue, Jun 7, 2016 at 2:18 PM, Nicolai Hess wrote: > > > 2016-06-07 13:57 GMT+02:00 Nicolai Hess : > >> >> Am 07.06.2016 1:56 nachm. schrieb "Henrik

Re: [Pharo-dev] GLMPresentation >> window looks strange

And this is not only place. I saw it is common approach to get view from GL presentation. And it makes code analysis so hard. 2016-06-07 10:54 GMT+02:00 Guille Polito : > Hi! > > We were browsing with Steph users of #announce: and we arrived to the > following method:

Re: [Pharo-dev] GT-Spotter dive in shortcut

2016-06-07 13:57 GMT+02:00 Nicolai Hess : > > Am 07.06.2016 1:56 nachm. schrieb "Henrik Nergaard" < > henrik.nerga...@uia.no>: > > > > IIRC the shortcut is not changed, it still is meta+right(+shift). Only > the tooltip was changed to display the system specific key instead

Re: [Pharo-dev] GT-Spotter dive in shortcut

Am 07.06.2016 1:56 nachm. schrieb "Henrik Nergaard" : > > IIRC the shortcut is not changed, it still is meta+right(+shift). Only the tooltip was changed to display the system specific key instead of “cmd” so for Windows/Linux this would be “ctrl”. No, it changed > > > >

Re: [Pharo-dev] GT-Spotter dive in shortcut

IIRC the shortcut is not changed, it still is meta+right(+shift). Only the tooltip was changed to display the system specific key instead of “cmd” so for Windows/Linux this would be “ctrl”. Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Nicolai

Re: [Pharo-dev] GT-Spotter dive in shortcut

is most probably an error :S > On 07 Jun 2016, at 12:55, Nicolai Hess wrote: > > Why did the shortcut for dive-in element/category changed from > cmd+right > cmd+shift+right > > to > > ctrl+right > ctrl+shift+right > > I know there were some discussions about this and

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

[Pharo-dev] GT-Spotter dive in shortcut

Why did the shortcut for dive-in element/category changed from cmd+right cmd+shift+right to ctrl+right ctrl+shift+right I know there were some discussions about this and that the behavior changed some time ago, but I don't know the rational behind this. thanks nicolai

[Pharo-dev] [pharo-project/pharo-core] 092dbb: 60067

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 092dbb81541495f197593e5877cd011ea655c6c1 https://github.com/pharo-project/pharo-core/commit/092dbb81541495f197593e5877cd011ea655c6c1 Author: Jenkins Build Server Date:

Re: [Pharo-dev] Privacy sendDiagnosticsAndUsageData should be ternary, not binary

Hi Peter, On Tue, Jun 7, 2016 at 12:05 AM, Peter Uhnak wrote: > Hi, > > Privacy>>sendDiagnosticsAndUsageData should be ternary, not binary. > > Because right now if I refuse sending the data I will be asked again every > single time. > Indeed right now, at least in Spotter,

[Pharo-dev] [ANN] Ephemeron Support is Ready

Hi All, Since this morning, in Pharo #60065, Ephemeron support is in the image. Most of the changes are infrastructural, so far transparent for the users. It is important to notice that even while the support is there, it is not enabled by default. Also, this required changes in the virtual

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

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

[Pharo-dev] [pharo-project/pharo-core] 70dc7b: 60066

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 70dc7b60e66385b0ffddd34338941c2c864f4314 https://github.com/pharo-project/pharo-core/commit/70dc7b60e66385b0ffddd34338941c2c864f4314 Author: Jenkins Build Server Date:

[Pharo-dev] GLMPresentation >> window looks strange

Hi! We were browsing with Steph users of #announce: and we arrived to the following method: GLMPresentation >> window self announce: (GLMWindowRequest new action: [ :aWindow | ^ aWindow ]). ^ nil And we could not stop noticing that, while the announcement, probably

[Pharo-dev] [pharo-project/pharo-core] c03d19: 60065

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c03d194384c8d581f6edf9ff72723b12c2277c00 https://github.com/pharo-project/pharo-core/commit/c03d194384c8d581f6edf9ff72723b12c2277c00 Author: Jenkins Build Server Date:

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

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

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

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

[Pharo-dev] [pharo-project/pharo-core] 1838ea: 60064

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 1838ea43bf2a0d7d0c6e5f552f2d295d96b4d359 https://github.com/pharo-project/pharo-core/commit/1838ea43bf2a0d7d0c6e5f552f2d295d96b4d359 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core] 33ed32: 60063

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 33ed32f27e6dee56c7b9df21ebb2ee1ec0392407 https://github.com/pharo-project/pharo-core/commit/33ed32f27e6dee56c7b9df21ebb2ee1ec0392407 Author: Jenkins Build Server Date:

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

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

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