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

Jupyter notebooks are not limited to Python, there are more than 40 https://github.com/jupyter/jupyter/wiki/Jupyter-kernels Pharo Smalltalk is one of them https://github.com/jmari/JupyterTalk I'd like to get it up and running On 8/7/18, Andrew Glynn wrote: > Grafoscopio exists due to vario

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

Grafoscopio exists due to various limitations of Jupyter, particularly the lack of real support for objects in its core language - Python. JSON is not equivalent to STON even in terms of storing JavaScript, it's mainly a data format. On 8/7/18, 2:14 PM, "Pharo-users on behalf of Sean P. DeNig

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

Hannes Hirzel wrote > P.S. Some notes and links how Jupyter notebooks relate to the Dynabook > idea here > http://wiki.squeak.org/squeak/1318 >From the swiki: "A Jupyter Notebook is… similar to Active Essays kept in a Smalltalk based Dynabook." I've understood a key point of the Dynabook dream (a

[Pharo-users] Dynabook and learning by doing

How could Dynabook and learning by doing could be related? http://blog.drgeo.eu/post/2018/Learning-by-doing Hilaire -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] [Pharo-dev] New Iceberg Version 1.2.1

Only adding a small detail, the Metacello expression is used to generate the project that is offered. Also I see it as the Detached head status for projects that are loaded using Metacello. Maybe we should display the dirtiness in other way, but I think that is not a problem. It is normal that a p

Re: [Pharo-users] [Pharo-dev] New Iceberg Version 1.2.1

Hi, I'll write down some of the reasons of the project's design, like that I can afterwards copy paste it in the wiki :). First, this design did not came up from an egg. We worked on it for about two months. And it is thought to be backwards compatible and manage lots of metacello particularities

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

On 08/07/2018 02:15 AM, Evan Donahue wrote: > Yes, that's right. As long as I don't "store settings" everything is > ok, but if I do find myself wanting to change a global setting of some > kind, and I hit "store," it /also/ stores the metacello paths, which > will then be incorrect for the next ne

[Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

Hi guys - I’ve been hammering on the exercism project to get pharo shining over there… its been a good side distraction (there is lots of energy in that community to) and its made me really push my use of Iceberg & git as well as learn some fo the newish file reference stuff (still getting good

Re: [Pharo-users] [Pharo-dev] New Iceberg Version 1.2.1

Forgot one thing. I find the new project feature quite intrusive. It will add those file to all repos unasked. So I have a lot of dirty projects I have no write access to. How is this supposed to work. Isn’t it better to assume defaults and add an option to add project files? Norbert > Am 07

Re: [Pharo-users] [Pharo-dev] New Iceberg Version 1.2.1

Great, thanks! I used 1.2.0 a few days ago and I had some problems: - some repos like voyage had a .properties file in the repo with content „{}“. This made the repo unusable. The only thing noticed is that in the repo view in iceberg the packages were named Voyage-Core.package instead of Voyag

Re: [Pharo-users] Pharo 7 file streams guideline

Guillermo Polito wrote > On Tue, Jul 31, 2018 at 6:29 PM Damien Pollet < > damien.pollet+pharo@ > > > wrote: > >> Hi Sven… a couple questions: >> >> - is there a preferred order of composition between the encoding and >> buffering streams ? If yes, it the same for read and write stream, or >> re

[Pharo-users] New Iceberg Version 1.2.1

New Iceberg Version 1.2.1 [ https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.0 + https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.1] Thanks to all brave users, issue reporters, and contributors :). This version includes the implementation of projects. Projects are a way of defining bas

Re: [Pharo-users] BS Web and Pharo

Hi, I have removed it. > On 2 Aug 2018, at 18:15, Tim Mackinnon 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 >

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

On Tue, Aug 7, 2018 at 9:24 AM Tim Mackinnon wrote: > Somewhat related - but the Pharo equivalent (said naively - as I’ve only > seen demos of Jupyter and not used it in anger myself) is gtDocumentor > which looks to be the concept reimagined in Smalltalk. Apologies if you > already know about it

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

Somewhat related - but the Pharo equivalent (said naively - as I’ve only seen demos of Jupyter and not used it in anger myself) is gtDocumentor which looks to be the concept reimagined in Smalltalk. Apologies if you already know about it - but its so cool its worth checking out if you haven’t -

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

The settings that you save will apply to all images - so you need to clear out those settings for shared repo’s etc. I think what is confusing is that using the Save button - means apply the settings to all images. If you change the setting locally in your image and don’t press save, it persis