January 2021 - Pharo-users - lists.pharo.org

[ANN] Boardwalk v6.0.0 [v6.0.0] released!
by Buenos Aires Smalltalk Jan. 15, 2021

Jan. 15, 2021

1 0

SpTablePresenter - can one edit cells using that?
by Kasper Osterbye Jan. 15, 2021

Jan. 15, 2021

Cheers, I was looking at class SpTablePresenter. It does not seem like there is a way to edit the values in the cells. Is that correct? If so, is there an other table class which will allow that? Best, Kasper

1 0

[ANN] Hyperspace v2.5.0 [v2.5.0] released!
by Buenos Aires Smalltalk Jan. 14, 2021

Jan. 14, 2021

1 0

FreeBSD
by Jimmie Houchin Jan. 13, 2021

Jan. 13, 2021

I am planning an install of FreeBSD. I am new to FreeBSD, but a long time Linux user. I know that FreeBSD has support for Linux binaries and I can try to start there. I know there are no FreeBSD builds. I was wondering what it would take for me to build it on FreeBSD. This will be new to me. So any pointers, help or advise greatly appreciated. Thanks. Jimmie

1 0

[Pharo @ FOSDEM 2021] Stand
by Santiago Bragagnolo Jan. 12, 2021

Jan. 12, 2021

We applied to participate in FOSDEM 2021, and we were accepted :)! ======================================= Hello team behind Pharo, Your submission for a stand at FOSDEM 2021 has been accepted. We welcome you to FOSDEM 2021, our first fully digital edition. As a reminder, this is what you can expect this year. - A spot on our exhibition website (stands.fosdem.org) - A Matrix chatroom. - A place to store video's. The exhibition website is a static site generated by hugo (gohugo.io). We have set the theme and the structure, and you can add as many pages as you want. The code for the website currently lives at https://github.com/FOSDEM/stands-website . Documentation will be added shortly (and will be communicated via the list). To get started with adding content to the website, follow these steps: 1. Create two git repositories (public), one for your content and one for your static files. Provide us with both links and make sure we can pull anonymously. 2. Add pages in any format Hugo accepts. Note that you cannot add more levels (if you want a deeper structure, ask us). 3. Once every hour a script will rebuild the website. 4. You can add links to your own website(s) as well, but we ask that you keep stand-related things on our stands website. We'll provide more information on where to upload the video's later this month. It is up to you if you wish to create them, but we think it will add value to your stand. More details on the chatroom will also be made available in the coming week. This week, we'll publish the list of accepted stands on our website, and add the primary and secondary contact to standholders(a)lists.fosdem.org for further communication. By the beginning of next week, the exhibition website will be put online (behind authentication as it is not public yet). As soon as the infrastructure is in place, the video site and the Matrix chatroom will be configured. We'll send further updates to the standholders mailing list. Please bear with us, this is new for us as well ;-) We hope to see you at FOSDEM! Kind regards, The FOSDEM Stands Team

3 7

Beta Testing ARM64 Linux & Windows
by tesonep＠gmail.com Jan. 12, 2021

Jan. 12, 2021

In the last months, we have been working on the implementation of a MIT-licenced ARMv8 Just-In-Time compiler for Pharo VM. We would like to announce that a beta first version of our JIT backend is available for beta-testing for ARM Linux and Windows machines. We are very happy with the advance in this subject, as we have not only implemented a new backend but we have added more than 2500 tests of the JIT, the primitives, code generation, plugins, and the VM in general. Also, we are generating a lot of documentation and improving the process to really democratize the development of the VM. After all the text there are details on how to obtain the versions for testing it. The following sections give more details of the current status, and the following steps including Apple Silicon, Windows, and Linux ARM64. *Current Status* Our objective is to have a running JIT for the new aarch64 architecture (ARM 64bits). This task includes not only a new backend for the JIT compiler but also adding support for external libraries, dependencies, and the build process. This means having a working VM with comparable features as the one existing in Intel X64. We are targeting all the major operating systems running on this platform (Linux, OSX, Windows). Each of them presents different restrictions and conditions. After expending some time this is the current status: - We implemented a full backend for the JIT compiler targeting aarch64. - All the image side was adapted to run on it, tested on Ubuntu ARM 64 bits. - We added support for: Iceberg (Libgit) / Athens (Cairo) / SDL / GTK - We implemented a LibFFI based FFI backend as the default one for Pharo 9 in aarch64 (next to come in all platforms). This opens the door to easily port the features to other platforms and OSes. This new implementation does not have an impact on performance as it has comparable results with the old implementation. Much more, this implementation opens also the door to have runners in different threads than the VM thread (non-blocking FFI). *Status By Platform* *Linux* We have a working version of the VM. It is using the same code-base and build process for both architectures (Intel X64 / ARM aarch64). A version can be compiled and executed in all the platforms. Also, we have integrated the build using Open Build Services (OBS) to generate packages for all the mainstream distributions. Currently, the version for Debian-like systems (Debian, Ubuntu, Raspberry pi OS, etc) is available and ready to beta test; the details for installing them are in the end of the mail. Versions for ARCH-based and RPM-based systems are in the working (If you want to get them or to test them please contact us, so we can pass on the detail of how to get them). *Windows * We have extended the build process to fully support Microsoft Visual Studio compilers and more flexibility to select the targets, also we are building it to run in Windows ARM. To correctly run the VM in Windows it is needed to build all dependencies for aarch64. In this path, we have a working Intel x64 version with Cygwin and MSVC, and a MSVC version for aarch64 (ARM64). The ARM64 version is available to be beta-testing on machines with this architecture. The Details are at the end of the mail. *OSX* Our third target is to have a working version for the newest Apple silicon. We are acquiring the corresponding hardware to test and to address the differences in the API exposed to JIT applications. As it is the case of the Windows VM, there is no need to change the machine code generation backend, as it is the same that has been implemented for Linux; but to compile external libraries and particularities of the new OS version. Thanks for your support. In the meantime, we will continue giving you news about the current state and where are we going. *Beta Testing - Linux* For Debian like distributions, the instructions are the following. *Installation* 1) Add a new APT source, usually modifying a file in /etc/apt/sources.list.d/, for example, we can add the pharo.list file with the following content. Also, we need to register the key of the repository. These steps should be done only once. We are giving a little script for modifying the configuration. It is only needed to execute line by line. *For Raspbian:* echo "deb https://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/… ./" >> pharo.list sudo cp pharo.list /etc/apt/sources.list.d/pharo.list wget https://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/… sudo apt-key add Release.key *For Ubuntu:* echo "deb https://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/… ./" >> pharo.list sudo cp pharo.list /etc/apt/sources.list.d/pharo.list wget https://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/… sudo apt-key add Release.key 2) Update the repository to take the current versions sudo apt update 3) Install Pharo9 VM sudo apt install pharo9 libgit2 4) In case of using the interactive version (with UI) check if the packages libsdl2-2.0-0 and libcairo2 are installed (Usually they are installed, but depends what it is installed in the system). These are not needed for the headless execution or if it is not used by the image. *Getting the images:* The images can be downloaded using zero-conf, the latest image is ready to be used. It can be done with: wget -O - get.pharo.org/64/90 | bash *Running Pharo* pharo Pharo.image eval 42 factorial Or interactive pharo Pharo.image --interactive *Windows Testing* A version of the VM is ready to be tested in Windows ARM64. A zip containing the VM is available in: https://files.pharo.org/vm/pharo-spur64/Windows-ARM64/PharoVM-9.0.0-4df0e56… As in Linux, the latest image is compatible with this version of the VM. *Error reporting* In case of encountering errors please report them attaching: - crash.dmp file and PharoDebug.log - Version of the image using (in case of any community project loaded, the names of those) - Complete machine version (the result of executing uname -a) - Complete information about the Linux distribution - Steps for reproducing the error (if needed) Thanks for the effort!! -- Pablo Tesone. tesonep(a)gmail.com

2 1

Re: is there a better way
by Roelof Wobben Jan. 11, 2021

Jan. 11, 2021

Thanks, Right now im downloading/fetching the images every time again. As I see it, the biggest bottleneck is that I have 10 images. And for all 10 I fetching the image and the data I could display when a user wants it. So that will be 20 calls to the api. So maybe some cache could be handy. Any hints how to make a cache in smalltalk. Roelof Op 6-1-2021 om 19:19 schreef Sven Van Caekenberghe: > Roelof, > > Working with multiple high resolution images, as I believe you are > doing, is always going to be a real challenge, performance wise. It > just takes time to transfer lots of data. > > First you have to make sure that you are not doing too much work > (double downloads, using too high resolutions for previews or > browsing). Also, make sure your ultimate client (the browser) can > cache as well if applicable (set modification dates on the response). > > Next you could cache images locally (on your app server) so that next > time you need the same image, you do not need to download it again. Of > course, this only helps if your hit rate is higher than zero (if you > actually ask for the same image multiple times). > > It is also possible to do multiple download requests concurrently: if > the other end is fast enough, that can certainly help. > > HTH, > > Sven > >> On 6 Jan 2021, at 18:11, Roelof Wobben via Pharo-users >> <pharo-users(a)lists.pharo.org> wrote: >> >> >> I did it on the root document and see this : >> >> <nkdkdknfekaflcfc.png> >> >> So as far as I see it , The most time it taken by getting all the >> data from all the 10 images. >> >> I hope someone can look at me if im on the right track and will help >> me to figure out faster ways to achieve the same >> >> Roelof >> >> >> >> Op 5-1-2021 om 05:16 schreef Richard O'Keefe: >>> Before you take another step, explore the root document. >>> >>> Profiling is easy. >>> Open a Playground. >>> Type an expression such as >>> 3 tinyBenchmarks >>> Right click and select 'Profile it'. >>> >>> More generally, in a browser, look at the "Tool - Profilers" >>> class category. The classic approach was >>> MessageTally spyOn: [3 tinyBenchmarks] >>> If I understand correctly, 'Profile it' uses TimeProfiler, >>> which has a nicer interface. (This is in Pharo 8.) >>> >>> >>> On Sun, 3 Jan 2021 at 23:03, Roelof Wobben <r.wobben(a)home.nl> wrote: >>> I want that the code fetches a url and some data from the >>> Rijksmuseaum api. >>> And as far as I see it the second it not pointless because it >>> getting more detailed info about the painting as in the first get. >>> >>> I did not profiled it because I never learned how to do that in Pharo. >>> >>> Roelof >>> >>> >>> >>> Op 3-1-2021 om 01:09 schreef Richard O'Keefe: >>>> What do you want the code to do? >>>> Have you profiled the code to see where the time is going? >>>> >>>> A quick look at the code shows >>>> - Paintings does one web get >>>> - each Painting does two more web gets >>>> ! and the first of those seems to be pretty pointless, >>>> as it refetches an object that Paintings already fetched >>>> and just looked at. >>>> >>>> >>>> >>>> On Sun, 3 Jan 2021 at 01:16, Roelof Wobben via Pharo-users >>>> <pharo-users(a)lists.pharo.org> wrote: >>>> Hello, >>>> >>>> I have now this code : https://github.com/RoelofWobben/Rijksmuseam >>>> >>>> but it seems to be slow. >>>> >>>> Can anyone help me with a way I can use a sort of cache so the page >>>> looks first at the cache if a image is there . >>>> If so, take the image from there , if not , ask the api for the url of >>>> the image. >>>> >>>> Roelof

5 5

Re: is there a better way
by Roelof Wobben Jan. 6, 2021

Jan. 6, 2021

2 1

[ANN] Stargate-Consul v2.0.0 [v2.0.0] released!
by Buenos Aires Smalltalk Jan. 6, 2021

Jan. 6, 2021

1 0

[ANN] Superluminal v1.2.1 [v1.2.1] released!
by Buenos Aires Smalltalk Jan. 6, 2021

Jan. 6, 2021

1 0