August 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by H. Hirzel

Thank you Serge, good to see that there is progress with Tensorflow and PolyMath. I have problems installing Jupytertalk into a pristine 6.1 (I follow the instructions) Metacello new baseline: 'JupyterTalk'; repository: 'github://jmari/JupyterTalk'; load:'all' gives an error message 'Could not resolve: BaselineOfJupyterTalk' Is there something else which needs to be installed first? --Hannes On 7/28/18, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > On Sat, Jul 28, 2018 at 11:21 AM H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > >> Hello >> >> What is the status of this project? >> >> >> https://github.com/jmari/JupyterTalk >> >> > âYou can ask the author of the software, Jesus Mari Aguirre. He is quite > active. > W > âe talk together about be able to use Jupytalk with Tensorflow and > PolyMath. > > He was able to reproduce part of my talk about Tensorflow: > https://htmlpreview.github.io/?https://github.com/jmari/JupyterTalk/blob/ma… > > > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally for > machines to execute."http://www.doesnotunderstand.org/ >

Aug. 4, 2018

Re: [Pharo-users] BS Web and Pharo

by Tim Mackinnon

Yeah - that babyâ¦ I hate seeing it over and overâ¦ presumably its some js that a third part coughed up (badly). Tim > On 4 Aug 2018, at 00:05, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > I guess that one ... > As the general warning in cookies (grrr), or the gpdr or .... > <image1.png> > > EnvoyÃ© de mon iPhone > > Le 3 aoÃ»t 2018 Ã 22:17, Damien Pollet <damien.pollet+pharo(a)gmail.com <mailto:damien.pollet+pharo@gmail.com>> a Ã©crit : > >> On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> the constant pestering to sign up for the Pharo newsletter. >> >> which pestering, where ? :confused:

Aug. 4, 2018

Re: [Pharo-users] BS Web and Pharo

by CÃ©drick BÃ©ler

I guess that one ... As the general warning in cookies (grrr), or the gpdr or .... EnvoyÃ© de mon iPhone > Le 3 aoÃ»t 2018 Ã 22:17, Damien Pollet <damien.pollet+pharo(a)gmail.com> a Ã©crit : > >> On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works> wrote: >> the constant pestering to sign up for the Pharo newsletter. > > which pestering, where ? :confused:

Aug. 3, 2018

Re: [Pharo-users] BS Web and Pharo

by Damien Pollet

On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works> wrote: > the constant pestering to sign up for the Pharo newsletter. > which pestering, where ? :confused:

Aug. 3, 2018

Re: [Pharo-users] safely determining whether ProcessWrapper process is running

by Guillermo Polito

Hi, Sorry for the delay On Sat, Jun 30, 2018 at 7:38 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > I feel like I am missing something obvious, but is there a _safe_ way to > test if PW is still running? > I don't think so. ProcessWrapper primitives are not safe. If they are not called in the right order, of even, if one primitive fails and you call another primitive on the same object, it produces a segmentation fault. > > If the process pointer for whatever reason is no longer valid (e.g. the > image crashed / I closed image), then #isRunning results in crashing the > image. Maybe this is a bug? > > Thanks, > Peter > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 3, 2018

Re: [Pharo-users] BS Web and Pharo

by Guillermo Polito

+1 I don't know how to solve it, but I agree it bothers me... Of course at some point I started ignoring it, but I imagine it can create a bad impression for people from outside the community. On Thu, Aug 2, 2018 at 6:15 PM Tim Mackinnon <tim(a)testit.works> wrote: > > Hey guys - when reading about the BS web (great article btw - > https://pxlnv.com/blog/bullshit-web/ ) it reminded me about the constant > pestering to sign up for the Pharo newsletter. > > Given I am signed up - how can I stop it always popping up? > > Itâs in the list of the BS web... so do we really need it to do this? At > least it should be a cookie that if I have it it goes away, or better still > - just put it as a menu entry and let people sign up if they like out stuff? > > Given our community fights the BS can't we lead better? > > Tim > > Sent from my iPhone > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 3, 2018

BS Web and Pharo

by Tim Mackinnon

Hey guys - when reading about the BS web (great article btw - https://pxlnv.com/blog/bullshit-web/ ) it reminded me about the constant pestering to sign up for the Pharo newsletter. Given I am signed up - how can I stop it always popping up? Itâs in the list of the BS web... so do we really need it to do this? At least it should be a cookie that if I have it it goes away, or better still - just put it as a menu entry and let people sign up if they like out stuff? Given our community fights the BS can't we lead better? Tim Sent from my iPhone

Aug. 2, 2018

Re: [Pharo-users] transactions on pharo objects

by Esteban A. Maringolo

El miÃ©., 1 de ago. de 2018 20:52, Richard Sargent < richard.sargent(a)gemtalksystems.com> escribiÃ³: > Esteban A. Maringolo wrote > > As a general purpose solution if you can do that, you end up > > implementing a mini gemstone in Pharo :) > > > > But what's sure is that you should have a mini object-table of the > > "touched" objects or do "explicit" registration of these objects like > > GLORP allows you to do. > > > It seems to me that the fundamental problem with the idea of registering > each object with the transaction (or anything else) is that it requires > white-box knowledge of what every invoked behaviour will do and touch. The > above example is so minimal, it looks easy. > I agree with that. Deciding when to what to copy and what to preserve is always tricky unless yo decide to copy the whole object graph which would be terrible. Very much like what to proxy and what to forward in GemBuilder. I think if you really want transactional Smalltalk, you need to use one > designed expressly for that purpose. > (And fortunately, there is one.) > That's why I say this is tricky and you'll probably end up implementing a mini-GemStone. I don't know what it means in terms of programming, but having a transactional object memory would be a useful thing to work with. Regards, Esteban.

Aug. 2, 2018

Re: [Pharo-users] transactions on pharo objects

by Richard Sargent

Esteban A. Maringolo wrote > I think it is a tricky thing to do "in memory transactions", even > without thinking about databases. > You have to define what to keep and where to place the "original" > values (inst. vars.) of the object. > > As a general purpose solution if you can do that, you end up > implementing a mini gemstone in Pharo :) > > But what's sure is that you should have a mini object-table of the > "touched" objects or do "explicit" registration of these objects like > GLORP allows you to do. > > e.g. > > | p | > p := Person new. > System transaction: [:tx | > tx register: p. > p name: 'Nobody'. > p age: 70. > ]. It seems to me that the fundamental problem with the idea of registering each object with the transaction (or anything else) is that it requires white-box knowledge of what every invoked behaviour will do and touch. The above example is so minimal, it looks easy. I think if you really want transactional Smalltalk, you need to use one designed expressly for that purpose. (And fortunately, there is one.) > self assert: p name equals: 'Nobody'. > self assert: p age equals: 70. > > I'm using System here, to make it compatible with GemStone. > #transaction: could be implemented in terms of #beginTransaction, > #commitTransaction and internally use #abortTransaction if an > unhandled Error is signalled. > > Regards! > > Esteban A. Maringolo > El lun., 30 jul. 2018 a las 10:17, Peter UhnÃ¡k (< > i.uhnak@ > >) escribiÃ³: >> >> Hi, >> >> is there some library or approach how to do transactions in pharo? >> And I don't mean database transactions, but directly in memory on Pharo >> objects... e.g. >> >> p := Person new. >> >> transaction do: [ >> p name: 'Nobody'. >> p age: 70. >> ] on: Error do: [ >> transaction rollback. >> ]. >> >> self assert: p name equals: 'Nobody'. >> self assert: p age equals: 70. >> >> transaction do: [ >> p name: 'Somebody'. >> p age: 1 / 0. >> ] on: Error do: [ >> transaction rollback. >> ]. >> >> self assert: p name equals: 'Nobody'. >> self assert: p age equals: 70. >> >> Any pointers appreciated. >> >> Thanks, >> Peter -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 1, 2018

Re: [Pharo-users] Monticello default repositories & Iceberg

by Evan Donahue

Thanks to these replies I found the issue, but I'm not sure how to solve it. I found the start up script. I have never consciously set it, but I assume some process in the distant past automatically created it for me. The issue was that the settings for: #monticello#cacheDirectory and #monticello#defaultDirectoryName pointed to obsolete random projects from the past. I deleted them from the settings file, but it looks like when my new image autogenerated them, it stored new ones in the settings file that are equally irrelevant to future generated images: /home/myusername/Pharo/images/testimage/pharo-local/package-cache and /builds/workspace/Pharo-6.0-Update-Step-1-Tracker, respectively. What should I set these to so that they behave appropriately as I create new images in Pharo launcher? Does pharo launcher have a global dedicated place for a package cache, or is there a way to make it switch per new image? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 1, 2018