Re: [Pharo-users] Morph reacting to Window being closed

Thank you Henrik, #outOfWorld: was the best solution to me, as I can use it even when I don't control the window/container the morph is embedded in. Peter On Sun, Jul 29, 2018 at 10:16 PM, Henrik-Nergaard wrote: > Hi Peter, > > There are two methods which can be used for this purpose. > #outOf

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

P.S. Some notes and links how Jupyter notebooks relate to the Dynabook idea here http://wiki.squeak.org/squeak/1318 My aim is to use nteract as client (https://nteract.io/ ) together with a Pharo based Smalltalk "kernel" (i.e. server acting as the "scripting engine") On 8/7/18, H. Hirzel wrote:

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

Thank you, Evan, for an alternative load script. Unfortunately it gives the same error message. I use a recent, pristine Pharo 6.1 installation on a 64bit Ubuntu based Linux. On 8/4/18, Evan Donahue wrote: > Try: > > Metacello new > githubUser: 'jmari' project: 'JupyterTalk' commitish

[Pharo-users] Cargo & Future Proofing Releases

Hi, I will have a few general interest packages to release in the near future, for performance testing, contracts, and the like, and I'm wondering what the current story is for package release. I've heard some things about an upcoming "Cargo" package manager, so I'm wondering what the timeline on

Re: [Pharo-users] Pharo Launcher & Stored Settings

Hmm, the only things I'm trying to accomplish are 1) use Pharo Launcher and 2) have each new image keep its repositories separate, as advised by others on the list, so that different images can check out different branches. Does that set up require custom scripting to adjust the repo path? The ca

Re: [Pharo-users] transactions on pharo objects

Hi This research from VPRI may be useful: Worlds: Controlling the Scope of Side Effects and Experiments with Worlds (Alessandro Warth, Yoshiki Ohshima, Ted Kaehler, and Alan Kay) They had a J

Re: [Pharo-users] BS Web and Pharo

Ditto here, and I'm already subscribed to the newsletter! So it's not only nagging, but also superfluous. On 03/08/2018 21:42, Tim Mackinnon wrote: > 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 0