- Pharo-users - lists.pharo.org

Re: [Pharo-users] where to find the ia32/i386 runtime libraries

by Sven Van Caekenberghe

One among many: https://www.youtube.com/watch?v=I5ogPOs3PLM might help. Please ask again if you keep on having problems. > On 31 Aug 2015, at 09:39, Ben Coman <btc(a)openInWorld.com> wrote: > > It would seem you already have the necessary ia32 libs since you have successfully opened Pharo. So the VM is there. I think you may not have chosen Don't from the context menu of the selection. > Cheers ben > > On 31 Aug 2015 11:47 am, "albert" <albert(a)spiritone.com> wrote: > Dear Sirs: > > I have: opensuse 13.2 x86_64, and glibc 2.19. > So, I downloaded: Default GNU/Linux Pharo4.0-linux.zip. > > After extracting zip, README.txt says: > ~ Just install the ia32/i386 runtime libraries and you should be fine. > > However, there are no files with such names among the extracted files. > > How to proceed installing the runtime libraries? > In advance, thank you. > > > By the way, opening pharo tells me: > ~ You can learn pharo by highlighting the next line and selecting [Do it] from the context menu:" > PharoTutorial go. > > Obviously, nothing happens when following these instructions -- the vm isn't there. > > When closing the pharo environment window, I get asked to save any changes. > At least, I get a dialog widget. > > Thanks, > Albert

Aug. 31, 2015

Re: [Pharo-users] where to find the ia32/i386 runtime libraries

by Ben Coman

It would seem you already have the necessary ia32 libs since you have successfully opened Pharo. So the VM is there. I think you may not have chosen Don't from the context menu of the selection. Cheers ben On 31 Aug 2015 11:47 am, "albert" <albert(a)spiritone.com> wrote: > Dear Sirs: > > I have: opensuse 13.2 x86_64, and glibc 2.19. > So, I downloaded: Default GNU/Linux Pharo4.0-linux.zip. > > After extracting zip, README.txt says: > ~ Just install the ia32/i386 runtime libraries and you should be fine. > > However, there are no files with such names among the extracted files. > > How to proceed installing the runtime libraries? > In advance, thank you. > > > By the way, opening pharo tells me: > ~ You can learn pharo by highlighting the next line and selecting [Do it] > from the context menu:" > PharoTutorial go. > > Obviously, nothing happens when following these instructions -- the vm > isn't there. > > When closing the pharo environment window, I get asked to save any changes. > At least, I get a dialog widget. > > Thanks, > Albert >

Aug. 31, 2015

where to find the ia32/i386 runtime libraries

by albert

Dear Sirs: I have: opensuse 13.2 x86_64, and glibc 2.19. So, I downloaded: Default GNU/Linux Pharo4.0-linux.zip. After extracting zip, README.txt says: ~ Just install the ia32/i386 runtime libraries and you should be fine. However, there are no files with such names among the extracted files. How to proceed installing the runtime libraries? In advance, thank you. By the way, opening pharo tells me: ~ You can learn pharo by highlighting the next line and selecting [Do it] from the context menu:" PharoTutorial go. Obviously, nothing happens when following these instructions -- the vm isn't there. When closing the pharo environment window, I get asked to save any changes. At least, I get a dialog widget. Thanks, Albert

Aug. 31, 2015

Publish to Monticello and mirror to git

by HernÃ¡n Morales Durand

Is it possible right now in Pharo 4 or 5 on any platform? Cheers, HernÃ¡n

Aug. 30, 2015

Re: [Pharo-users] Pharo 4.0 -- Inspecting a recursive data structure is slow

by Nicolai Hess

No this doesn't even fully work for the GTInspector (even not in Pharo 5.0). It is the same issue Ben discovered when working with the pointer explorer. (http://forum.world.st/Proposal-for-LiteralArray-class-tp4803015.html and http://forum.world.st/Fwd-14827-ProtoObject-pointersTo-failing-circular-ref… ) The problem is that arrays printOn: does not check for already visited objects (squeak does this, but the implementation in pharo changed). For example, in Pharo 50 | myDict | myDict := Dictionary new. myDict at: #hello put: 'hello'. myDict at: #recurHello put: myDict. myDict inspect you can open the inspector, but selecting the first element in the "keys" tab makes the image unresponsive. The same happens if you select the #array instvar in the "raw" tab. 2015-08-29 15:16 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > As for me no need to hurry. I switch now to Pharo 5 build 50287 in the > meantime. I will continue using that if I do not run into larger > problems. > > --Hannes > > On 8/29/15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 29 Aug 2015, at 12:58, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> > >> Was there an issue/fix for this in Pharo 5? > >> It might be worth backporting to Pharo 4. > >> > > Maybe one related to what is printed for the dictionary. > > It used to be very slow for large collections > > > > > https://pharo.fogbugz.com/f/cases/15311/The-display-string-for-collection-m… > > > >

Aug. 30, 2015

About videos, youtube and our future mooc

by stepharo

Hi guys 1 Pharo Starter Kit ---------------- We started to work on a Pharo Starter Kit distribution (to be announced soon) containing - all our new lecture support (revisited lectures) - the books - vm/images - videos - ... All the material will be used for the Pharo Mooc we are working on http://sdmeta.gforge.inria.fr/StarterKitCache/ Point 1: If you have suggestions please let us know. YouTube Collection ---------------- I also started to collect youtube videos to put on the starter kit. You can find a first collection at http://sdmeta.gforge.inria.fr/Videos/YouTubeVideos/ If you know a cool video that you think should be added to this collection let me know. 3 Future nice videos ----------------- Now for the Mooc we would like to have a special ressources where each week we let the students watch cool videos on cool external projects. - We will propose a kind of template such as 3 min max, a title, email, project If you have idea start to think about it. Stef

Aug. 29, 2015

Re: [Pharo-users] Pharo 4.0 -- Inspecting a recursive data structure is slow

by H. Hirzel

As for me no need to hurry. I switch now to Pharo 5 build 50287 in the meantime. I will continue using that if I do not run into larger problems. --Hannes On 8/29/15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 29 Aug 2015, at 12:58, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> Was there an issue/fix for this in Pharo 5? >> It might be worth backporting to Pharo 4. >> > Maybe one related to what is printed for the dictionary. > It used to be very slow for large collections > > https://pharo.fogbugz.com/f/cases/15311/The-display-string-for-collection-m… >

Aug. 29, 2015

Re: [Pharo-users] Pharo 4.0 -- Inspecting a recursive data structure is slow

by Marcus Denker

> On 29 Aug 2015, at 12:58, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Was there an issue/fix for this in Pharo 5? > It might be worth backporting to Pharo 4. > Maybe one related to what is printed for the dictionary. It used to be very slow for large collections https://pharo.fogbugz.com/f/cases/15311/The-display-string-for-collection-m…

Aug. 29, 2015

Re: [Pharo-users] Pharo 4.0 -- Inspecting a recursive data structure is slow

by Marcus Denker

> On 29 Aug 2015, at 13:27, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > On 8/29/15, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> It seems to be fixed in Pharo5 already. Debugger comes up within less than a >> second and is usable. > > Very welcome. > I assume you mean 'Inspector' (not debugger) > Yes. Marcus

Aug. 29, 2015

Re: [Pharo-users] Pharo 4.0 -- Inspecting a recursive data structure is slow

by H. Hirzel

On 8/29/15, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Was there an issue/fix for this in Pharo 5? > It might be worth backporting to Pharo 4. If it is not a big effort, yes please. > > On Sat, Aug 29, 2015 at 12:06 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> It seems to be fixed in Pharo5 already. Debugger comes up within less >> than >> a second and is usable. >> >> Marcus >> > On 29 Aug 2015, at 11:57, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> > >> > Andrei, >> > >> > Thanks for confirming the bug. >> > >> > Report is here >> > >> > >> https://pharo.fogbugz.com/f/cases/16425/Pharo-4-0-Inspecting-a-recursive-da… >> > >> > --Hannes >> > >> > On 8/29/15, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> Hi Hannes, >> >> >> >> Can open a bug report? >> >> I though most recursive problems were fixed in the new inspector. >> >> Seems that there are still some related to printing recursive >> structures. >> >> >> >> You can switch to the previous inspector (GTInspector >> >> setGTInspectorEnabledStatus: false), >> >> however, this bug seem to also kill that inspector. >> >> >> >> Cheers, >> >> Andrei >> >> >> >> On Sat, Aug 29, 2015 at 7:16 AM, H. Hirzel <hannes.hirzel(a)gmail.com> >> wrote: >> >> >> >>> Hello >> >>> >> >>> I have realized that inspecting a recursive data structure is very >> >>> slow in Pharo 4.0 >> >>> >> >>> A test case: >> >>> >> >>> | myDict | >> >>> myDict := Dictionary new. >> >>> myDict at: #hello put: 'hello'. >> >>> myDict at: #recurHello put: myDict. >> >>> myDict inspect >> >>> >> >>> It takes a long time for the inspector to come up. And the image >> >>> freezes later on if you continue. >> >>> >> >>> The problem is with the inspector because if I do >> >>> | myDict | >> >>> myDict := Dictionary new. >> >>> myDict at: #hello put: 'hello'. >> >>> myDict at: #recurHello put: myDict. >> >>> 3 + 4 inspect >> >>> >> >>> it comes up instantly. >> >>> >> >>> >> >>> As a comparison I attach the Cuis ** test result. The inspector comes >> >>> up instantly and the image does not have any problems. >> >>> >> >>> >> >>> What are the workarounds in Pharo 4.0? >> >>> >> >>> - Setting a time out somewhere? >> >>> - Disabling certain functions? >> >>> - Loading a simpler inspector? >> >>> >> >>> Regards >> >>> >> >>> Hannes >> >>> >> >>> >> >>> ** current build 2463.image >> >>> https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev >> >>> >> >> >> > >> >> >> >

Aug. 29, 2015