May 2020 - Pharo-users - lists.pharo.org

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

by CÃ©drick BÃ©ler

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(a)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(a)stfx.eu> >> An: "Any question about pharo is welcome" <pharo-users(a)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(a)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. >>> 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 >>> >>> to automatically build >>> >>> http://catalog.pharo.org/ >>> >>> and also a JSON source >>> >>> 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 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 >>> >>> 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

Re: [Pharo-users] Pharo-Sound

by Ben Coman

On Thu, 14 May 2020 at 02:50, 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? > Sorry I don't the answer Russ, but just to piggy-back your query... @all, is sound something that we should now be starting to do via FFI rather than existing plugins? [but pls prioritize Russ's question] cheers -ben

May 14, 2020

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

by Offray Vladimir Luna CÃ¡rdenas

Hi Pierce, My workflow with Gitea is pretty similar to yours. The only difference is that the Gitea server is community hosted on the web, instead of running on local hardware. It seems we share the joy of minimalist self contained little tools, as your work on SQLite shows :-). BTW, thanks for it. Cheers, Offray On 13/05/20 8:22 p.Â m., Pierce Ng 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 > >

May 14, 2020

Re: [Pharo-users] Need help putting my Pharo package under source control

by tbrunz

Well, you can capture the stack to the clipboard, and you can save it as a 'Fuel' file. That allows examination (including by others, within a different image). If you look at the image you posted, of the debugger window, on the far right of "Proceed Restart Into Over Through" there's a small drop-down menu (with an icon of horizontal bars). Click on that and you should see options for 'Fuel out Stack' and 'Copy Stack to Clipboard'. As far as how to make the best use of this... That's over my head! (But others on this forum know.) -t -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 14, 2020

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

by Pierce Ng

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

May 14, 2020

Re: [Pharo-users] [ANN] What are good reasons to use Smalltalk?

by Richard O'Keefe

This is an ambiguous question. There are at least - Smalltalk the language - Smalltalk the libraries - Smalltalk the IDE Now my own Smalltalk system does not have an IDE, it does not support run-time modifications to the system, and it does not (yet) have graphics. But I still enjoy using it and find it worth using. The poll includes only one option that is close to my reasons for using Smalltalk. It's ambiguous another way. Different Smalltalk systems have different IDEs and different libraries. The VisualAge IDE is different in a number of ways from Squeak & Pharo. So is Dolphin, but in a *good* way. Dolphin is easily the *prettiest* GUI/IDE around. The libraries are different too. The ANSI Smalltalk standard has been around a long time, and I *still* cannot open a file in a portable way. So when you ask about "Smalltalk", I have to ask "which?" VisualAge was designed to fit into the IBM commercial programming environment, and it does so admirably. On Thu, 14 May 2020 at 07:43, Richard Kenneth Eng <horrido.hobbies(a)gmail.com> wrote: > > https://smalltalk.tech.blog/2020/05/13/what-are-good-reasons-to-use-smallta… > > > Please participate in the poll. >

May 14, 2020

Siren 9.0 Released

by stephen＠heaveneverywhere.com

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. 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 The read the demo code workbook (this text), go to, http://FASTLabInc.com/Siren/Siren7.5.Workbook.html or http://FASTLabInc.com/Siren/Siren7.5.Workbook.pdf If you like to read manuals, take a look at, 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 <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 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 --

May 13, 2020

Re: [Pharo-users] Uptime

by Vince Refiti

Hello Sven This is the kind of thing I like to see. Gives me more confidence in recommending Pharo to management for production use. Just some things that still concern me though: Why are people surprised at discovering that Pharo is capable of such uptimes? Are people experiencing instability with Pharo in production settings? If so, what kind of instability are people experiencing? Thanks, Vince -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Sven Van Caekenberghe Sent: Tuesday, 12 May 2020 6:06 PM To: Pharo users <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Uptime EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hi, So here is a little anecdote from the real world. I was planning to update the OS on my Linux server, from Ubuntu 18.04 LTS to 20.04 LTS (Long Term Support). This small (Digital Ocean, 1GB RAM, 1 Core) cloud server runs 3 Pharo images with public facing web sites. The machine itself reports: $ uptime 12:37:50 up 530 days, 21:46, 1 user, load average: 0.02, 0.04, 0.01 which means it hasn't been powered down or didn't restart in 530 days. I was surprised to discover that 2 of the Pharo images on that machine did just as well: $ ./repl.sh Connecting to Telnet REPL at locahost:41011 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Neo Console Pharo-7.0+alpha.build.660.sha.2eb9bd2f41e7b0bd8f9f4190906910f83c178ab1 (32 Bit) pharo> get system.uptime 405 days 20 hours 29 minutes pharo> quit Bye! $ ./repl.sh Connecting to Telnet REPL at locahost:41001 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Neo Console Pharo4.0 of 18 March 2013 update 40620 > get system.uptime 530 days 21 hours 44 minutes > quit Bye! So both Pharo 7 and Pharo 4 kept on doing their jobs for a very long time. I think this is a testament to the stability of Pharo and to what is possible. Regards, Sven -- Sven Van Caekenberghe Proudly supporting Pharo https://urldefense.com/v3/__http://pharo.org__;!!I_DbfM1H!U29_nUf8k6rmGjsp2… https://urldefense.com/v3/__http://association.pharo.org__;!!I_DbfM1H!U29_n… https://urldefense.com/v3/__http://consortium.pharo.org__;!!I_DbfM1H!U29_nU…

May 13, 2020

Re: [Pharo-users] [ANN] What are good reasons to use Smalltalk?

by Richard Sargent

You missed the fact that it makes it easier to communicate with the user community, since it's a "near-English" grammar, and you can easily use a common terminology. On Wed, May 13, 2020, 12:43 Richard Kenneth Eng <horrido.hobbies(a)gmail.com> wrote: > > https://smalltalk.tech.blog/2020/05/13/what-are-good-reasons-to-use-smallta… > > > Please participate in the poll. >

May 13, 2020

[ANN] What are good reasons to use Smalltalk?

by Richard Kenneth Eng

https://smalltalk.tech.blog/2020/05/13/what-are-good-reasons-to-use-smallta… Please participate in the poll.

May 13, 2020