[Pharo-dev] Language Server Protocol

Just a very brief thought, to wonder being a Language Server Protocol client might be a path to polygot programming in Pharo. Or if providing a LSP server might be a bridge-head for Pharo to be integrated into larger projects. * http://langserver.org/ *

Re: [Pharo-dev] Pharo 60 needs help because Removing-a-package-with-extensions-let-the-extensions-in-the-system-and-break-their-reload

Super tx guille!!! On Tue, Feb 7, 2017 at 12:18 PM, Guillermo Polito wrote: > I proposed a slice in the inbox for this. > > - added RPackage>>removeFromSystem > - this version removes defined classes and also extension methods > defined in the package. > - make

Re: [Pharo-dev] [QA] Debugger buttons explained

As we are here, what are your best proposals for these buttons: Full stack Run to here Where is? Le 06/02/2017 à 21:25, Sean P. DeNigris a écrit : > How about... -- Dr. Geo http://drgeo.eu

Re: [Pharo-dev] [QA] Debugger buttons explained

ok got it! Le 07/02/2017 à 20:49, Andrei Chis a écrit : > Seems that I made a small mistake before. > DebugAction>>#asMenuRegistrationIn: is called only when creating the > context menu. > SpecDebuggerDynamicToolbar is the class that builds the toolbar with the > step buttons. Then each button

Re: [Pharo-dev] [QA] Debugger buttons explained

Seems that I made a small mistake before. DebugAction>>#asMenuRegistrationIn: is called only when creating the context menu. SpecDebuggerDynamicToolbar is the class that builds the toolbar with the step buttons. Then each button will be an instance of SpecDebugActionButton. Andrei On Tue, Feb

Re: [Pharo-dev] [QA] Debugger buttons explained

Changed to the SpecDebugger in the method mentionned bellow does not have action on newly debuggin session with SpecDebugger. This method is not call. Any idea? Le 06/02/2017 à 21:57, Andrei Chis a écrit : > For the Spec interface of the debugger you need to adapt >

Re: [Pharo-dev] [QA] Debugger buttons explained

Ok thanks for the tips. As labes was use as tooltip too I have to set the balloon text as bellow which is not great but should help for the transition. setBalloonText: ((anAction help ifNil: [ anAction title]) , Character tab asString , anAction shortcutAsString) trimBoth; I will look at the

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

cool. thx. On Tue, Feb 7, 2017 at 10:46 PM, Andrei Chis wrote: > Done. > > Cheers, > Andrei > > On Tue, Feb 7, 2017 at 1:35 PM, Ben Coman wrote: > >> On Tue, Feb 7, 2017 at 8:00 PM, Andrei Chis >> wrote: >> > >> >

[Pharo-dev] Debugging "1 ifTrue: [2]" (was Re: Debugger hang when step throught)

On Tue, Feb 7, 2017 at 5:35 PM, Denis Kudriashov wrote: > Also I found another funny issue. Try debugIt following expression: > > 1 ifTrue: [2]. > > You will be wondering that debugger will not able to open. To quickly get to the point to observe the cause, you can

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

Done. Cheers, Andrei On Tue, Feb 7, 2017 at 1:35 PM, Ben Coman wrote: > On Tue, Feb 7, 2017 at 8:00 PM, Andrei Chis > wrote: > > > > > > On Sat, Feb 4, 2017 at 4:40 PM, Ben Coman wrote: > >> > >> > >> > On Fri, Feb 3,

[Pharo-dev] [pharo-project/pharo-core] 240c87: 60378

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

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

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

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

On Tue, Feb 7, 2017 at 8:00 PM, Andrei Chis wrote: > > > On Sat, Feb 4, 2017 at 4:40 PM, Ben Coman wrote: >> >> >> > On Fri, Feb 3, 2017 at 3:13 AM, Ben Coman wrote: >> >> >> >> Just curious what the magic numbers here

Re: [Pharo-dev] Debugger hang when step throught

I regularly got hit by this kind of lockup. Do not know exactly why it locks up but then it is "kill pharo" "recover changes" and "change sorter" fun session... Got one an hour ago, drives me up the wall. It is one of the reasons that made me add the Save with Timetag feature. [image: Inline

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

On Sat, Feb 4, 2017 at 4:40 PM, Ben Coman wrote: > > > On Fri, Feb 3, 2017 at 3:13 AM, Ben Coman wrote: > >> > >> Just curious what the magic numbers here relate to... > >> and can they be factored out to a meaningful method name? > >> > >>

Re: [Pharo-dev] Pharo 60 needs help because Removing-a-package-with-extensions-let-the-extensions-in-the-system-and-break-their-reload

I proposed a slice in the inbox for this. - added RPackage>>removeFromSystem - this version removes defined classes and also extension methods defined in the package. - make Nautilus ask the RPackage to remove itself (instead of doing it in the UI) I tested it with the fileout of a package

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

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

[Pharo-dev] [pharo-project/pharo-core] ab7ee8: 60377

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

Re: [Pharo-dev] Esteban's ChangeLog week of 30 January 2017

I love such reports :) I like when I have smart ideas that work :) On Mon, Feb 6, 2017 at 4:54 PM, Sean P. DeNigris wrote: > EstebanLM wrote > > This is my weekly ChangeLog, from 30 January 2017 to 5 February 2017. > > Go, go, go, Esteban!!! > > > EstebanLM wrote > > the

Re: [Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

Ok let us close the bug entry. One less to go. Stef On Tue, Feb 7, 2017 at 11:24 AM, Guillermo Polito wrote: > I back up Pavel and Esteban here. > > On Tue, Feb 7, 2017 at 11:18 AM, Esteban Lorenzano > wrote: > >> >> On 7 Feb 2017, at 10:57,

[Pharo-dev] Pharo 60 needs help because Removing-a-package-with-extensions-let-the-extensions-in-the-system-and-break-their-reload

https://pharo.fogbugz.com/f/cases/19664/Removing-a-package-with-extensions-let-the-extensions-in-the-system-and-break-their-reload

Re: [Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

I back up Pavel and Esteban here. On Tue, Feb 7, 2017 at 11:18 AM, Esteban Lorenzano wrote: > > On 7 Feb 2017, at 10:57, Pavel Krivanek wrote: > > The uperchase character is the symbol on the key. > > In OS X the uppercase characters are used: >

Re: [Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

> On 7 Feb 2017, at 10:57, Pavel Krivanek wrote: > > The uperchase character is the symbol on the key. > > In OS X the uppercase characters are used: > http://cdn.osxdaily.com/wp-content/uploads/2011/07/access-library-lion.jpg >

Re: [Pharo-dev] FileStreams and encoding ( opening a readStream on a FileRerefence)

OK, I committed the following in Zn #bleedingEdge: === Name: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.46 Author: SvenVanCaekenberghe Time: 7 February 2017, 11:07:31.306364 am UUID: a2928299-1dda-4fdf-b15e-e5d7bed2373e Ancestors: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.45 Add

Re: [Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

The uperchase character is the symbol on the key. In OS X the uppercase characters are used: http://cdn.osxdaily.com/wp-content/uploads/2011/07/access-library-lion.jpg In Chrome too: http://addoncrop.com/cdn/2014/12/Google-Chrome-Menu-Settions-option.png On Windows too:

Re: [Pharo-dev] Debugger hang when step throught

2017-02-07 10:30 GMT+01:00 Denis Kudriashov : > More simple way to reproduce: > > #(2) select: [:i| i] > > > Problem somehow related to mustBeBoolean error. If you try debug > > #(2) select: [:i| i / 0] > > > Debugger will fallback into #/ method at ZeroDivide statement. But

Re: [Pharo-dev] Debugger hang when step throught

More simple way to reproduce: #(2) select: [:i| i] Problem somehow related to mustBeBoolean error. If you try debug #(2) select: [:i| i / 0] Debugger will fallback into #/ method at ZeroDivide statement. But with mustBeBoolean trick it's not work. 2017-02-07 8:03 GMT+01:00 Stephane Ducasse

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

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

[Pharo-dev] [pharo-project/pharo-core] f197e6: 60376

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

Re: [Pharo-dev] Segmentation fault while installing Scale

Hi, We are looking at it with Santi. I see in the log that you're using an ubuntu 12? I tried in a debian jessie and Santi in an ubuntu 14 and we could not reproduce it. Also the travis ci of scale uses ubuntu 12 and the installation works in there... Could you give more details about your

Re: [Pharo-dev] [QA] Debugger buttons explained

Hi Hilaire, I find your use case interesting. It used to be the case, that one could discover an application commands by exploring the objects making up the GUI... Now, with Spec or Glamour, is that still the case? It seems not any more. Doru, can you confirm? Regards, Thierry 2017-02-06

Re: [Pharo-dev] Pharo 60 need help white-theme-color-for-button-is-not-good

> On 7 Feb 2017, at 08:07, Stephane Ducasse wrote: > > No it is important. > There is no point to have a supercool system that looks so bad and turn > people off. > But I do not get it your 13136 was integrated. > > No, this is exactly an example of this “even