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

Re: [Pharo-users] [ANN] Pharo Launcher v1.2 release

by Christophe Demarey

> Le 19 juin 2018 Ã 16:28, Serge Stinckwich <serge.stinckwich(a)gmail.com> a Ã©crit : > > Thank you Christophe for your work ! > I really appreciate it. > > I dl the 64 bits VM for macOS. Everytime I run a 32 bits image, I have a warning that using a 32 bits images, require a 32 bits VM. > And then when I select yes, everything works. Why having this warning everytime ? I added this warning so that people are aware that they use 32-bit images on a 64-bit system. We are moving to mostly 64-bit images. The biggest concern for this warning was raised by a Linux user: he installed a 64-bit Pharo Launcher and was surprised to not be able to launch 32-bit images. Indeed, on linux, you need additional set up (i.e. install 32-bit libraries) to be able to launch 32-bit images. I understand thi warning could be annoying. Maybe I should add a setting to ignore these warnings? Would it be enough? Or should I only warn on Linux where it is really important? But in this case, people could may not be aware of using 32 or 64 bits images. Could you open an issue for that?

June 20, 2018

Re: [Pharo-users] Cargo

by Esteban Lorenzano

hi, (this is more pharo-dev) > On 20 Jun 2018, at 08:55, Norbert Hartl <norbert(a)hartl.name> wrote: > > Here comes my every-no-and-then-inquiry of the status of cargo. Is it in pharo7? Is it usable? 1. no 2. so-so :P and Christophe will provide a better answer, for sure :) cheers! Esteban > > Norbert >

June 20, 2018

Re: [Pharo-users] How to contribute to Calypso when it relies on pharo-core editors?

by Guillermo Polito

Hi Tim, Yes, there you're experiencing the limits of our current process. We were studying the usage of git subtrees/submodules/subrepos but none of them seem a satisfying solution for what would give us a smooth contribution process. Now, we can enhance a bit the current status by adding calypso in the list of iceberg projects. I agree with this. Actually putting Pharo and Iceberg itself there is something we started to do slowly. There was this feeling that people would complain "agh but I only want to see my projects not the system ones". What I believe is that we are used to see and change all packages in the system, that's in our "blood" as pharoers. So seeing all loaded projects may confuse a bit newcomers but empower experts too... Also, to answer your question about compatibility in Pharo6/7, or even different Pharo7 versions, what I'd say is that the best way to do it is to keep backwards compatibility when possible. Instead of removing/renaming classes or methods, deprecate them. I'm aware that this is not always possible, so trust your criteria. Guille On Wed, Jun 20, 2018 at 3:45 AM Tim Mackinnon <tim(a)testit.works> wrote: > Thinking about this more - why doesnât Calypso appear in iceberg as a > separate project alongside iceberg and Pharo? > > Thatâs whatâs confusing? And how did it get loaded from itâs git project > without it appearing? > > Which all makes me think there might need to be an iceberg setting - > show/hide system projects so they donât get in the way of your own > projects. > > But then if you accidentally save a method in a system class - how are we > going to spit it and know? > > I hate getting burned when you thought you were on a roll > > Tim > > Sent from my iPhone > > > On 20 Jun 2018, at 02:26, Tim Mackinnon <tim(a)testit.works> wrote: > > > > Hi - so in trying to improve the sendersof/implementors of - I thought I > had nailed it (and got working what I had done in Pharo 6 for Pharo 7) - > but when I loaded my commit into a fresh image I realised that none of the > (minor) changes I had made to Calypso had been committed. > > > > This is actually quite confusing - and its take me a while to realise > that Calypso is a separate project and so when I picked commit on Pharo - > this wonât pick up any of the changes in Calypsoâ¦. Arrrgggg > > > > So now Iâm guessing that I have to follow the same steps that I followed > for loading a pharo repo - for Calypso? > > > > But then if I do this - and I propose some fixes to Calypso - how can it > work, as it relies on some changes to older pharo core editors that its > inserting from? > > > > My changes without Calypso will work (they did in V6) - but then how can > someone test those in V7 as Calypso is then the default variable. > > > > Iâm in a bit of a twist - how can I proceed? > > > > Iâd really like to help improve the situation - as its bugged me for > years that its a pain looking stuff up quickly (requiring you to highlight > just the right stuff for very obvious things) > > > > Tim > > > -- 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

June 20, 2018

Cargo

by Norbert Hartl

Here comes my every-no-and-then-inquiry of the status of cargo. Is it in pharo7? Is it usable? Norbert

June 20, 2018

Re: [Pharo-users] [Moose-dev] [ann] gt documenter

by Tim Mackinnon

Actually I realised it ended up on the be moose forum - hereâs what Doru replied (for any lurkers) Sent from my iPhone > On Jun 18, 2018, at 1:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > > Guys this is really impressive! Thanks. > 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - > > 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) Show Quoted Content > 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - > > 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) Ok. > 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? Indeed, this is due to the fact that loading GToolkitDocumenter does not load GToolkitVisualizer which includes GtMondrian. We are still working on finding the right dependencies balance. Until then, please load the whole GToolkit to get the full support. > 3) You canât scroll the Diff tabs of results, only the Code tabs Good catch! Cheers, Doru Sent from my iPhone > On 20 Jun 2018, at 02:47, Tim Mackinnon <tim(a)testit.works> wrote: > > Bump (not sure this got through , and keen to know how to load the diagramming bit) > > Guys this is really impressive! > > 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - > > 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) > > 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? > 3) You canât scroll the Diff tabs of results, only the Code tabs > > Tim > >> On 13 Jun 2018, at 21:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: >> https://github.com/feenkcom/gtoolkit-documenter >> >> Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. >> >> Attached you can see a preview of how documents look like: >> >> <gt-documenter.png> >> >> At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: >> â¢ code documentation >> â¢ tutorials >> â¢ interactive data notebook >> >> >> Code documentation >> ---- >> Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: >> https://twitter.com/feenkcom/status/973899862482866176 >> >> You can see a live example of documentation by inspecting the following snippet: >> GtDocumenter editorForText: BrToggleExamples comment. >> >> >> Tutorials: >> ---- >> Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: >> https://twitter.com/feenkcom/status/999975333972541440 >> >> The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. >> >> The size of the preview can also be adjusted live: >> https://twitter.com/feenkcom/status/1001152789874167808 >> https://twitter.com/feenkcom/status/1001407762285375490 >> >> You can see a live tutorial by inspecting: >> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. >> >> >> Interactive data notebook: >> ---- >> A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: >> â¢ it supports defining variables in code snippets, and >> â¢ the execution of code shows an embedded inspector. >> >> For example: >> https://twitter.com/feenkcom/status/996310432225820672 >> https://twitter.com/feenkcom/status/1002851190475026432 >> >> An example, can be seen by inspecting: >> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. >> >> >> As always, please do let us know what you think. >> >> Enjoy, >> The feenk team >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "If you can't say why something is relevant, >> it probably isn't." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev >

June 20, 2018

Re: [Pharo-users] [Moose-dev] [ann] gt documenter

by Tim Mackinnon

Bump (not sure this got through , and keen to know how to load the diagramming bit) Guys this is really impressive! 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? 3) You canât scroll the Diff tabs of results, only the Code tabs Tim > On 13 Jun 2018, at 21:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: > https://github.com/feenkcom/gtoolkit-documenter > > Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. > > Attached you can see a preview of how documents look like: > > <gt-documenter.png> > > At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: > â¢ code documentation > â¢ tutorials > â¢ interactive data notebook > > > Code documentation > ---- > Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: > https://twitter.com/feenkcom/status/973899862482866176 > > You can see a live example of documentation by inspecting the following snippet: > GtDocumenter editorForText: BrToggleExamples comment. > > > Tutorials: > ---- > Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: > https://twitter.com/feenkcom/status/999975333972541440 > > The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. > > The size of the preview can also be adjusted live: > https://twitter.com/feenkcom/status/1001152789874167808 > https://twitter.com/feenkcom/status/1001407762285375490 > > You can see a live tutorial by inspecting: > IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. > > > Interactive data notebook: > ---- > A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: > â¢ it supports defining variables in code snippets, and > â¢ the execution of code shows an embedded inspector. > > For example: > https://twitter.com/feenkcom/status/996310432225820672 > https://twitter.com/feenkcom/status/1002851190475026432 > > An example, can be seen by inspecting: > IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. > > > As always, please do let us know what you think. > > Enjoy, > The feenk team > > > -- > www.tudorgirba.com > www.feenk.com > > "If you can't say why something is relevant, > it probably isn't." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

June 20, 2018

Re: [Pharo-users] How to contribute to Calypso when it relies on pharo-core editors?

by Tim Mackinnon

Thinking about this more - why doesnât Calypso appear in iceberg as a separate project alongside iceberg and Pharo? Thatâs whatâs confusing? And how did it get loaded from itâs git project without it appearing? Which all makes me think there might need to be an iceberg setting - show/hide system projects so they donât get in the way of your own projects. But then if you accidentally save a method in a system class - how are we going to spit it and know? I hate getting burned when you thought you were on a roll Tim Sent from my iPhone > On 20 Jun 2018, at 02:26, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - so in trying to improve the sendersof/implementors of - I thought I had nailed it (and got working what I had done in Pharo 6 for Pharo 7) - but when I loaded my commit into a fresh image I realised that none of the (minor) changes I had made to Calypso had been committed. > > This is actually quite confusing - and its take me a while to realise that Calypso is a separate project and so when I picked commit on Pharo - this wonât pick up any of the changes in Calypsoâ¦. Arrrgggg > > So now Iâm guessing that I have to follow the same steps that I followed for loading a pharo repo - for Calypso? > > But then if I do this - and I propose some fixes to Calypso - how can it work, as it relies on some changes to older pharo core editors that its inserting from? > > My changes without Calypso will work (they did in V6) - but then how can someone test those in V7 as Calypso is then the default variable. > > Iâm in a bit of a twist - how can I proceed? > > Iâd really like to help improve the situation - as its bugged me for years that its a pain looking stuff up quickly (requiring you to highlight just the right stuff for very obvious things) > > Tim

June 20, 2018

How to contribute to Calypso when it relies on pharo-core editors?

by Tim Mackinnon

Hi - so in trying to improve the sendersof/implementors of - I thought I had nailed it (and got working what I had done in Pharo 6 for Pharo 7) - but when I loaded my commit into a fresh image I realised that none of the (minor) changes I had made to Calypso had been committed. This is actually quite confusing - and its take me a while to realise that Calypso is a separate project and so when I picked commit on Pharo - this wonât pick up any of the changes in Calypsoâ¦. Arrrgggg So now Iâm guessing that I have to follow the same steps that I followed for loading a pharo repo - for Calypso? But then if I do this - and I propose some fixes to Calypso - how can it work, as it relies on some changes to older pharo core editors that its inserting from? My changes without Calypso will work (they did in V6) - but then how can someone test those in V7 as Calypso is then the default variable. Iâm in a bit of a twist - how can I proceed? Iâd really like to help improve the situation - as its bugged me for years that its a pain looking stuff up quickly (requiring you to highlight just the right stuff for very obvious things) Tim

June 20, 2018

Re: [Pharo-users] Nice catchy video for covering Pharo capability

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 19/06/18 17:13, Andrei Stebakov wrote: > Could you suggest a nice video for a presentation to showcase Pharo as > a nice language for data visualization? > > Thanks, > Andrei > I like the video Software as a Graph[1], which inspired me to do Grafoscopio[2]. Some blog post (not in video format) show the capabilities of Pharo as a data storytelling and visualization platform for reproducible publishing and research and can be found in [3] and [4]. [1] https://vimeo.com/94724841 [2] http://mutabit.com/grafoscopio/index.en.html [3] http://mutabit.com/offray/blog/en/entry/sdv-infomed [4] http://mutabit.com/offray/blog/en/entry/ds-twitter-mockup Hope this helps, Offray

June 19, 2018

Nice catchy video for covering Pharo capability

by Andrei Stebakov

Could you suggest a nice video for a presentation to showcase Pharo as a nice language for data visualization? Thanks, Andrei

June 19, 2018