- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Seg Fault Pharo 7.0.3

by Sven Van Caekenberghe

> On 5 Oct 2019, at 04:48, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sven Van Caekenberghe-2 wrote >> Are you using full screen mode ? > > The window was probably maximized, but not in fullscreen OK, that is not the same, that should work.

Oct. 5, 2019

Re: [Pharo-dev] XmlSupport on GitHub?

by ducasse

I would suggest to not wait for monty and do it. May be his life attracted in another sphere and this is ok too. Or may be he does not have cycles now. Stef > On 5 Oct 2019, at 00:09, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > Yes - this is still the current state that there only is a copy of Pharo's XML project available on Svens github account. > > I suggested in [1] to have a more central/official community place on https://github.com/pharo-contributions location > and offered a helping hand for the migration. If I remember correctly Peter offered help as well. > > But for the migration to GH it would be good to also know about Monty's github username (as I wrote in [3]) - so far there was > NO FURTHER RESPONSE from Monty's side and therefore no further activity in moving XML code to github more officially. > > Bye > T. > > [1] http://forum.world.st/Status-of-XML-Support-s-move-to-GitHub-tt5093297.html > [2] https://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2019-March/2747… > [3] https://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2019-March/2747… > > >> Gesendet: Freitag, 04. Oktober 2019 um 12:43 Uhr >> Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] XmlSupport on GitHub? >> >> >> >>> On 4 Oct 2019, at 12:37, BenoÃ®t Verhaeghe <badetitou(a)gmail.com> wrote: >>> >>> Hello, >>> >>> I think this is what you're looking for >>> https://github.com/svenvc/XML-Support-Pharo >>> >>> (but maybe not) >> >> Indeed, this is just a dirty 'last-version-only' copy, definitively *not* the final solutions. >> >>> BenoÃ®t >>> >>> Le ven. 4 oct. 2019 Ã 12:29, Tudor Girba <tudor(a)tudorgirba.com> a Ã©crit : >>> Hi, >>> >>> Did anyone port XmlSupport to GitHub? >>> >>> Cheers, >>> Tudor >>> >>> >>> -- >>> feenk.com >>> >>> âHow do you feenk today?" >>> >>> >> >> >> >

Oct. 5, 2019

Re: [Pharo-dev] BlockClosures - Equality and Things

by ducasse

Hi sean just a question since I started to finally understand for real the multiple objects that closures represent :) Would it not make sense to have internally an object (not a closure) that represent a method and that answer the method value or value: You could save this object and on potentially even generate a block if needed. I do not think that in magritte we use the closuring aspect of closure we use them as anonymous method. Stef > On 5 Oct 2019, at 04:58, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > While developing Magritte, I have a problem because blocks that are > read/written to/from strings (e.g. via Magritte forms) have a different > outerContext before and after and thus I don't know how (without an ugly > hack) to determine whether they were changed by the user. > > Question: Is there a smarter way to do block equality? > Currently in Pharo block comparison is via #==. In Squeak, there is: > BlockClosure >> #= aClosure > self == aClosure ifTrue: [^true]. > aClosure class = self class ifFalse: [^false]. > (self method == aClosure method and: [startpc = aClosure startpc > and: [self > isClean]]) "<--- this line" > ifTrue: [^true]. > ^outerContext = aClosure outerContext and: [startpc = aClosure > startpc] Do you know if they have the new closure model because we are working to move to it. > > I'm not totally sold on the implementation due to the `startpc = aClosure > startpc` the first time it appears (in the comment-marked line). With it, in > a workspace, the following is false: `[1] = [1]`, but removing that test > makes it true. I'd like something that returns true if both blocks are clean > and they "do the same thing". But I like the track it's on... > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 5, 2019

BlockClosures - Equality and Things

by Sean P. DeNigris

While developing Magritte, I have a problem because blocks that are read/written to/from strings (e.g. via Magritte forms) have a different outerContext before and after and thus I don't know how (without an ugly hack) to determine whether they were changed by the user. Question: Is there a smarter way to do block equality? Currently in Pharo block comparison is via #==. In Squeak, there is: BlockClosure >> #= aClosure self == aClosure ifTrue: [^true]. aClosure class = self class ifFalse: [^false]. (self method == aClosure method and: [startpc = aClosure startpc and: [self isClean]]) "<--- this line" ifTrue: [^true]. ^outerContext = aClosure outerContext and: [startpc = aClosure startpc] I'm not totally sold on the implementation due to the `startpc = aClosure startpc` the first time it appears (in the comment-marked line). With it, in a workspace, the following is false: `[1] = [1]`, but removing that test makes it true. I'd like something that returns true if both blocks are clean and they "do the same thing". But I like the track it's on... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 5, 2019

Re: [Pharo-dev] Seg Fault Pharo 7.0.3

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > Are you using full screen mode ? The window was probably maximized, but not in fullscreen ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 5, 2019

Re: [Pharo-dev] XmlSupport on GitHub?

by Torsten Bergmann

Hi, Yes - this is still the current state that there only is a copy of Pharo's XML project available on Svens github account. I suggested in [1] to have a more central/official community place on https://github.com/pharo-contributions location and offered a helping hand for the migration. If I remember correctly Peter offered help as well. But for the migration to GH it would be good to also know about Monty's github username (as I wrote in [3]) - so far there was NO FURTHER RESPONSE from Monty's side and therefore no further activity in moving XML code to github more officially. Bye T. [1] http://forum.world.st/Status-of-XML-Support-s-move-to-GitHub-tt5093297.html [2] https://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2019-March/2747… [3] https://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2019-March/2747… > Gesendet: Freitag, 04. Oktober 2019 um 12:43 Uhr > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] XmlSupport on GitHub? > > > > > On 4 Oct 2019, at 12:37, BenoÃ®t Verhaeghe <badetitou(a)gmail.com> wrote: > > > > Hello, > > > > I think this is what you're looking for > > https://github.com/svenvc/XML-Support-Pharo > > > > (but maybe not) > > Indeed, this is just a dirty 'last-version-only' copy, definitively *not* the final solutions. > > > BenoÃ®t > > > > Le ven. 4 oct. 2019 Ã 12:29, Tudor Girba <tudor(a)tudorgirba.com> a Ã©crit : > > Hi, > > > > Did anyone port XmlSupport to GitHub? > > > > Cheers, > > Tudor > > > > > > -- > > feenk.com > > > > âHow do you feenk today?" > > > > > > >

Oct. 4, 2019

[Pharo 8.0] Build #833: Compiler: Cache Vector Index

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #833 was: FAILURE. The Pull Request #4827 was integrated: "Compiler: Cache Vector Index" Pull request url: https://github.com/pharo-project/pharo/pull/4827 Issue Url: https://github.com/pharo-project/pharo/issues/CacheVectorIndex Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 4, 2019

What is a GlobalIdentifier

by StÃ©phane Ducasse

Hi We have a package SystemIdentification and I would like to know if this is still in use. Here is the comment of the class. I keep global IDs that are used for tracking user activity, e.g. computer id. By default, you should access me by calling #uniqueInstance. Responsibility: The IDs that are important to store onto disk (and shared by all images) should be placed in persistedInformation instance variable. On other hand, if you do not want to store it onto disk, create a new instance variable. I can #loadPreferences and #savePreferences onto a disk. I know computer ID and secret ID. Computer ID is a global UUID that is share among all the images. It is stored on a local disk. Secret ID is use for encrypting information, e.g., class names, method names. You can use #hashForText: method. Collaborators: I do not collaborate with other classes. I only offer the basic IDs for other frameworks. Public API and Key Messages - computerUUID - ensureComputerUUID - hashForText: - loadPreferences - savePreferences. Before using #computerUUID, you should call #ensureComputerUUID. It will update UUID from the disk or stores existing one if it is not stored yet. I behave like this as automatic storing data to disk on image start-up leads to errors. It looks like it is used by the GTEventCollector and I wonder if it is used and useful anymore. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Oct. 4, 2019

Re: [Pharo-dev] Seg Fault Pharo 7.0.3

by Sven Van Caekenberghe

Are you using full screen mode ? Because then it is a known issue. > On 4 Oct 2019, at 18:58, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Also, the image is sometimes crashing when my MacBook goes to sleep. Not sure > if it's related because there is no crash amp > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 4, 2019

[Pharo 8.0] Build #832: Improve-slot-error-message

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #832 was: SUCCESS. The Pull Request #4826 was integrated: "Improve-slot-error-message" Pull request url: https://github.com/pharo-project/pharo/pull/4826 Issue Url: https://github.com/pharo-project/pharo/issues/Improve Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 4, 2019