- Pharo-dev - lists.pharo.org

Looking for a good shortcut for "contextual spotter"

by Esteban Lorenzano

Hello, Most of you donât know it, but Calypso incorporates an option to show a âcontextual spotterâ which will list all available commands in the context you selected. This is meant to help on discoverability and reachability of commands available. This is *in addition to shortcuts* not a replace of them (but lets be honest, we have far more commands than those that are possible to handle with a simple shortcut). Anyway, originally I mapped this command to meta+/, which fitted well with my keyboard and language, but seems is not the case for many others (and this is not working at all on windows). So. Iâm looking for options :) So far I have this two ideas: 1- alt+enter 2- meta+h First one looks nice, but Iâm not sure it will work on all platforms/combinations. What do you think? Esteban Ps: I will also add an icon somewhere to expose the contextual spotter.

Nov. 6, 2018

Re: [Pharo-dev] Unable to repair repository

by Alistair Grant

Hi Guille, On Tue, 6 Nov 2018 at 10:43, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Alistair, > > On Tue, Nov 6, 2018 at 9:39 AM Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Everyone, >> >> In the latest Pharo (88c6b8d), attempting to repair the pharo >> repository, i.e. clone it, first a warning is raised: >> >> "There is no associated repository configured." >> >> and then a DNU: #pathString was sent to nil. >> >> The DNU is because IceTipCopyCommitishCommand>>canBeExecutedInContext: >> now sends #commitId instead of #shortCommitId. >> IceTipRepositoryModel>>shortCommitId has an exception handler, while >> #commitId doesn't. >> >> Can someone explain why the warning was added? It is a bit annoying >> to have to click through dialogs telling me that the repository I'm >> trying to create needs to be created. > > > I've seen that yesterday evening, and I've fixed it here https://github.com/pharo-vcs/iceberg/issues/1068. > I've put links on the original issues that caused the regression, and the workaround meanwhile we prepare a new version. > > A fix will be pushed in a 1.3.2 version in the following hours ^^. Cool, thanks! (I had already added the exception handler to #commitId as a partial workaround). >> Using the generic Error exception handler has the risk of hiding other >> problems. Wouldn't it be better to create a IceRepositoryMissing >> error, or similar? > > > The support for missing repositories should be indeed revisited a bit and enhanced. > Particularly, we have other issues related to this that we have not worked on yet like this one: > > https://github.com/pharo-vcs/iceberg/issues/949 > > This issue is pretty important, but no time to work on it yet, so if someone wants to propose a solution, we take it :)... I'm trying to review Pavel's PR #1953 [1], but may take a look afterwards. Thanks again, Alistair [1] https://github.com/pharo-project/pharo/pull/1953

Nov. 6, 2018

Re: [Pharo-dev] Zinc Websockets

by Sven Van Caekenberghe

Hi, > On 6 Nov 2018, at 02:06, Shaping <shaping(a)uurda.org> wrote: > > Hi all. > > What is the easiest way to port Zinc Websockets to VW? Has this been done? > > > Shaping Zinc-WebSockets-Core is actually not that big, but it builds on top of the Zinc HTTP Components framework and is kind of integrated with it. I would suggest you start by studying its implementation and then evaluate how to get this working on top of VW's HTTP classes. Sven

Nov. 6, 2018

Re: [Pharo-dev] Unable to repair repository

by Guillermo Polito

Hi Alistair, On Tue, Nov 6, 2018 at 9:39 AM Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Everyone, > > In the latest Pharo (88c6b8d), attempting to repair the pharo > repository, i.e. clone it, first a warning is raised: > > "There is no associated repository configured." > > and then a DNU: #pathString was sent to nil. > > The DNU is because IceTipCopyCommitishCommand>>canBeExecutedInContext: > now sends #commitId instead of #shortCommitId. > IceTipRepositoryModel>>shortCommitId has an exception handler, while > #commitId doesn't. > > Can someone explain why the warning was added? It is a bit annoying > to have to click through dialogs telling me that the repository I'm > trying to create needs to be created. > I've seen that yesterday evening, and I've fixed it here https://github.com/pharo-vcs/iceberg/issues/1068. I've put links on the original issues that caused the regression, and the workaround meanwhile we prepare a new version. A fix will be pushed in a 1.3.2 version in the following hours ^^. > > Using the generic Error exception handler has the risk of hiding other > problems. Wouldn't it be better to create a IceRepositoryMissing > error, or similar? > The support for missing repositories should be indeed revisited a bit and enhanced. Particularly, we have other issues related to this that we have not worked on yet like this one: https://github.com/pharo-vcs/iceberg/issues/949 This issue is pretty important, but no time to work on it yet, so if someone wants to propose a solution, we take it :)...

Nov. 6, 2018

Re: [Pharo-dev] [ANN] The STON Specification

by Shaping

STON is able to serialise Pharoâs Floats, what do you mean by double ? Floating-point numbers in IEEE 64-bit format, 14 or 15 significant digits, with a range between =10^307 and 10^307. Additionally, I recently asked Sven if t would be possible to store ScaledDecimals (I think it implements what you call ArbitraryPrecisionFloats) without loss of precision. Iâm referring VWâs Double (and SmallDouble in 64-bit engines/images). APFs are binary representations that can be arbitrarily large, using Integers (LargePositiveIntegers for example) to model the bits of the mantissa. Before, because STON extends JSON, it was storing all kind of numbers either as float or integer. Now, thanks to Sven, STON stores ScaledDecimals correctly (without loss of precision through serialisation as float, what was done before). But I do not know if this change is integrated in recent images yet. â¦.. Number subclass: #Float instanceVariableNames: '' classVariableNames: 'E Epsilon Halfpi Infinity Ln10 Ln2 MaxVal MaxValLn MinValLogBase2 NaN NegativeInfinity NegativeZero Pi RadiansPerDegree Sqrt2 ThreePi Twopi' poolDictionaries: '' category: 'Kernel-Numbers' My instances represent IEEE-754 floating-point double-precision numbers. They have about 16 digits of accuracy and their range is between plus and minus 10^307. Some valid examples are: 8.0 13.3 0.3 2.5e6 1.27e-30 1.27e-31 -12.987654e12 â¦. I see that Pharoâs Float is VWâs Double. So then I just need to be able to serialize APF. â¦. FIFloatType subclass: #FFIFloat128 instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'UnifiedFFI-Types' I'm a 128bits (cuadruple precision) float. It is usually not used, but some compiler modes support it (__float128 in gcc) THIS IS NOT YET SUPPORTED â¦. The class above is also from the Pharo 7 image. This is the largest of the c-type FFIFloats. Any Float classes of this size and larger for the Smalltalk heap on 64-bit Pharo? Cheers, Shaping Le 6 nov. 2018 Ã 06:58, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > a Ã©crit : (Having domain problems recently. Please excuse this posting if you have seen it twice. I've not seen it appear yet on the list.) Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of David T. Lewis Sent: Wednesday, October 31, 2018 14:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] [ANN] The STON Specification This is very clear and well written. Dave Hi, Since there can never be enough documentation I finally took some time to write a more formal description of STON as a data format. https://github.com/svenvc/ston/blob/master/ston-spec.md The idea is to let this stabilise a bit and to then update the two other documents describing STON, where necessary: https://github.com/svenvc/ston/blob/master/ston-paper.md https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc cessfulBuild/artifact/book-result/STON/STON.html Also, the latest changes in STON have to make their way to the Pharo image as well. https://github.com/svenvc/ston All feedback is welcome. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Nov. 6, 2018

Unable to repair repository

by Alistair Grant

Hi Everyone, In the latest Pharo (88c6b8d), attempting to repair the pharo repository, i.e. clone it, first a warning is raised: "There is no associated repository configured." and then a DNU: #pathString was sent to nil. The DNU is because IceTipCopyCommitishCommand>>canBeExecutedInContext: now sends #commitId instead of #shortCommitId. IceTipRepositoryModel>>shortCommitId has an exception handler, while #commitId doesn't. Can someone explain why the warning was added? It is a bit annoying to have to click through dialogs telling me that the repository I'm trying to create needs to be created. Using the generic Error exception handler has the risk of hiding other problems. Wouldn't it be better to create a IceRepositoryMissing error, or similar? Thanks, Alistair

Nov. 6, 2018

Re: [Pharo-dev] [ANN] Iceberg v1.3.1

by Cyril Ferlicot

On Mon, Nov 5, 2018 at 5:09 PM HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Cyril, > > Does the update apply to Pharo 6.1? > Hi, The version will not be present by default in Pharo 6.1 because it cause too much changes to be in a minor release. (The last Iceberg release in Pharo 6.1 was the 0.6 or 0.7 I think). But it can be loaded via the script in the README. > Cheers, > > HernÃ¡n > -- Cyril Ferlicot https://ferlicot.fr

Nov. 6, 2018

Re: [Pharo-dev] [ANN] The STON Specification

by Julien

Hello, STON is able to serialise Pharoâs Floats, what do you mean by double ? Additionally, I recently asked Sven if t would be possible to store ScaledDecimals (I think it implements what you call ArbitraryPrecisionFloats) without loss of precision. Before, because STON extends JSON, it was storing all kind of numbers either as float or integer. Now, thanks to Sven, STON stores ScaledDecimals correctly (without loss of precision through serialisation as float, what was done before). But I do not know if this change is integrated in recent images yet. Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 6 nov. 2018 Ã 06:58, Shaping <shaping(a)uurda.org> a Ã©crit : > > (Having domain problems recently. Please excuse this posting if you have > seen it twice. I've not seen it appear yet on the list.) > > > Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? > > Shaping > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of > David T. Lewis > Sent: Wednesday, October 31, 2018 14:58 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] [ANN] The STON Specification > > This is very clear and well written. > > Dave > >> Hi, >> >> Since there can never be enough documentation I finally took some time >> to write a more formal description of STON as a data format. >> >> https://github.com/svenvc/ston/blob/master/ston-spec.md >> >> The idea is to let this stabilise a bit and to then update the two >> other documents describing STON, where necessary: >> >> https://github.com/svenvc/ston/blob/master/ston-paper.md >> >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc >> cessfulBuild/artifact/book-result/STON/STON.html >> >> Also, the latest changes in STON have to make their way to the Pharo >> image as well. >> >> https://github.com/svenvc/ston >> >> All feedback is welcome. >> >> Sven >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> >> > > > > >

Nov. 6, 2018

Porting from VW to Pharo

by Shaping

Can someone point me to the best tools for porting from VW 7.10 to Pharo 7 64-bit (or maybe 6.1)? I'm not sure what to do about the namespaces. I realize that VW's namespace solution is just a good hack and that the true nature of the problem runs much deeper--but it does a good job of avoiding class-name collisions, which is mostly what I need it for, and I can control exactly how imports work. Any suggestions are welcome. Thanks. Shaping

Nov. 6, 2018

[ANN] The STON Specification

by Shaping

(Having domain problems recently. Please excuse this posting if you have seen it twice. I've not seen it appear yet on the list.) Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of David T. Lewis Sent: Wednesday, October 31, 2018 14:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] [ANN] The STON Specification This is very clear and well written. Dave > Hi, > > Since there can never be enough documentation I finally took some time > to write a more formal description of STON as a data format. > > https://github.com/svenvc/ston/blob/master/ston-spec.md > > The idea is to let this stabilise a bit and to then update the two > other documents describing STON, where necessary: > > https://github.com/svenvc/ston/blob/master/ston-paper.md > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc > cessfulBuild/artifact/book-result/STON/STON.html > > Also, the latest changes in STON have to make their way to the Pharo > image as well. > > https://github.com/svenvc/ston > > All feedback is welcome. > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Nov. 6, 2018