- Pharo-users - lists.pharo.org

Re: [Pharo-users] Thinking aloud about project at hand

by Cyril Ferlicot

On Tue 14 Apr 2020 at 15:45, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: > > Take a look at the DrGeo example app, it shows how to do that (link > bellow). > > > you hook in a startUpList: and shutDownList: of your main class. > Hi, If you need to hook startup/shutdown actions, you can read this documentation: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > Great, I'll check it out. > > > You can start with a simple Pharo image (look at the blog of Leon Ramon > on activeRecord in Pharo). > > So my suggestion is the following > > - start with what makes you the fastest and focus on your domain. > > For persistence I'll start with the minimal effort - Fuel. At first glance > it looks that it has everything that I need. > > Thanks for all the tips, I'll report my experiences as I progress. > > Best wishes, > Tomaz > > > -- Cyril Ferlicot https://ferlicot.fr

April 14, 2020

Re: [Pharo-users] Thinking aloud about project at hand

by TomaÅ¾ Turk

> Take a look at the DrGeo example app, it shows how to do that (link bellow). > you hook in a startUpList: and shutDownList: of your main class. Great, I'll check it out. > You can start with a simple Pharo image (look at the blog of Leon Ramon on activeRecord in Pharo). > So my suggestion is the following > - start with what makes you the fastest and focus on your domain. For persistence I'll start with the minimal effort - Fuel. At first glance it looks that it has everything that I need. Thanks for all the tips, I'll report my experiences as I progress. Best wishes, Tomaz

April 14, 2020

Problem switching from PetitParser to PetitParser2

by PBKResearch

Hello I have been switching part of a package called TextLint so that it uses PetitParser2 as the parsing engine. For the most part it went fairly smoothly, but I have one problem which occurs in many places. The original parse rules had many conditional matching rules based on PPPredicateObjectParser. I have changed this to PP2PredicateObjectNode, using the same block as a predicate in each case. All of them fail when I test run them in a playground; in every case the error message is of the form: 'Character does not understand [some condition testing method]'. The condition being tested is meaningless for a character - it applies to a token produced by some earlier parsing. Looking at the code for PP2PredicateObjectNode>>#predicate:, I see that the predicate is always treated as a PP2CharSetPredicate, which is claimed to be a performance optimization. The error messages I have seen come from the initialization of this, setting up the 255 precomputed results, because they all relate to a character with asciiValue = 1. All these rules worked in PetitParser, because the methods for PPPredicateObjectParser allow one to distinguish between a character set predicate and a general block; in fact, the class side contains a large variety of methods for generating conditions. As far as I can see, PP2PredicateObjectNode allows only one type of condition. Have I misunderstood - is there some way to specify the condition is not a character set? Thanks for any help Peter Kenny

April 14, 2020

Re: [Pharo-users] Loading Seaside and Magritte in Pharo8 - baseline load conflicts

by Sven Van Caekenberghe

Hi, > On 14 Apr 2020, at 11:23, Sebastijan Kaplar <s.kaplar1(a)outlook.com> wrote: > > MetacelloConflictingProjectError: Load Conflict between existing BaselineOfGrease [baseline] from github://SeasideSt/Grease:v1.4.x/repository and BaselineOfGrease [baseline] from github://SeasideSt/Grease:v1.4.3/repository Yes I have seen that also before in other situations, and it is super annoying. Apparently, v1.4.x and v1.4.3 are considered different/conflicting. I don't know if this is a bug or by design. I believe you can solve this with #onConflict directives on the Metacello class, but this also feels like a hack. Sven

April 14, 2020

Loading Seaside and Magritte in Pharo8 - baseline load conflicts

by Sebastijan Kaplar

Hello everyone, so I canât resolve the problem in my project, which emerged when something happened in one of those repositories (it was working fine previously). When I try to load the project using metacello Metacello new baseline: #NewWave; repository: 'github://skaplar/NewWave:development'; load. I get MetacelloConflictingProjectError: Load Conflict between existing BaselineOfGrease [baseline] from github://SeasideSt/Grease:v1.4.x/repository and BaselineOfGrease [baseline] from github://SeasideSt/Grease:v1.4.3/repository <github://SeasideSt/Grease:v1.4.3/repository> More info here (https://travis-ci.org/github/skaplar/NewWave/jobs/671515073 <https://travis-ci.org/github/skaplar/NewWave/jobs/671515073>) My baseline looks something like this: â¦Seaside seaside: spec spec baseline: 'Seaside3' with: [ spec repository: 'github://SeasideSt/Seaside:master/repository' ] â¦Magrite magritte: spec spec baseline: 'Magritte' with: [ spec loads: #( Seaside ); repository: 'github://magritte-metamodel/magritte:v3.6â ] If someone cares for a deeper look (https://github.com/skaplar/NewWave/tree/development/BaselineOfNewWave <https://github.com/skaplar/NewWave/tree/development/BaselineOfNewWave>) Any help would be appreciated! Thanks, Sebastijan

April 14, 2020

Re: [Pharo-users] [ANN] QRCode on github

by Sven Van Caekenberghe

Great, thanks. This is indeed a very well written project. > On 14 Apr 2020, at 00:19, Renaud de Villemeur via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Renaud de Villemeur <renaud.devillemeur(a)tuta.io> > Subject: [ANN] QRCode on github > Date: 14 April 2020 at 00:19:58 GMT+2 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Need to generate a QRCode ? An old (but still relevant) project was available on smalltalkhub. > > As I wasn't aware if it was already available elsewhere, I moved it to Github, including load instruction: > https://github.com/rvillemeur/QRCode > > Unit test are all green on Linux. > > Have fun. > Renaud > > > > >

April 14, 2020

Re: [Pharo-users] Minimality

by CÃ©drick BÃ©ler

Hi Erik, > (Part of this I mentioned on Discord as well, but not all readers will be on > Discord) Yes Iâve just seen it and I remembered seeing your posts > > I'm working with a tiny Smalltalk image (currently around 150Kb) which > contains basic classes (very similar to PharoCandle, but with the regular > Smalltalk names without PC-prefix, see > https://github.com/carolahp/PharoCandleSrc) It additionally supports > WebSockets when used in combination with SqueakJS, but I'm working on a > regular WebSocket-version for OpenSmalltalk-VM as well. > > The image has an ObjectEncoder/Decoder pair allowing the image to 'receive' > encoded classes and methods from a regular Smalltalk image (bytcode only, > since no compiler is present in the tine image). The tiny image can install > these classes and use them. The current 'protocol' is to send messages to > this tiny image and have the image send events back to the regular image. > The tiny image (client) is responsible for making a connection with the > regular image (server). But this protocol can be adjusted with newly > installed classes of course ;-). Cool this is the stuff I need to play with. How can I try ? > > My idea (dream?) is to create small cloud images for personal use, so you > can run many on limited computing units. Frankly this is my same goal, except I see them as Â« Information system node Â» of a distributed information system architecture ie. Computing units of information objects (often related to scripts btw). So this is really really great what you achieved :) > These images will not have file- or > FFI-support Ok. Indeed this would complicate for nothing. No FFI support but would some simple interaction wanted (I/o stream, small unix system call ?). > and need to retrieve data through WebSocket/HTTP/... or other > web communication technology. It is part of a project I'm working on to > learn programming in Smalltalk to kids. Cool > They can spin up an image in the > cloud (or on their Raspberry Pi at home) and load their code from a remote > repository. For me it would be spin a new information system and eventually link it with shared others (can be a remote repo). > The development environment will run in the cloud and be usable > with a web browser. In the web browser runs a tiny image which can execu...o > wait, I explained that part already ;-). So in the web browser this same > tiny image is running (on SqueakJS). This time, it loads code to be able to > manipulate the DOM. This tiny image is sort of the Javascript replacement. > So everything is Smalltalk! :-) > > Still a long way to go though. I hope to be able to demonstrate a little of > this in a not so distant future. I will share my code as well. Everything > will be open source. Iâm really interested and love to help in some ways. So as far as you have info/tuto or other thinks, please tell me. Just be running it would be the first step. Any pointers/repositories ? Cheers, CÃ©drik > > Feel free to reach out if anyone wants to participate. ;-) > > Regards, > Erik > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

April 14, 2020

Migrating your projects to GitHub? Do not forget to tag your project!

by Esteban Lorenzano

Hello, Just a gentle reminder to tag your project as âPharoâ, so a search engine can find it better! Esteban

April 14, 2020

[ANN] QRCode on github

by Renaud de Villemeur

Need to generate a QRCode ? An old (but still relevant) project was available on smalltalkhub. As I wasn't aware if it was already available elsewhere, I moved it to Github, including load instruction: https://github.com/rvillemeur/QRCode Unit test are all green on Linux. Have fun. Renaud

April 13, 2020

Re: [Pharo-users] Minimality

by Erik Stel

Hi Cedreek, (Part of this I mentioned on Discord as well, but not all readers will be on Discord) I'm working with a tiny Smalltalk image (currently around 150Kb) which contains basic classes (very similar to PharoCandle, but with the regular Smalltalk names without PC-prefix, see https://github.com/carolahp/PharoCandleSrc) It additionally supports WebSockets when used in combination with SqueakJS, but I'm working on a regular WebSocket-version for OpenSmalltalk-VM as well. The image has an ObjectEncoder/Decoder pair allowing the image to 'receive' encoded classes and methods from a regular Smalltalk image (bytcode only, since no compiler is present in the tine image). The tiny image can install these classes and use them. The current 'protocol' is to send messages to this tiny image and have the image send events back to the regular image. The tiny image (client) is responsible for making a connection with the regular image (server). But this protocol can be adjusted with newly installed classes of course ;-). My idea (dream?) is to create small cloud images for personal use, so you can run many on limited computing units. These images will not have file- or FFI-support and need to retrieve data through WebSocket/HTTP/... or other web communication technology. It is part of a project I'm working on to learn programming in Smalltalk to kids. They can spin up an image in the cloud (or on their Raspberry Pi at home) and load their code from a remote repository. The development environment will run in the cloud and be usable with a web browser. In the web browser runs a tiny image which can execu...o wait, I explained that part already ;-). So in the web browser this same tiny image is running (on SqueakJS). This time, it loads code to be able to manipulate the DOM. This tiny image is sort of the Javascript replacement. So everything is Smalltalk! :-) Still a long way to go though. I hope to be able to demonstrate a little of this in a not so distant future. I will share my code as well. Everything will be open source. Feel free to reach out if anyone wants to participate. ;-) Regards, Erik -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 13, 2020