June 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Morphic or forking bug?

by Sven Van Caekenberghe

Hi Horrido, It is very hard to follow what you are exactly doing or trying to do. Here is the simplest example I can think of that updates something in Morphic on a regular basis. StringMorph subclass: #MyClock instanceVariableNames: '' classVariableNames: '' package: '_UnpackagedPackage' MyClock>>#initialize super initialize. self updateClock MyClock>>#step self updateClock MyClock>>#updateClock self contents: Time now printString MyClock class>>#open "self open" ^ self new openInWindow This inherits #stepTime as 1 second. If I open such a window and save my image, it is still there when the image is restarted, with the clock still working. Updating (data structures in) the main UI process from another process is dangerous. Saving such constructs is even more dangerous. HTH, Sven > On 2 Jun 2017, at 15:54, horrido <horrido.hobbies(a)gmail.com> wrote: > > Sorry, I could be mistaken. I just checked my notes. The *0 asString* test > failed once, but I've not been able to replicate it. I might've been working > with an unclean image. > > So perhaps it is related to Morphic, after all. > > > horrido wrote >> Yup, they all fail. Interesting that > * >> 0 asString > * >> fails. This means it has NOTHING to do with Morphic (or Morphic being >> thread-unsafe). >> >> Ben Coman wrote >>> On Wed, May 31, 2017 at 10:23 PM, horrido < > >>> horrido.hobbies@ > >>> > wrote: >>> >>> Can you try a few other variations... >>> [ [ true ] whileTrue: [ 0 asString. delay wait ] fork. >>> [ [ true ] whileTrue: [ a contents: '0'. delay wait ] fork. >>> [ [ true ] whileTrue: [ a contents: '0'. ] forkAt: 20. >>> >>> cheers -ben > > > > > > -- > View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4948984.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 2, 2017

Re: [Pharo-users] Morphic or forking bug?

by horrido

Sorry, I could be mistaken. I just checked my notes. The *0 asString* test failed once, but I've not been able to replicate it. I might've been working with an unclean image. So perhaps it is related to Morphic, after all. horrido wrote > Yup, they all fail. Interesting that * > 0 asString * > fails. This means it has NOTHING to do with Morphic (or Morphic being > thread-unsafe). > > Ben Coman wrote >> On Wed, May 31, 2017 at 10:23 PM, horrido < >> horrido.hobbies@ >> > wrote: >> >> Can you try a few other variations... >> [ [ true ] whileTrue: [ 0 asString. delay wait ] fork. >> [ [ true ] whileTrue: [ a contents: '0'. delay wait ] fork. >> [ [ true ] whileTrue: [ a contents: '0'. ] forkAt: 20. >> >> cheers -ben -- View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4948984.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 2, 2017

Re: [Pharo-users] Morphic or forking bug?

by horrido

Yup, they all fail. Interesting that *0 asString* fails. This means it has NOTHING to do with Morphic (or Morphic being thread-unsafe). Ben Coman wrote > On Wed, May 31, 2017 at 10:23 PM, horrido < > horrido.hobbies@ > > wrote: > > Can you try a few other variations... > [ [ true ] whileTrue: [ 0 asString. delay wait ] fork. > [ [ true ] whileTrue: [ a contents: '0'. delay wait ] fork. > [ [ true ] whileTrue: [ a contents: '0'. ] forkAt: 20. > > cheers -ben -- View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4948983.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 2, 2017

Other halt messages

by Stephane Ducasse

Hi I would love to have

June 2, 2017

Re: [Pharo-users] Porting Transducers to Pharo

by Stephane Ducasse

There is a package for that NGFileOuter or something like that on cincom store. We used it for mobydic code. On Wed, May 31, 2017 at 6:35 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > If I remember correctly, there is a parcel in VisualWorks to export a file > out (Squeak format). > > @Milton, can you give a hand to Steffen? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 31, 2017, at 10:32 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > > Thanks for the encouraging response! First question: Which is the > recommended (friction free) way to exchange code between VW and Pharo? > > Cheers! > Steffen > > Am .05.2017, 16:22 Uhr, schrieb Alexandre Bergel <alexandre.bergel(a)me.com > >: > > I second Sven. This is very exciting! > > Let us know when you have something ready to be tested. > > Alexandre > > > > > >

June 2, 2017

Re: [Pharo-users] Morphic or forking bug?

by horrido

Here is something I found by accident... If I run my app, then close it, then save/exit the image, then open the image again, edit my application class to add a new instance variable, then save the change â Pow! â I get about a dozen debugger pop-ups saying "#wait was sent to nil". What this tells me (and you may correct me if I'm wrong), the VM still has a thread running that is sending #wait messages to my application *which has already shutdown*. This can't be good, but whether this is related to the segmentation fault is anybody's guess at this point. Stephane Ducasse-3 wrote > Thanks for reporting. > I hope that in Pharo 70 we will get rid of the FreeType pluging. > > Stef > > On Thu, Jun 1, 2017 at 3:30 PM, horrido < > horrido.hobbies@ > > wrote: > >> I downloaded Pharo 6.0 but used the same Spur VM (which I presume is >> still >> the latest for Raspberry Pi): >> http://files.pharo.org/vm/pharo-spur32/linux/armv6/pharo-linux-ARMv6- >> 201705051953-b8db6de.zip >> >> It crashed, too. >> >> >> Denis Kudriashov wrote >> > 2017-05-31 17:57 GMT+02:00 horrido < >> >> > horrido.hobbies@ >> >> > >: >> > >> >> I'm using Pharo 5.0 >> > >> > >> > I test it with Pharo 6 (latest image and VM) and have no problem. Could >> > you >> > check it too? >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Morphic- >> or-forking-bug-tp4948727p4948818.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> -- View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4948911.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 2, 2017

Re: [Pharo-users] Pharo and QT

by Stephane Ducasse

Hi dimitris We would love to have that. We could have a Spec binding and build automatically applications in QT for people willing. Esteban always wanted to have a Cocoa binding used the same way. But this is large task Stef On Thu, Jun 1, 2017 at 2:44 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > A must for any serious dekstop application with Pharo, but it is a hudge > task > > > Le 29/05/2017 Ã 14:35, Dimitris Chloupis a Ã©crit : > > Is there an interest for working with QT from Pharo ? I make no > > promises just something I was interested in trying. > > -- > Dr. Geo > http://drgeo.eu > > > >

June 1, 2017

Re: [Pharo-users] Morphic or forking bug?

by Stephane Ducasse

Thanks for reporting. I hope that in Pharo 70 we will get rid of the FreeType pluging. Stef On Thu, Jun 1, 2017 at 3:30 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > I downloaded Pharo 6.0 but used the same Spur VM (which I presume is still > the latest for Raspberry Pi): > http://files.pharo.org/vm/pharo-spur32/linux/armv6/pharo-linux-ARMv6- > 201705051953-b8db6de.zip > > It crashed, too. > > > Denis Kudriashov wrote > > 2017-05-31 17:57 GMT+02:00 horrido < > > > horrido.hobbies@ > > > >: > > > >> I'm using Pharo 5.0 > > > > > > I test it with Pharo 6 (latest image and VM) and have no problem. Could > > you > > check it too? > > > > > > -- > View this message in context: http://forum.world.st/Morphic- > or-forking-bug-tp4948727p4948818.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 1, 2017

[ANN] Pharo Sprint App minor release for the Pharo Sprint June 2

by Juraj Kubelka

Hi, we have just released new minor version of the Pharo Sprint App. There are some minor bug fixes included and users asked me to be able to remove cases from the proposed list. See you around tomorrow during the sprint and if you have issues to work on, propose them using the app :-) Juraj Download link: https://github.com/JurajKubelka/PharoSprint <https://github.com/JurajKubelka/PharoSprint>

June 1, 2017

Re: [Pharo-users] Morphic or forking bug?

by horrido

I downloaded Pharo 6.0 but used the same Spur VM (which I presume is still the latest for Raspberry Pi): http://files.pharo.org/vm/pharo-spur32/linux/armv6/pharo-linux-ARMv6-201705… It crashed, too. Denis Kudriashov wrote > 2017-05-31 17:57 GMT+02:00 horrido < > horrido.hobbies@ > >: > >> I'm using Pharo 5.0 > > > I test it with Pharo 6 (latest image and VM) and have no problem. Could > you > check it too? -- View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4948818.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 1, 2017