- Pharo-users - lists.pharo.org

Re: [Pharo-users] Deleting images / saving as - in Pharo Launcher auncher

by StÃ©phane Ducasse

> On 14 May 2020, at 23:20, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi CÃ©drick, > >> Le 7 mai 2020 Ã 08:24, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : >> >> Hi Christophe, >> >> >> This version is definitely cooler :) > > Thanks > >> I just wander as for the previous version why deleting image can take some time, whereas itâs quick to delete the image repository. Is it normal ? > > In Pharo, deleting files is slow because Pharo visits all the files to delete to check if there are file descriptors opened on these files to close them. > I think it is something that could be improved. In many situations, you know you do not have descriptors on these files and we could have a method to delete without doing the check, just the system call, without visiting the tree. + 1 Yes we should introduce a massiveFolder delete. > >> Another thing that might help my way of doing things. I like to "save as" the image so as to have a quick check point, and the launcher is not Â« friendly Â» with renaming as it loads the default image. >> >> Any idea on how to integrate that ? Maybe having a list of images that pops-up ? > > For this feature, I have no good idea for now. > I had in mind to use a tree instead of a list of images. You could expand if there are more than one image and see other images in the folder. > The problem is for the metadata file: we could assume that other images should use the same metadata as the core image and use them to run the image. (For now, the metadata filename is the same for all images). > >> I actually changed once the "save as Â» in a Â« save checkpoint charly Â» where it saves a copy but still load the default name. Might be an option ? :) > > Â« Saves a copy Â» : do you mean you copy the full folder to another name ? > > Cheers, > Christophe -------------------------------------------- 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 15, 2020

Re: [Pharo-users] Covid-19 Tracker with PharoJS

by Guillermo Polito

Itâs cool! > El 14 may 2020, a las 17:37, Noury Bouraqadi <bouraqadi(a)gmail.com> escribiÃ³: > > Hi, > > Dave Mason did implement a COVID-19 tracker with PharoJS. > https://covid.cs.ryerson.ca/compare/ <https://covid.cs.ryerson.ca/compare/> > > Noury

May 15, 2020

Re: [Pharo-users] git and Pharo new book...

by StÃ©phane Ducasse

Thanks! S > On 15 May 2020, at 03:50, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > I already start to send PRs to fix typos. > > > > On Thu, May 14, 2020 at 9:55 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > if you want to contribute to a chapter on other than github solutions. > I would be happy to help editing such chapter. > > If you want to you can do a PR with a chapter. > > S > >> On 14 May 2020, at 03:22, Pierce Ng <pierce(a)samadhiweb.com <mailto:pierce@samadhiweb.com>> wrote: >> >> On Wed, May 13, 2020 at 11:07:00AM -0500, Offray Vladimir Luna CÃ¡rdenas wrote: >>> This is perfect timing, as I have started to slowly migrate my own repos >>> from SmalltalkHub to a simple, self hosted and self contained Gitea[1] >> >> Hi Offray, >> >> I run Gitea on a Raspberry Pi at home. I have a couple of scripts that >> back up the Gitea data, encrypt the backup with GPG, then uploads >> somewhere. Happy to share if you want them. >> >> On the topic, Iceberg works fine with Gitea. My SOP as follows: >> >> - create repo using Gitea web interface >> - using command line, clone locally via ssh >> - using command line, 'git remote add ...' >> >> Then in Iceberg use the local clone. >> >> Pierce >> >> > > -------------------------------------------- > 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 > > > > -- > Serge Stinckwicâhâ > https://twitter.com/SergeStinckwich <https://twitter.com/SergeStinckwich> > â -------------------------------------------- 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 15, 2020

Re: [Pharo-users] git and Pharo new book...

by Serge Stinckwich

I already start to send PRs to fix typos. On Thu, May 14, 2020 at 9:55 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > if you want to contribute to a chapter on other than github solutions. > I would be happy to help editing such chapter. > > If you want to you can do a PR with a chapter. > > S > > On 14 May 2020, at 03:22, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Wed, May 13, 2020 at 11:07:00AM -0500, Offray Vladimir Luna CÃ¡rdenas > wrote: > > This is perfect timing, as I have started to slowly migrate my own repos > from SmalltalkHub to a simple, self hosted and self contained Gitea[1] > > > Hi Offray, > > I run Gitea on a Raspberry Pi at home. I have a couple of scripts that > back up the Gitea data, encrypt the backup with GPG, then uploads > somewhere. Happy to share if you want them. > > On the topic, Iceberg works fine with Gitea. My SOP as follows: > > - create repo using Gitea web interface > - using command line, clone locally via ssh > - using command line, 'git remote add ...' > > Then in Iceberg use the local clone. > > Pierce > > > > -------------------------------------------- > 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 > > -- Serge Stinckwic âhâ https://twitter.com/SergeStinckwich â

May 15, 2020

Re: [Pharo-users] git and Pharo new book...

by Pierce Ng

On Thu, May 14, 2020 at 03:54:31PM +0200, StÃ©phane Ducasse wrote: > if you want to contribute to a chapter on other than github solutions. > I would be happy to help editing such chapter. > > If you want to you can do a PR with a chapter. Sure, I'll do that. I'll start next month Jun 2020. Pierce

May 15, 2020

Re: [Pharo-users] Deleting images / saving as - in Pharo Launcher auncher

by Christophe Demarey

Hi CÃ©drick, > Le 7 mai 2020 Ã 08:24, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > > Hi Christophe, > > > This version is definitely cooler :) Thanks > I just wander as for the previous version why deleting image can take some time, whereas itâs quick to delete the image repository. Is it normal ? In Pharo, deleting files is slow because Pharo visits all the files to delete to check if there are file descriptors opened on these files to close them. I think it is something that could be improved. In many situations, you know you do not have descriptors on these files and we could have a method to delete without doing the check, just the system call, without visiting the tree. > Another thing that might help my way of doing things. I like to "save as" the image so as to have a quick check point, and the launcher is not Â« friendly Â» with renaming as it loads the default image. > > Any idea on how to integrate that ? Maybe having a list of images that pops-up ? For this feature, I have no good idea for now. I had in mind to use a tree instead of a list of images. You could expand if there are more than one image and see other images in the folder. The problem is for the metadata file: we could assume that other images should use the same metadata as the core image and use them to run the image. (For now, the metadata filename is the same for all images). > I actually changed once the "save as Â» in a Â« save checkpoint charly Â» where it saves a copy but still load the default name. Might be an option ? :) Â« Saves a copy Â» : do you mean you copy the full folder to another name ? Cheers, Christophe

May 14, 2020

Re: [Pharo-users] Artefact: special characters related issue

by Sabine Manaa

Hi Evelyn, Look here: http://forum.world.st/Artefact-and-WideString-td4857147.html#a4857325 Greetings Sabine -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 14, 2020

Re: [Pharo-users] Siren 9.0 Released

by StÃ©phane Ducasse

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 <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://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 14, 2020

Re: [Pharo-users] [ANN] Pharo Compendium

by Torsten Bergmann

Hi CÃ©drick, The GitHub partÂ is based on an open public GitHub HTTP query - which has some limits: Â - it does not return private repos, only public ones Â - it has a rate limit to not bring servers down Maybe there is a wayÂ to overcome these limits via authentication, yes. But most of my projects are public - so for me this was not a problem yet. And the initial idea of Compendium is to find public resources available to all users - not private ones available to single ones. Â If time permits I might look into this ... but not now. Bye T. Gesendet:Â Donnerstag, 14. Mai 2020 um 13:02 Uhr Von:Â "CÃ©drick BÃ©ler" <cdrick65(a)gmail.com> An:Â "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> Betreff:Â Re: [Pharo-users] [ANN] Pharo Compendium Really great tool Torsten :) Â I tagged some of my repo to test. I reseted the stores because they wasnât showing. It seems to load but then when querying in spotter, I got an error message because of non authentification. Â I went in in the (iceberg) settings, checked then unchecked the default RSA keys directory (by the way is it a know bug or is it just me ?). Â It worked after, I mean no error when querying spotter. Â Still I donât see my projects. Iâll try later but if you have an idea... Â Â Cheers, CÃ©drick Â Le 12 mai 2020 Ã 16:35, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> a Ã©crit :Â Hi Sven, I added spotter search now. I prefixed the github spotter entries additionally with the user name (owner). This way you will be able to quickly find tagged public projects by keying in the project and/or username. See attached picture for an example. Catalog loading is possible via spotter too. Have fun T. Â Gesendet: Mittwoch, 06. Mai 2020 um 14:24 Uhr Von: "Sven Van Caekenberghe" <sven@stfx.eu[mailto:sven@stfx.eu]> An: "Any question about pharo is welcome" <pharo-users@lists.pharo.org[mailto:pharo-users@lists.pharo.org]> Betreff: Re: [Pharo-users] [ANN] Pharo Compendium Great work, Torsten, works like a charm ! Since all Github projects have a README.md maybe that could be used as well, it will certainly contain more information. Most projects have several keyswords as well, that could be useful to show. Also, why not add a 'clone & metacello install baseline of' command ? Another idea: allow spotter searching of the pharo compendium entries ? Sven Â On 2 May 2020, at 22:34, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> wrote: Hi, time flows and Pharo-Project is improving on all ends since its inception in 2008. As you know over time for the code project hosting we used SqueakSource, SS3 repos and other and later switched to SmalltalkHub available on http://smalltalkhub.com[http://smalltalkhub.com]. Starting with Iceberg in Pharo 6 many community projects are now hosted elsewhere - most of them moved to GitHub. Pharo's git support allows also for GitLab, BitBucket and other git hosting services. I still think easy and quick accessibility to external (re)sources directly from the image is key - especially for new users who often get lost among all the various things that are available. Back in 2013 I therefore provided a small tool called ConfigBrowser as a replacement for MetacelloConfigurationBrowser to easily load Metacello configs directly into Pharo. Later we improved quick loading with a primary tool called "Catalog" written by Esteban. Catalog is indexing every 24 hours all configs within specific meta-repositories on SmalltalkHub (per Pharo version) like http://www.smalltalkhub.com/#!/~Pharo/MetaRepoForPharo80[http://www.smallta… to automatically build Â http://catalog.pharo.org/[http://catalog.pharo.org/] and also a JSON source Â http://catalog.pharo.org/catalog/json[http://catalog.pharo.org/catalog/json] The last one feeds the catalog browser and catalog spotter search within the Pharo image. So Catalog helped us and especially new Pharo users to find what is available as external project or package. Unfortunately some package maintainers are too lazy and do not maintain their configs over old and new Pharo versions. Also SmalltalkHub.com[http://SmalltalkHub.com] is now seen as legacy and will only be available in a read only mode or as a browseable archive soon. So we have to think about others steps beyond Catalog and (triggered by a recent discussion on Discord) I started now a simple tool that helped me finding all GitHub projects marked with "pharo" as GitHub topic. I additionally also added previous catalog loading. More sources could be added as well as some kind of custom stores/plugins. Maybe this tool could be the base for a future replacement of the catalog tool. Long story short - let me introduce "Pharo Compendium": Compendium is a new UI tool to list, browse and load Pharo artefacts from the web like: - GitHub Projects - Catalog Projects and other By default there are two plugin packages available for GitHub and Catalog - but you can implement own ones easily to connect to other sources on the web. Compendium is available on: Â https://github.com/astares/Pharo-Compendium[https://github.com/astares/Phar… It is implemented using the new Spec2 UI framework - so you need a recent Pharo 9 image to give it a try. Just run: Â Â Metacello new repository: 'github://astares/Pharo-Compendium/src'; baseline: 'Compendium'; load to load the tool. Then go to "Tools" -> "Compendium Browser". Attached is a screenshot demoing the primary functionality. If you want your GitHub project to be listed in the tool you simply need to add the topic "pharo" to the GitHub repository on the GitHub webpage. Feel free to comment or help improving the tool by sending PR's. Thx T. (aka astares) <compendium.png> Â <Compendium_Spotter.jpg>

May 14, 2020

Covid-19 Tracker with PharoJS

by Noury Bouraqadi

Hi, Dave Mason did implement a COVID-19 tracker with PharoJS. https://covid.cs.ryerson.ca/compare/ <https://covid.cs.ryerson.ca/compare/> Noury

May 14, 2020