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

Re: [Pharo-users] [Seaside] ZincStaticServerAdaptor starts with different port

by Sven Van Caekenberghe

WAServerManager class>>#startUp sends #startUp to all registered adaptors If you saved an image with a running adaptor in it, it will be restarted when the image comes up. This is cool and works fine, but I find it better suited to development than deployment. When deploying I make sure there are no servers of any kind running, and then start them manually and explicitly in a startup script. So if something starts up automagically, you must have done something. BTW, 80 is a restricted port, but I guess you already know that. > On 10 May 2020, at 00:14, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi, > > I have a ZnZincStaticServerAdaptor, that after quitting the image and > starting it again starts in a different port. > > So I did: > WAServerManager default adaptors do: [ :each | WAServerManager default > unregister: each ]. > (ZnZincStaticServerAdaptor startOn: 8000 andServeFilesFrom: > (FileLocator imageDirectory / 'static' ) asFileReference). > > And get the server running in the port 8000. [see zn8000.png] > > But after restarting the image, it is running in the port 80. [see zn80.png] > > Why is it so? > > Regards, > <zn8000.png><zn80.png>_______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

May 10, 2020

ZincStaticServerAdaptor starts with different port

by Esteban Maringolo

Hi, I have a ZnZincStaticServerAdaptor, that after quitting the image and starting it again starts in a different port. So I did: WAServerManager default adaptors do: [ :each | WAServerManager default unregister: each ]. (ZnZincStaticServerAdaptor startOn: 8000 andServeFilesFrom: (FileLocator imageDirectory / 'static' ) asFileReference). And get the server running in the port 8000. [see zn8000.png] But after restarting the image, it is running in the port 80. [see zn80.png] Why is it so? Regards,

May 9, 2020

Re: [Pharo-users] Matching block parameter in rewrite rule

by Cyril Ferlicot D.

Le 08/05/2020 Ã 02:51, Gabriel Cotelli a Ã©critÂ : > Cyril, something likeÂ this: > > | env rewriter result methods changes | > env := RBBrowserEnvironment default forPackages: (RPackageOrganizer > default packages ). > > rewriter := RBParseTreeRewriter new. > rewriter Â > replace:'`@receiver detect: `@arg1 ifFound: [ :`arg2 | `arg2 ] ifNone: > `@arg3' with: '`@receiver detect: `@arg1 ifNone: `@arg3'. > > changes := Array with: (RBSmalllintChecker runRule: > (RBTransformationRule new > rewriteRule: rewriter; > yourself) > onEnvironment: Â env Â ) builder. > > Â (ChangesBrowser changes: changes) open. Thank you! I got it to work :) Now I'll be able to rewrite much more things :) -- Cyril Ferlicot https://ferlicot.fr

May 8, 2020

Re: [Pharo-users] Matching block parameter in rewrite rule

by Gabriel Cotelli

Cyril, something like this: | env rewriter result methods changes | env := RBBrowserEnvironment default forPackages: (RPackageOrganizer default packages ). rewriter := RBParseTreeRewriter new. rewriter replace:'`@receiver detect: `@arg1 ifFound: [ :`arg2 | `arg2 ] ifNone: `@arg3' with: '`@receiver detect: `@arg1 ifNone: `@arg3'. changes := Array with: (RBSmalllintChecker runRule: (RBTransformationRule new rewriteRule: rewriter; yourself) onEnvironment: env ) builder. (ChangesBrowser changes: changes) open. On Thu, May 7, 2020 at 8:22 PM Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Hi, > > I was wondering if it was possible with the parse tree rewriter to match > a block parameter? > > I would like to be able, for example, to rewrite: > > `#() detect: #odd ifFound: [ :e | e ] ifNone: [ self toto ]` > > as > > `#() detect: #odd ifNone: [ self toto ]` > > But I don't know how to express this rule with the rewrite rules of Pharo. > > I tried multiple things such as: > > '`@receiver detect: `@arg1 ifFound: [ `@arg2 | `@arg2 ] ifNone: `@arg3 ' > -> '`@receiver detect: `@arg1 ifNone: `@arg3' > > or > > '`@receiver detect: `@arg1 ifFound: [ :`@arg2 | `@arg2 ] ifNone: `@arg3 > ' -> '`@receiver detect: `@arg1 ifNone: `@arg3' > > Without sucess. > > Is there a way to do that or is it a limitation of the rewrite syntax? > > -- > Cyril Ferlicot > https://ferlicot.fr > >

May 8, 2020

Matching block parameter in rewrite rule

by Cyril Ferlicot D.

Hi, I was wondering if it was possible with the parse tree rewriter to match a block parameter? I would like to be able, for example, to rewrite: `#() detect: #odd ifFound: [ :e | e ] ifNone: [ self toto ]` as `#() detect: #odd ifNone: [ self toto ]` But I don't know how to express this rule with the rewrite rules of Pharo. I tried multiple things such as: '`@receiver detect: `@arg1 ifFound: [ `@arg2 | `@arg2 ] ifNone: `@arg3 ' -> '`@receiver detect: `@arg1 ifNone: `@arg3' or '`@receiver detect: `@arg1 ifFound: [ :`@arg2 | `@arg2 ] ifNone: `@arg3 ' -> '`@receiver detect: `@arg1 ifNone: `@arg3' Without sucess. Is there a way to do that or is it a limitation of the rewrite syntax? -- Cyril Ferlicot https://ferlicot.fr

May 7, 2020

Issues browsing/saving a class in a package - seems like its unknown

by PAUL DEBRUICKER

Hi - In Pharo 7 I'm having an issue with a particular class where if I browse it in Calypso I can see & navigate among the methods in the class. If I run some of the methods I get dnu errors for methods I can see in the class browser. If I re-save a method that has the dnu without changing anything then Calypso shows two methods in the same class with the same name. If in a playground I try a MyClass recompile Then I get an "Unknown variable..." dialog that asks me to define the class. If I highlight the MyClass in the playground and "browse" it then Calypso finds the class and opens the browser. If I fileout the class then the fileout has all the methods and two copies with the same name of the one I re-saved above. Because of these issues I cannot save the package using Monticello or iceberg. Any ideas what I can do to fix this situation? At a minimum I reckon I can fileout the bad class, delete it from the image, and file it back in, then save. Thanks Paul

May 7, 2020

Deleting images / saving as - in Pharo Launcher auncher

by CÃ©drick BÃ©ler

Hi Christophe, This version is definitely cooler :) 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 ? 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 ? 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 ? :) Cheers, CÃ©drick

May 7, 2020

Re: [Pharo-users] [ANN] Ansible v1.0.0 [v1.0.0] released!

by ducasse

This is great! Thanks for all this good energy > On 6 May 2020, at 20:39, Buenos Aires Smalltalk <github(a)fast.org.ar> wrote: > > Ansible <https://u15343809.ct.sendgrid.net/ls/click?upn=Uy61-2B68gB74aaPZq0VQlFt1xga…>, ansible is an amqp client for pharo reached it's v1.0.0 <https://u15343809.ct.sendgrid.net/ls/click?upn=Uy61-2B68gB74aaPZq0VQlFt1xga…> version. > > Changelog > > Migrated from Cuis port > Added tests to common integration patterns using GitHub Actions (tests pass in Pharo 6.1, Pharo 7 and Pharo 8) > Added code coverage metrics using CodeCov > Fixed code generation from specification for version 0-9-1 > Added documentation. A three parts tutorial inspired in the RabittMQ ones. > Added some basic abstractions like AmqpConnectionBuilder to ease the building of complex objects. > Regards, > > The Buenos Aires Smalltalk team > >

May 6, 2020

[ANN] Ansible v1.0.0 [v1.0.0] released!

by Buenos Aires Smalltalk

May 6, 2020

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

by Sven Van Caekenberghe

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>

May 6, 2020