- Pharo-users - lists.pharo.org

Re: [Pharo-users] Refactor without formatting

by Guillermo Polito

Hi, > El 20 may 2020, a las 1:54, Ben Coman <btc(a)openinworld.com> escribiÃ³: > > That seems to violate the Principal Of Least Surprise. Yes, I happen to also not like that behaviour :( > Whether or not it ends up getting changed, I think its worthwhile entering that directly in the issue tracker. > It would assist if you could bisect to isolate which commit introduced the behaviour. Opening an issue is a good start. I also wonder, I think refactorings work like this since the beginning? But if it was introduced at some point, it should be nice to know if it can be easily reverted. Also, refactorings DO need to rebuild the source code after refactoring, so maybe there are some cases where maintaining the old formatting is difficult? > > cheers -ben > > On Wed, 20 May 2020 at 01:34, Vitor Medina Cruz <vitormcruz(a)gmail.com <mailto:vitormcruz@gmail.com>> wrote: > Hello, > > When I run a refactoring, Rename Method, for example, the refactoring is reformatting the code affected. Is it possible to configure Pharo to refactor without reformatting code? Depending on the refactoring, the reformat is so intrusive that make it more worth to make the refactoring by hand. > > Regards, > Vitor

May 20, 2020

Re: [Pharo-users] Siren 9.0 Released

by Richard O'Keefe

Cincom still has a "Personal Use Licence". http://www.cincomsmalltalk.com/main/community/product-portal/trying-cincom-… I am running vw8.3pul, and file ~/vw8.3pul/bin/linuxx86_64/visual /home/ok/vw8.3pul/bin/linuxx86_64/visual: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9, stripped it is 64-bit. The paid version of VW is up to 9.0, but 8.3 works for me. On Fri, 15 May 2020 at 08:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks Steven this is cool to see that Siren is living and kicking. > Last year I was browsing the old site and I was sad because I thought it > was dead. > Your OSC looks better than the one in Pharo even if we used it > successfully to connect interactive tables with a HCI research group. > > If you need help to migrate from VW let us know because it would be great > to have Siren working in Pharo. > I did not see any Unit tests and the tests saved us when we migrated > Moose. Sometimes we even only kept them because they were > better than the implementation. It took us around six months and we got > free :) > And we have some contacts that would be interested in London. We could put > you in contact. > > Now just some questions and you may know the answer so I ask > > I was thinking but I may be totally wrong that it was forbidden to give VW > images and that the current license > was for personal use only. Long time ago the shrink process was removing > the compiler. Now I saw that your image is 42mb. > > Personally I do not want to download any VisualWorks distribution and sign > their licenses because I want to stay cristal clear > on ANY license and possible issues. I did not look at Visualworks since > 2008 and I feel clean and I will stay like that. > > So I imagine that Iâm not allowed to use your software. Iâm not good in > music sadly so there is no frustration from my side. > > You mention that people can use a non-commercial version of VW but this > license does not exist anymore. > Is there a 64 bits version of VW because VW7.5 starts to show its age and > on recent mac you only have 64 bits. > > > Some people may think that we are just over the top on open-source but > this is not by accident that we took the responsibility to create Pharo. > We could not distribute Moose our open-source platform so after 10 years > of hard work we had to do something. And we created Pharo. > And the problem we got were with the previous version (the non commercial) > of the Cincom license and the new one is even more restrictive. > Some friends of mine told me that some lawyers were starting to get picky > and send letters around. > So watch out. > > BTW I did not see the license of Siren on the git repo. If I may suggest > one, > BSD/MIT are nice, avoid GPL because it means that nobody serious on > Smalltalk will ever look at your system and contribute. > > S. > > On 14 May 2020, at 01:40, stephen(a)heaveneverywhere.com wrote: > > > Hello all, > > The Siren system is a general-purpose framework for music and sound > composition, processing, performance, and analysis; it is a collection of > about 350 classes written in Smalltalk-80 (40 kLOC or so). Siren 9.0 works > on VisualWorks Smalltalk (though the bulk has been ported to other dialects > as well); Siren supports streaming I/O via OpenSoundControl (OSC), MIDI, > and multi-channel audio ports. The Siren release is available via the web > from the URL http://FASTLabInc.com/Siren <http://fastlabinc.com/Siren>. > > Siren is a programming framework and tool kit; the intended audience is > Smalltalk developers, or users willing to learn Smalltalk in order to write > their own applications. The built-in applications are meant as > demonstrations of the use of the libraries, rather than as end-user > applications. Siren is not a MIDI sequencer, nor a score notation editor, > through both of these applications would be easy to implement with the > Siren framework. > > There are several elements to Siren: > > * the Smoke music representation language (music magnitudes, events, event > lists, generators, functions, and sounds); > > * voices, schedulers and I/O drivers (real-time and file-based voices, > sound, score file, OSC, and MIDI I/O); > > * user interface components for musical applications (UI framework, tools, > and widgets); > > * several built-in applications (editors and browsers for Smoke objects); > and > > * external library interfaces for streaming I/O and DSP math (sound/MIDI > I/O, fast FFT, CSL & Loris sound analysis/resynthesis packages ) > > The best in-depth doc (book chapter) is in, > http://FASTLabInc.com/Siren/Doc/SirenBookChapter.pdf > <http://fastlabinc.com/Siren/Doc/SirenBookChapter.pdf> > > The read the demo code workbook (this text), go to, > http://FASTLabInc.com/Siren/Siren7.5.Workbook.html > <http://fastlabinc.com/Siren/Siren7.5.Workbook.html> > or > http://FASTLabInc.com/Siren/Siren7.5.Workbook.pdf > <http://fastlabinc.com/Siren/Siren7.5.Workbook.pdf> > > If you like to read manuals, take a look at, > http://FASTLabInc.com/Siren/Manual <http://fastlabinc.com/Siren/Manual> > > or watch the detailed Siren demo at, > https://vimeo.com/120751122 > > The links to get Siren9 are, > > Web site: http://fastlabinc.com/Siren > > Package download: http://fastlabinc.com/Siren/Siren_9.0.zip > > Github repo: https://github.com/stpope/Siren9 > > > Comments solicited. > > Stephen Pope > > > -- > > Stephen Travis Pope Santa Barbara, California, USA > > <pastedGraphic.tiff> http://HeavenEverywhere.com > <http://heaveneverywhere.com/> http://FASTLabInc.com > <http://fastlabinc.com/> > https://vimeo.com/user19434036/videos *http://heaveneverywhere.com/Reflections > <http://heaveneverywhere.com/Reflections>* > > -- > > > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

May 20, 2020

Re: [Pharo-users] Siren 9.0 Released

by Todd Blanchard

It is interesting to see that Siren uses PortAudio. I was considering to recommend adopting it for Pharo in the other sound thread. It has been used in a lot of projects, but I am a little concerned it has not been recently updated. http://www.portaudio.com > On May 14, 2020, at 1:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Thanks Steven this is cool to see that Siren is living and kicking. > Last year I was browsing the old site and I was sad because I thought it was dead. > Your OSC looks better than the one in Pharo even if we used it successfully to connect interactive tables with a HCI research group. > > If you need help to migrate from VW let us know because it would be great to have Siren working in Pharo. > I did not see any Unit tests and the tests saved us when we migrated Moose. Sometimes we even only kept them because they were > better than the implementation. It took us around six months and we got free :) > And we have some contacts that would be interested in London. We could put you in contact. > > Now just some questions and you may know the answer so I ask > > I was thinking but I may be totally wrong that it was forbidden to give VW images and that the current license > was for personal use only. Long time ago the shrink process was removing the compiler. Now I saw that your image is 42mb. > > Personally I do not want to download any VisualWorks distribution and sign their licenses because I want to stay cristal clear > on ANY license and possible issues. I did not look at Visualworks since 2008 and I feel clean and I will stay like that. > > So I imagine that Iâm not allowed to use your software. Iâm not good in music sadly so there is no frustration from my side. > > You mention that people can use a non-commercial version of VW but this license does not exist anymore. > > Is there a 64 bits version of VW because VW7.5 starts to show its age and on recent mac you only have 64 bits. > > > Some people may think that we are just over the top on open-source but this is not by accident that we took the responsibility to create Pharo. > We could not distribute Moose our open-source platform so after 10 years of hard work we had to do something. And we created Pharo. > And the problem we got were with the previous version (the non commercial) of the Cincom license and the new one is even more restrictive. > Some friends of mine told me that some lawyers were starting to get picky and send letters around. > So watch out. > > BTW I did not see the license of Siren on the git repo. If I may suggest one, > BSD/MIT are nice, avoid GPL because it means that nobody serious on Smalltalk will ever look at your system and contribute. > > S. > >> On 14 May 2020, at 01:40, stephen(a)heaveneverywhere.com <mailto:stephen@heaveneverywhere.com> wrote: >> >> >> Hello all, >> >> The Siren system is a general-purpose framework for music and sound composition, processing, performance, and analysis; it is a collection of about 350 classes written in Smalltalk-80 (40 kLOC or so). Siren 9.0 works on VisualWorks Smalltalk (though the bulk has been ported to other dialects as well); Siren supports streaming I/O via OpenSoundControl (OSC), MIDI, and multi-channel audio ports. The Siren release is available via the web from the URL http://FASTLabInc.com/Siren <http://fastlabinc.com/Siren>. >> >> Siren is a programming framework and tool kit; the intended audience is Smalltalk developers, or users willing to learn Smalltalk in order to write their own applications. The built-in applications are meant as demonstrations of the use of the libraries, rather than as end-user applications. Siren is not a MIDI sequencer, nor a score notation editor, through both of these applications would be easy to implement with the Siren framework. >> >> There are several elements to Siren: >> >> * the Smoke music representation language (music magnitudes, events, event lists, generators, functions, and sounds); >> >> * voices, schedulers and I/O drivers (real-time and file-based voices, sound, score file, OSC, and MIDI I/O); >> >> * user interface components for musical applications (UI framework, tools, and widgets); >> >> * several built-in applications (editors and browsers for Smoke objects); and >> >> * external library interfaces for streaming I/O and DSP math (sound/MIDI I/O, fast FFT, CSL & Loris sound analysis/resynthesis packages ) >> >> The best in-depth doc (book chapter) is in, >> http://FASTLabInc.com/Siren/Doc/SirenBookChapter.pdf <http://fastlabinc.com/Siren/Doc/SirenBookChapter.pdf> >> >> The read the demo code workbook (this text), go to, >> http://FASTLabInc.com/Siren/Siren7.5.Workbook.html <http://fastlabinc.com/Siren/Siren7.5.Workbook.html> >> or >> http://FASTLabInc.com/Siren/Siren7.5.Workbook.pdf <http://fastlabinc.com/Siren/Siren7.5.Workbook.pdf> >> >> If you like to read manuals, take a look at, >> http://FASTLabInc.com/Siren/Manual <http://fastlabinc.com/Siren/Manual> >> >> or watch the detailed Siren demo at, >> https://vimeo.com/120751122 <https://vimeo.com/120751122> >> >> The links to get Siren9 are, >> >> Web site: http://fastlabinc.com/Siren <http://fastlabinc.com/Siren> >> >> Package download: http://fastlabinc.com/Siren/Siren_9.0.zip <http://fastlabinc.com/Siren/Siren_9.0.zip> >> >> Github repo: https://github.com/stpope/Siren9 <https://github.com/stpope/Siren9> >> >> >> Comments solicited. >> >> Stephen Pope >> >> >> -- >> >> Stephen Travis Pope Santa Barbara, California, USA >> <pastedGraphic.tiff> http://HeavenEverywhere.com <http://heaveneverywhere.com/> http://FASTLabInc.com <http://fastlabinc.com/> >> https://vimeo.com/user19434036/videos <https://vimeo.com/user19434036/videos> http://heaveneverywhere.com/Reflections <http://heaveneverywhere.com/Reflections> >> >> -- >> >> >> > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

May 20, 2020

Re: [Pharo-users] New user

by Vince Refiti

Hi I prefer to clone every repo I use locally. I just did this with Seaside and then used Iceberg to load it into a new Pharo8 image and it worked. Vince From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Vitor Medina Cruz Sent: Wednesday, 20 May 2020 12:27 PM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] New user EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hello, I feel your pain. Updated, consistent and centralized documentation is not strong in Pharo. Things are changing fast and docs don't catch up, also there is an effort to move projects to github, so usually updated stuff are there. I never use Catalog anymore because often things goes wrong. Books are only good to explain major concepts that are less likely to change over time, in order to getting started I would recommend: 1- Seaside github project: https://github.com/SeasideSt/Seaside<https://urldefense.com/v3/__https:/github.com/SeasideSt/Seaside__;!!I_DbfM1…>. Their readme and wiki page seems to be very good and updated, I just evaluated this on playground and it worked as expected: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:v3.4.1/repository'; load I avoid using master tag as it is usually development branch or frequently has some commit that breaks everything up and and what I want is something reliable, so I always use version tags (when the projects provides one). After that, I think using the wiki (https://github.com/SeasideSt/Seaside/wiki<https://urldefense.com/v3/__https:/github.com/SeasideSt/Seaside/wiki__;!!I_…>) or seaside web book (http://book.seaside.st/book<https://urldefense.com/v3/__http:/book.seaside.st/book__;!!I_DbfM1H!WXIAvRa…>) can get you through all you need to know. 2- Pharo open documentation is a much better place to be getting started with Pharo: https://github.com/pharo-open-documentation/pharo-wiki<https://urldefense.com/v3/__https:/github.com/pharo-open-documentation/phar…> 3- Then you can go and read Pharo by Example and Deep in Pharo books in order to get more information after you can get started, if you are interest, but by now you must be able to do most basic stuff with the system.. Hope that helps you getting by and fuel you interest in Smalltalk and Pharo. Regars, Vitor On Tue, May 19, 2020 at 7:38 PM G B via Pharo-users <pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org>> wrote: I am new to Pharo and liked that it is a cleaned up and modern Smalltalk, but I think I'm done before I ever started. My biggest interest was in Seaside, yet trying to install it from instructions on the Seaside GitHub fails: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load Trying to load packages from the catalog browser like Magritte fails. Some packages aren't updated for 8.0 and are only available for 7.0. Some are only available for 4.0. Trying to follow the book for creating a blog has ha me spend time trying to get something going to no avail. I'm not an expert programmer, but I've been in IT for 25 years and can do some C, Racket, Pascal, shell languages, awk, Perl, but I am stymied at every turn with Pharo.

May 20, 2020

Re: [Pharo-users] New user

by Ben Coman

Something I'm not quite sure on, is whether using repository: 'github://....'rather than a HTTPS connection requires SSH keys to set up. Presuming so, you should first ensure you SSH is working from the command lineper... https://help.github.com/en/github/authenticating-to-github/testing-your-ssh… think a facility to do a similar user-check from within Pharo would be extremely useful.) Next, if you are on Windows, the added complexity is that "Use Custom Keys" must be enabled.(And it would be useful if that was the default for Windows. I trip over it _every_ time I start a new image.) [image: image.png] cheers -ben On Wed, 20 May 2020 at 06:38, G B via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > I am new to Pharo and liked that it is a cleaned up and modern Smalltalk, > but I think I'm done before I ever started. My biggest interest was in > Seaside, yet trying to install it from instructions on the Seaside GitHub > fails: > > Metacello new > baseline:'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load > > Trying to load packages from the catalog browser like Magritte fails. Some > packages aren't updated for 8.0 and are only available for 7.0. Some are > only available for 4.0. Trying to follow the book for creating a blog has > ha me spend time trying to get something going to no avail. > > I'm not an expert programmer, but I've been in IT for 25 years and can do > some C, Racket, Pascal, shell languages, awk, Perl, but I am stymied at > every turn with Pharo. > > >

May 20, 2020

Re: [Pharo-users] New user

by Vitor Medina Cruz

Hello, I feel your pain. Updated, consistent and centralized documentation is not strong in Pharo. Things are changing fast and docs don't catch up, also there is an effort to move projects to github, so usually updated stuff are there. I never use Catalog anymore because often things goes wrong. Books are only good to explain major concepts that are less likely to change over time, in order to getting started I would recommend: 1- Seaside github project: https://github.com/SeasideSt/Seaside. Their readme and wiki page seems to be very good and updated, I just evaluated this on playground and it worked as expected: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:v3.4.1/repository'; load I avoid using master tag as it is usually development branch or frequently has some commit that breaks everything up and and what I want is something reliable, so I always use version tags (when the projects provides one). After that, I think using the wiki ( https://github.com/SeasideSt/Seaside/wiki) or seaside web book ( http://book.seaside.st/book) can get you through all you need to know. 2- Pharo open documentation is a much better place to be getting started with Pharo: https://github.com/pharo-open-documentation/pharo-wiki 3- Then you can go and read Pharo by Example and Deep in Pharo books in order to get more information after you can get started, if you are interest, but by now you must be able to do most basic stuff with the system.. Hope that helps you getting by and fuel you interest in Smalltalk and Pharo. Regars, Vitor On Tue, May 19, 2020 at 7:38 PM G B via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > I am new to Pharo and liked that it is a cleaned up and modern Smalltalk, > but I think I'm done before I ever started. My biggest interest was in > Seaside, yet trying to install it from instructions on the Seaside GitHub > fails: > > Metacello new > baseline:'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load > > Trying to load packages from the catalog browser like Magritte fails. Some > packages aren't updated for 8.0 and are only available for 7.0. Some are > only available for 4.0. Trying to follow the book for creating a blog has > ha me spend time trying to get something going to no avail. > > I'm not an expert programmer, but I've been in IT for 25 years and can do > some C, Racket, Pascal, shell languages, awk, Perl, but I am stymied at > every turn with Pharo. > > >

May 20, 2020

Re: [Pharo-users] Refactor without formatting

by Ben Coman

That seems to violate the Principal Of Least Surprise. Whether or not it ends up getting changed, I think its worthwhile entering that directly in the issue tracker. It would assist if you could bisect to isolate which commit introduced the behaviour. cheers -ben On Wed, 20 May 2020 at 01:34, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Hello, > > When I run a refactoring, Rename Method, for example, the refactoring is > reformatting the code affected. Is it possible to configure Pharo to > refactor without reformatting code? Depending on the refactoring, the > reformat is so intrusive that make it more worth to make the refactoring by > hand. > > Regards, > Vitor >

May 19, 2020

New user

by G B

I am new to Pharo and liked that it is a cleaned up and modern Smalltalk, but I think I'm done before I ever started.Â My biggest interest was in Seaside, yet trying to install it from instructions on the Seaside GitHub fails: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load Trying to load packages from the catalog browser like Magritte fails. Some packages aren't updated for 8.0 and are only available for 7.0.Â Some are only available for 4.0.Â Trying to follow the book for creating a blog has ha me spend time trying to get something going to no avail. I'm not an expert programmer, but I've been in IT for 25 years and can do some C, Racket, Pascal, shell languages, awk, Perl, but I am stymied at every turn with Pharo.

May 19, 2020

Re: [Pharo-users] Pharo-Sound

by Russ Whaley

The repository browser did not list PharoSound - at least in an obvious place :) so I couldn't unload it. I created a new image - spent two hours getting Git/Iceberg working (personal problems, I guess - character flaw that this is so difficult for me). But my new image is only 70MB. My old image was 270MB. So I guess it doesn't matter how to unload PharoSound as I now have a new image... Thanks! Russ On Thu, May 14, 2020 at 9:56 AM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > > On 14 May 2020, at 15:44, Russ Whaley <whaley.russ(a)gmail.com> wrote: > > Okay, so I may just have a compatibility issue w/v8, I suppose. The > suggestions on external audio, etc., are great - and a future need for me > for sure, but right now, I'd settle for a beep :) - as I'm having troubles > (another post on Spec2) updating my display with a 'Correct' or 'Incorrect' > - between normal refreshes... so I just wanted an audible beep to let me > know things were working. I created a Logger class where I can log and see > (in the log) that all the functional code is getting processed properly - I > just can't seem to get it to the display. > > I may try the FFI route - but it looks to be quite a bit more than I need > right now. > > Is there a way to completely remove the PharoSound 'package'? It's > possible, with me trying to figure out how to use it, I ran something that > disabled it in my version. Reloading it didn't help, but perhaps if I > could get it completely deleted? > > > go the repository browser, select it and press unload. > > S/ > > > Thanks all! > Russ > > On Thu, May 14, 2020 at 9:36 AM StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Hi russ >> >> I do not know if the catalog is referring the latest version but in >> anycase the plugins are all using old libraries and do not really work >> anymore (because not >> available anymore). >> >> We were discussing monday about it and to propose a binding to more >> recent libraries such as openAV >> We need help there. >> >> S. >> >> On 13 May 2020, at 20:49, Russ Whaley <whaley.russ(a)gmail.com> wrote: >> >> I'm using Pharo 8 stable (64bit) version. >> >> I pulled PharoSound from the Catalog and installed. Installed fine, no >> errors. >> >> I went to the comments on the abstract class. Copied the examples to the >> Playground, ran them - worked fine (although I don't know how to stop the >> dang PluckedString example!!)... I digress :) >> >> I created my own subclass to play specific sounds at certain events in my >> application. Worked well. A day later - I have no sound in my image at >> all now. Nothing works. I reinstalled from the Catalog. Ran the code >> listed in the AbstractSound comments - nothing. >> >> I installed a new Pharo 8 stable 64-bit image - pulled PharoSound in, >> copied the sampe code from AbstractSound comments... and it worked just >> fine. >> >> Any ideas how I can get sound to work again on my original image? For >> me, it is a real pain to try and migrate all my code over to a new image. >> It is apparently a character flaw on my part, but it takes me hours to get >> Git/Iceberg working properly on a new image. (yes, I'm ashamed). I see a >> new book on the topic, but I had been following that book while it was wip, >> and Git/Iceberg just whips my butt. But if going to a new image is the >> solution, I'll try, try again. >> >> What do you think? >> >> Thanks, >> Russ >> >> -- >> Russ Whaley >> whaley.russ(a)gmail.com >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >> > > -- > Russ Whaley > whaley.russ(a)gmail.com > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > -- Russ Whaley whaley.russ(a)gmail.com

May 19, 2020

Pharo on Chromebook

by Jan KurÅ¡

Hi, has anyone an experience with running Pharo on Chromebook (using Crostini)? It worked reasonably well for me in the past (3 months ago), now I see rendering issues: [image: image.png] I tried with latest and greatest Pharo8 and fresh image, I see the same rendering issue. Thanks, Jan

May 19, 2020