Re: [Pharo-dev] PharoSpur32Vm

2017-01-23 8:59 GMT+01:00 Esteban Lorenzano : > > On 22 Jan 2017, at 13:19, Nicolai Hess wrote: > > > > 2017-01-22 10:21 GMT+01:00 Clément Bera : > >> Hi, >> >> I believe they're built from* https://github.com/OpenSmalltalk/vm

Re: [Pharo-dev] PharoSpur32Vm

2017-02-04 1:44 GMT+01:00 Nicolai Hess : > > > 2017-01-23 8:59 GMT+01:00 Esteban Lorenzano : > >> >> On 22 Jan 2017, at 13:19, Nicolai Hess wrote: >> >> >> >> 2017-01-22 10:21 GMT+01:00 Clément Bera : >>

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

All my projects must be Pharo 6 ready because most of them were created inside Pharo 6 anyway. But thanks for the reminder . Time to make sure they work as expected. On Fri, 3 Feb 2017 at 15:06, Sven Van Caekenberghe wrote: > On 3 Feb 2017, at 13:48, Cyril Ferlicot D.

Re: [Pharo-dev] Zinc / REST misunderstanding

great I will not have time to look at it today, but I will definitely follow your suggestions, especially the contentReader:/contentWriter: part, coupled with JSON thanks again nicolas On 02/02/2017 18:29, Sven Van Caekenberghe wrote: Well, now that it works, we can make it better ;-)

Re: [Pharo-dev] PharoLauncher create image / default image name

Hi, Yes, I changed it on purpose after a small survey of people in the mod group. The old naming was very annoying, especially with some templates coming from Jenkins. If some still prefer the old naming, maybe the best way would be to have an option to choose the naming strategy. Christophe

Re: [Pharo-dev] PharoLauncher create image / default image name

Am 03.02.2017 12:35 nachm. schrieb "Peter Uhnak" : I was also looking at this, but couldn't figure out how to change it back, Do you know in what specific commit this happened? PharoLauncher-Core-ChristopheDemarey.100 (I prefer the old naming, since it included context and

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

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

Re: [Pharo-dev] PharoLauncher create image / default image name

> PharoLauncher-Core-ChristopheDemarey.100 Thanks! > If some still prefer the old naming, maybe the best way would be to have an > option to choose the naming strategy. Unless there is a critical mass of people it's imho needless clutter in the codebase; I can patch it myself locally. For me

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

> On 3 Feb 2017, at 13:48, Cyril Ferlicot D. wrote: > > On 03/02/2017 13:41, Sven Van Caekenberghe wrote: >> Thanks for report this, Cyril, it should be fixed in version 2.8.2 > > That was fast, thank you. Well, the bug report was very clear, it even included the

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

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

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

On 02/02/2017 17:18, Sven Van Caekenberghe wrote: > 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 >

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

Thanks for report this, Cyril, it should be fixed in version 2.8.2 > On 3 Feb 2017, at 13:36, Cyril Ferlicot D. wrote: > > On 02/02/2017 17:18, Sven Van Caekenberghe wrote: >> Good idea, Torsten! >> >> I updated the following (with new #stable releases and catalog

[Pharo-dev] [pharo-project/pharo-core] b13be4: 60372

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

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

On 03/02/2017 13:41, Sven Van Caekenberghe wrote: > Thanks for report this, Cyril, it should be fixed in version 2.8.2 > > That was fast, thank you. I confirm it work now. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France signature.asc

Re: [Pharo-dev] PharoLauncher create image / default image name

I was also looking at this, but couldn't figure out how to change it back, Do you know in what specific commit this happened? (I prefer the old naming, since it included context and I knew whether the image was Pharo or Moose). Thanks, Peter On Wed, Feb 01, 2017 at 08:23:33PM +0100, Cyril

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

Yes these numbers should be refactored For collections only the first and the last 21 elements are displayed in the Raw view. Don't remember why 21. Cheers, Andrei On Fri, Feb 3, 2017 at 3:13 AM, Ben Coman wrote: > Just curious what the magic numbers here relate to... >

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

They could be extracted to class vars for example TWENTY_ONE := 21. Later if performance is still not good enough they may be changed for example to TWENTY_ONE := 15. (joke) Cheers, Alex On 3 February 2017 at 17:08, Tudor Girba wrote: > There is very little meaning behind

Re: [Pharo-dev] magic numbers in gtInspectorVariableValuePairs

There is very little meaning behind the number. The previous inspector showed the first 100 and the last 10 elements. 100 is anyway too large for a quick inspection, so we picked another number. I wanted 42 but that was still large, so we are now at 21. Doru > On Feb 3, 2017, at 4:20 PM,