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

How to read this file into a image

by r.wobben＠home.nl

Hello, Im just trying for fun to get exercism working on P9 and now I wonder how I can take care that this data from a exercism api can be read in the image so the user can work on it. ``` ``` ``` " \# Hello World The classical introductory exercise. Just say ""Hello, World!"". \[""Hello, World!""\](http://en.wikipedia.org/wiki/%22Hello,_world!%22_program) is the traditional first program for beginning programming in a new language or environment. The objectives are simple: \- Write a function that returns the string ""Hello, World!"". \- Run the test suite and make sure that it succeeds. \- Submit your solution and check it at the website. If everything goes well, you will be ready to fetch your first real exercise \## Hint If you are editting this file in a text editor and not in Pharo - please review the \[Getting Started\](https://exercism.io/tracks/pharo/installation) section. While you can use a text editor, the Pharo IDE is partly what makes the language so special. In Pharo you can run code (including tests) with broken methods and missing classes. When the VM encounters broken code, it raises a debugger which lets you explore the problem a little better. You then have the option to press the Create button to add a missing class or method, as well as correct any code that causes an error. When you do so, the debugger will backup and let you resume execution with your new changes. Try doing this with your HelloWorld example, by simply running any one of the unit test methods. " Class { #name : #HelloWorldTest, #superclass : #ExercismTest, #category : #'Exercise@HelloWorld' } { #category : #config } HelloWorldTest class >> exercise \[ "Answer the configured exercise meta data for this exercise, an ExercismExercise. HelloWorld is a special case as it's the first exercise" ^(ExercismExercise for: self) isCore: true; isAutoApproved: true; difficulty: 1; topics: #('introduction' 'strings'); yourself \] { #category : #config } HelloWorldTest class >> uuid \[ "Answer a unique id for this exercise" ^'a1812b5e-2788-4ea6-b948-bfe54edeb0da' \] { #category : #config } HelloWorldTest class >> version \[ "Answer the exercise version number string this test was derived from" ^'1.1.0' \] { #category : #testing } HelloWorldTest >> testHello \[ self assert: HelloWorld sayHello equals: 'Hello, World!' \]

Jan. 25, 2021

Happy New Year and Pharo 90 good news.

by StÃ©phane Ducasse

Dear happy Pharoers, First we wish you a good 2021 year. We really hope that we will get out of this situation. On the Pharo side we have excellent news. Pharo 90 is continuing to follow its roadmap and it will be another version a massive amount of improvements. We will mention them in the Pharo 90 announce but we can cite a few: Spec2, new tools, new debugger framework, better parser, general speedup, new optimisations, full block and clean block closures, support for large images, new fluid class syntax, ... The key and important advance is that the VM roadmap is delivering. We have been working on the implementation of a MIT-licensed ARMv8 Just-In-Time compiler for Pharo VM. We are very happy with the advance on this subject, as we have not only implemented a new backend but we added more than 2500 tests to the JIT, the primitives, code generation, plugins and the VM in general. In the process we fixed many problems. We are currently fixing ephemerons since they never really worked in Pharo. We are stressing the infrastructure with more than 50000 ephemerons. Also, we are improving and cleaning up the primitive invocation scheme to fix heap corruption issues, and fixing many open issues in the VM. Finally, we are working a lot to have a reproducible build in all the platforms and easing the path to VM development, we are still far from our objective but the improvements are starting to show. We are happy that following the roadmap that was decided during General assembly of PharoDays is successful. We have been investing in the Pharo VM and that our efforts are greatly paying off. This is the current status around the VM - We implemented a full backend for the JIT compiler targeting ARMv8 (AARCH64) - We launched the beta version for Windows, Linux and raspberry of the new 64 JIT ARM. - We are waiting to receive a new mac machine to be able to test our new JIT on it. - All the image side was adapted to run on it, tested on Ubuntu ARM 64 bits and Windows ARM. - We have support for all third party libraries in these platforms: Iceberg (Libgit) / Athens (Cairo) / SDL / GTK. - We implemented a LibFFI-based FFI backend as the default one for Pharo 9 in aarch64 (It is also present in other platforms, keeping the existing one as fallback, e.g. used when the VM is not the latest). - We revisited the complete compilation chain on Windows to use CMake and avoid Cigwin dependency. - We are starting to use OBS to build for multiple Unix and Linux distributions (Debian-like is Done, More distributios to come). - Many bugs on the VM have been fixed, for all these bugs tests have been written to detect regressions and to to document the solution. - We are always performing clean-ups of the VM base code: removing dead-code and experiments from the main branch. All removed code is kept in the history and it is accessible to revisit or to improve to the level that is required to be integrated (e.g., Newspeak Support, Lowcode) - We improved the implementation of Windows Network primitives, and we have done a clean-up of the event handling code allowing an IDLE VM. - We are starting to improve the JIT compiler. We are applying some approaches developed in modern compiler such as bloc representation. - We are working in statistics collection to characterize the behavior of different components of the VM. - We are planning to generate a set of benchmarks that correctly represents the workload of applications using the VM (e.g, Web Server, Interactive Applications, FFI intensive applications). It means that in the near future we expect to be able to improve even more our VM applying a scientific approach: measure, assess, improve. - We expect that for Pharo 10, we will continue to clean the VM code and be more agile. - We will able to look again at Sista. All these steps show that we are in much better situation. We drastically reduce the truck factor around the VM. It particularly means that the consortium now does not depend of the good will and knowledge of other people. We want to thank every member of the consortium. Now we have a particular thank to Lifeware that renewed their contract and Schmidt Buro for their original contract. A last word â do not hesitate to contact us, we are here to help you growing your business. S. Ducasse on the behalf of the Pharo consortium -------------------------------------------- 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: Aurore Dalle 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 -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle 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

Jan. 25, 2021

Re: Iceberg error on adding a package

by Sanjay Minni

Hi Guillermo seems something is wrong with iceberg i get a error/walkback with anything even adding a repository what is the usual approach to fixing such situations regards Sanjay Guillermo Polito wrote > Hi Sanjay, Iâd say the UI is in an incorrect state and did not update > after some change. > > Would you mind trying closing all your iceberg windows and retest with a > freshly open one? > >> El 25 ene 2021, a las 8:17, Sanjay Minni < > sm@ > > escribiÃ³: >> >> Iceberg Pharo 9 Win 10 64 bit - error when trying to add another package >> to a >> project >> >> I have a Project with a package which I am committing to github >> repository. >> Now when trying to add another package (+ Add Package) I get this >> walkback >> >> <http://forum.world.st/file/t368721/IcebergError.jpg> >> >> what could be the issue. >> >> >> >> >> ----- >> cheers, >> Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 25, 2021

[ANN] Next Pharo Sprint: Jan 29

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Jan 29 (this Friday) Goals of this sprint: - Fix issues from tracker https://github.com/pharo-project/pharo/issues This is a Remote Sprint, it happens on Discord. http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

Jan. 25, 2021

Re: Magritte

by Sanjay Minni

Am posing messages on GH Repo Disc Board while awaiting subscription approval to Magritte ML Sanjay Sean P. DeNigris wrote > Sanjay Minni wrote >> > <magritte Description> >> ...Â Are the pragmas required > > Yes, annotating methods is how they are registered as part of the Magritte > description. There have been several non-backward-compatible Magritte > versions (currently on v. 3), so that may have been added later; note that > these methods should be on the instance side, unlike in the original > Magritte. Here is an example: > > MyClass>>#descriptionHasMetacelloConfiguration > > <magritteDescription> > ^ MABooleanDescription new > priority: 250; > accessor: #hasMetacelloConfiguration; > beReadOnly; > beRequired; > yourself > > p.s. happy to discuss here, but we also added a discussion place to the GH > repo: https://github.com/magritte-metamodel/magritte/discussions > p.p.s. there is a Magritte ML, but it doesn't get much traffic > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 25, 2021

Re: Iceberg error on adding a package

by Sanjay Minni

Tried ... issue remains the same On Mon, 25 Jan 2021 at 13:44, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi Sanjay, Iâd say the UI is in an incorrect state and did not update > after some change. > > Would you mind trying closing all your iceberg windows and retest with a > freshly open one? > > > El 25 ene 2021, a las 8:17, Sanjay Minni <sm(a)planage.com> escribiÃ³: > > > > Iceberg Pharo 9 Win 10 64 bit - error when trying to add another package > to a > > project > > > > I have a Project with a package which I am committing to github > repository. > > Now when trying to add another package (+ Add Package) I get this > walkback > > > > <http://forum.world.st/file/t368721/IcebergError.jpg> > > > > what could be the issue. > > > > > > > > > > ----- > > cheers, > > Sanjay > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > -- --- Sanjay Minni +91-9900-902902

Jan. 25, 2021

Re: Iceberg error on adding a package

by Guillermo Polito

Hi Sanjay, Iâd say the UI is in an incorrect state and did not update after some change. Would you mind trying closing all your iceberg windows and retest with a freshly open one? > El 25 ene 2021, a las 8:17, Sanjay Minni <sm(a)planage.com> escribiÃ³: > > Iceberg Pharo 9 Win 10 64 bit - error when trying to add another package to a > project > > I have a Project with a package which I am committing to github repository. > Now when trying to add another package (+ Add Package) I get this walkback > > <http://forum.world.st/file/t368721/IcebergError.jpg> > > what could be the issue. > > > > > ----- > cheers, > Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 25, 2021

Iceberg error on adding a package

by Sanjay Minni

Iceberg Pharo 9 Win 10 64 bit - error when trying to add another package to a project I have a Project with a package which I am committing to github repository. Now when trying to add another package (+ Add Package) I get this walkback <http://forum.world.st/file/t368721/IcebergError.jpg> what could be the issue. ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 25, 2021

Pharo as a development environment for TiddlyWiki target/deployment platform

by Offray Vladimir Luna CÃ¡rdenas

Hi, In a previous mail I told how our last semester explorations in the local communityÂ building, deploying and teaching Brea[1][2], a Pharo powered tool between a Static Site Generator and a headless CMS, led me towards TiddlyWiki[3] as the more dynamic counterpart of such deployments and today we a a little chat[4] with Norbert about trying to avoid the over complication of NodeJS and replacing that with a pretty simple Pharo based counterpart. [1] https://mutabit.com/repos.fossil/indieweb/ [2] https://code.tupale.co/Offray/Brea [3] https://tiddlywiki.com/ [4] https://twitter.com/NorbertHartl/status/1353319130804465668 I would like to start with something like tw5-server.rb [5], which is a pretty small Ruby script (46 lines) based in the Webrick and fileutils libraries, using the Pharo counterparts (Zinc? Teapot?). I don't have experience in Ruby, but maybe something in the list can help. It seems that the script opens a folder in the local file system and serves the files there. One of them is a TiddlyWiki file and once it is served (at port 8000) the class DefaultFileHandler (lines 18 to 35) takes care of saving the file and sucesive copies of it. Particularly lines 25 and 26 create a backup of the body in the current file and updates the Tiddly file body with new versions as saving is done in the web user interface. But further details scape me, particularly how the server knows that the TiddlyWiki file is being save. [5] https://gist.github.com/jimfoltz/ee791c1bdd30ce137bc23cce826096da Any corrections on my understanding so far, hints or pointers on how to get something similar with Pharo would be greatly appreciated. Cheers, Offray

Jan. 25, 2021

Re: Magritte

by Sanjay Minni

Thanks - I will make further postings in Magritte ML (just subscribed) ML and Discord are friendlier and visible even to the non subscribers than GH discussion boards ,,, my view Sean P. DeNigris wrote > Sanjay Minni wrote >> > <magritte Description> >> ...Â Are the pragmas required > > Yes, annotating methods is how they are registered as part of the Magritte > description. There have been several non-backward-compatible Magritte > versions (currently on v. 3), so that may have been added later; note that > these methods should be on the instance side, unlike in the original > Magritte. Here is an example: > > MyClass>>#descriptionHasMetacelloConfiguration > > <magritteDescription> > ^ MABooleanDescription new > priority: 250; > accessor: #hasMetacelloConfiguration; > beReadOnly; > beRequired; > yourself > > p.s. happy to discuss here, but we also added a discussion place to the GH > repo: https://github.com/magritte-metamodel/magritte/discussions > p.p.s. there is a Magritte ML, but it doesn't get much traffic > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 24, 2021