Re: [Pharo-dev] GTDebugger variables table

On Fri, Feb 3, 2017 at 10:21 AM, Ben Coman wrote: > On Fri, Feb 3, 2017 at 12:28 AM, Denis Kudriashov > wrote: > > > > 2017-02-02 17:16 GMT+01:00 John Brant : > >> > >> I think my preference would be to have several tabs

Re: [Pharo-dev] GTDebugger variables table

On Fri, Feb 3, 2017 at 12:28 AM, Denis Kudriashov wrote: > > 2017-02-02 17:16 GMT+01:00 John Brant : >> >> I think my preference would be to have several tabs for the variables. In >> addition to the one tab that we have now that shows all

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

On Fri, Feb 3, 2017 at 10: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? > > Context>>gtInspectorVariableValuePairs > Whoops, this is... Object>>gtInspectorVariableValuePairs >

[Pharo-dev] magic numbers in gtInspectorVariableValuePairs

Just curious what the magic numbers here relate to... and can they be factored out to a meaningful method name? Context>>gtInspectorVariableValuePairs "This is a helper method that returns a collection of variable_name -> value for the current object. Subclasses can override it to specialize what

Re: [Pharo-dev] athens dead code?

On 29 January 2017 at 19:16, stepharong wrote: > On Sun, 29 Jan 2017 17:21:44 +0100, Igor Stasenko > wrote: > > > > On 29 January 2017 at 16:16, stepharong wrote: > >> >> >> On 27 January 2017 at 00:06, stepharong

Re: [Pharo-dev] Zinc / REST misunderstanding

Well, now that it works, we can make it better ;-) This is a more correct way to do your call: ZnClient new beOneShot; contentWriter: [ :data | ZnEntity with: (STONJSON toString: data ) type: ZnMimeType applicationJson ]; url: 'http://server.com/redmine/issues/430.json';

Re: [Pharo-dev] Zinc / REST misunderstanding

Hi thanks Sven, it now works. from your answer, I could infer the final solution. Apart from your suggestions, the content-type: also had to be called on ZnClient and voila! nicolas On 02/02/2017 17:11, Sven Van Caekenberghe wrote: On 2 Feb 2017, at 16:51, Nicolas Anquetil

Re: [Pharo-dev] GTDebugger variables table

2017-02-02 17:16 GMT+01:00 John Brant : > I think my preference would be to have several tabs for the variables. In > addition to the one tab that we have now that shows all variables, I can > think of tabs for locals, inst vars, interesting variables, watched >

Re: [Pharo-dev] Pharo 6 update catalog entries

Good idea, Torsten! I updated the following (with new #stable releases and catalog configs for Pharo 3,4,5 & 6): - NeoCSV - NeoJSON - Ston - ZTimestamp - Stamp - ZincHTTPComponents - Zodiac - WebSockets - Zinc SSO These were already running 6.0 builds on the CI servers. Sven > On 31 Jan

Re: [Pharo-dev] GTDebugger variables table

On 02/02/2017 04:22 AM, Denis Kudriashov wrote: Now I think I realized main reason of my confusion. Temps and receiver vars are not just in single table but they are also sorted by name all together. I'm not a fan of this either. While I can filter by the type of variable to limit the list,

[Pharo-dev] Zinc / REST misunderstanding

Hi, I am trying to create a small Redmine wrapper with Zinc, using Redmine REST API And I am having a problem to update issues in redmine from zinc. In curl, I can do: curl -v -H "Content-Type: application/json" -X PUT --data-binary '{ "issue": { "subject": "Subject different

Re: [Pharo-dev] Pharo 6 update catalog entries

I update PolyMath for Pharo 6.0. All tests are green: https://github.com/PolyMathOrg/PolyMath On Tue, Jan 31, 2017 at 10:44 AM, Torsten Bergmann wrote: > Hi, > > in preparation of upcoming Pharo 6 release we already should do a pass on > all our external loadable projects: > > -

Re: [Pharo-dev] GTDebugger variables table

> On 02/02/2017 11:22, Denis Kudriashov wrote: > > Hi. > > Finally I force myself to report my bad feeling of merged variable table in > GTDebugger. > By "merged" I mean that debugger join temps and receiver state in one table. > Sometimes I really not like it because it is difficult to find