July 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] GitBridge

by Cyril Ferlicot

On Wed, Jul 17, 2019 at 4:59 PM Alexandre Bergel via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Thanks Cyril, > > This look awesome. A quick question: to access external resources, I usually use the expression (that you provide me some times ago) > > repo := (IceRepository registry detect: [ :each | each includesPackageNamed: 'GeneticAlgorithm' ] ifNone: [ self error: 'Please add a clone of this project to Iceberg to access to the resources' ]) location. > > In this case, I can use some resources located in the git repository of the GeneticAlgorithm project. Eg. repo / âmy image.pngâ > > What does GitBridge bring more than that? I feel I miss something obvious... > Well, it is mostly that. If you check the implementation it uses the same kind of expression. What it bring more is to factorise the code to do it (Like this if Iceberg change I just need to update GitBridge and all projects using it will be fixed). It also brings methods such as #version that can be useful and I hope we will add useful things to it to avoid everyone duplicating their own version in their project. Last thing is that the API is clear. For example you can just do: `GABridge images` instead of the whole detect on the Iceberg registry. > Cheers, > Alexandre > > > -- Cyril Ferlicot https://ferlicot.fr

July 17, 2019

Re: [Pharo-users] [ANN] TinyLogger

by Alexandre Bergel

Pretty cool! I love the way you document your application. Very effective! Alexandre > On Jul 16, 2019, at 4:16 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > Some time ago I released the first stable version of a project of mine: > TinyLogger. I announced it on Twitter but I forgot to announce it here :) > > I started this project because at some point I had an urgent need of a > simple logger and at that time beacon was broken. :( I had no time to > check from where the error came from and wait for the integration of a > PR so I did a simple logger directly in my project. > > After some month/years I took some time to extract it to its own project > and document it to give an alternative logger for simple cases. > > You can find information, a quick start and documentation here: > > https://github.com/jecisc/TinyLogger > > -- > Cyril Ferlicot > https://ferlicot.fr >

July 17, 2019

Re: [Pharo-users] [ANN] GitBridge

by Alexandre Bergel

Thanks Cyril, This look awesome. A quick question: to access external resources, I usually use the expression (that you provide me some times ago) repo := (IceRepository registry detect: [ :each | each includesPackageNamed: 'GeneticAlgorithm' ] ifNone: [ self error: 'Please add a clone of this project to Iceberg to access to the resources' ]) location. In this case, I can use some resources located in the git repository of the GeneticAlgorithm project. Eg. repo / âmy image.pngâ What does GitBridge bring more than that? I feel I miss something obvious... Cheers, Alexandre > On Jul 16, 2019, at 4:07 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Hi! > > Today I released the v1 of a project I wanted to do since a long time: > GitBridge. > > The goal of the project is to easily access external resources stored in > the git repository of the project and other information. > > For more infos check the Quick start or documentation present at: > https://github.com/jecisc/GitBridge > > When Monticello was the most common VCS usable with Pharo we stored a > lot of external resources in the image. Now we are able to store them > outside, get a lighter image and make it easier to edit and version them! > > This can be useful to store test resources, CSS/JS files for web > applications, documentation, etc. > > This can also be useful to get from the application some information > such as the current version of the application instead of hard-coding it > in a method to update at each release. > > It implementation relies on Iceberg and the repositories registered in it. > > -- > Cyril Ferlicot > https://ferlicot.fr >

July 17, 2019

Question about Artifact and Especial Characters

by Juan Pablo Sandoval Alcocer

Hi, We are using Artifact for automatically creating pdf invoices. It was working well so far, until we realize a problem with especial characters, for instance "ZariÄ". When some special characters are used, our script generate a white pdf as invoice :(. We tried to fix this using different char encodings for instance: UTF8 or Latin1. But then the special character is showed differently. [image: image.png] - Does anyone had this problem before? - Any idea of how may we address this? Thanks, Juan p.

July 17, 2019

Re: [Pharo-users] "whenSelectedItemChanged:" in Spec

by Peter Kenny

Ben Coman wrote > I'm not familiar with Spec but I'll have a go... > > On Wed, 17 Jul 2019 at 07:03, Steve Quezadas < > steveeq1@ > > wrote: > >> On Tue, Jul 16, 2019 at 7:43 AM Ben Coman < > btc@ > > wrote: >>> >>> On Tue, 16 Jul 2019 at 12:49, Steve Quezadas < > steveeq1@ > > wrote: >>> > >>> > I am running through the "Spec UI Framework" tutorial, and in it has a >>> widget class inherited from "ComposablePresenter" (ComposablePresenter >>> subclass: #WidgetClassList). But for some reason the >>> "whenSelectedItemChanged:" method call does not execute when I select >>> any item on the GUI list. Is there anything I'm missing? >>> > >>> > I posted this earlier on the list, and someone suggested I try >>> "whenActivatedDo:" or "whenSelectionChangedDo:", but it doesn't do >>> anything as well. The code looks like this: >>> > >>> > whenSelectedItemChanged: aBlock >>> > Transcript show: 'should get here; cr. >>> > >>> > I am using Pharo 7. >>> >>> Can you FileOut the entire sample class and attached it? >>> >>> cheers -ben >>> >> >> Ok, I filed out and it exported the file 'WidgetClassList.st' . This is >> the contents of the file: >> >> 'From Pharo7.0.3 of 12 April 2019 [Build information: >> Pharo-7.0.3+build.158.sha.0903ade8a6c96633f07e0a7f1baa9a5d48cfdf55 (64 >> Bit)] on 16 July 2019 at 3:58:28.785036 pm'! >> ComposablePresenter subclass: #WidgetClassList >> instanceVariableNames: 'list' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'QuotesProg'! >> >> !WidgetClassList methodsFor: 'initialization' stamp: 'SteveQuezadas >> 7/10/2019 14:07'! >> initializeWidgets >> list := self newList. >> list items: (AbstractWidgetPresenter allSubclasses >> sorted: [:a :b | a name < b name ]). >> self focusOrder add: list.! ! >> >> >> !WidgetClassList methodsFor: 'events-shortcuts' stamp: 'SteveQuezadas >> 7/15/2019 21:40'! >> whenSelectedItemChanged: aBlock >> Transcript show: 'got here'; cr. >> ! ! > > Looking at ListPresenter>>whenSelectedItemChanged: aBlock > it is registering aBlock on selectionHolder using #whenChangedDo: > Reviewing selectionHolder "Code search...>References to it" I see that > selectionHolder is initialized as an instance of SelectionHolderClass. > > So it seems you are expecting whenSelectedItemChanged: to be called > every time the-selection-is-changed > when actually it is only called once (by your application) to register > the block-to-be-called when the-selection-is-changed. > You don't seem to have done any such registration. > > cheers -ben Essentially ben is right. The method WidgetClassList >> when SelectedItemChanged: should just relay the message to the component ListPresenter, in the instvar list, which will carry out the registration as he describes. The problem is that this method seems to have been replaced by a debugging method, which simply displays a progress message on the Transcript. I think all you need is to enter the correct code for this method as shown in the 'Spec UI Framework' booklet: WidgetClassList >> whenSelectedItemChanged: aBlock list whenSelectedItemChanged: aBlock This is at least worth a try. You will be sticking to the code as shown in the booklet. HTH Peter Kenny -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 17, 2019

ESUG19: Camp Smalltalk 24/25 August

by Marcus Denker

As usual at ESUG, we will be holding an informal âCamp Smalltalkâ the weekend before the conference. The idea is to meet, hack, discuss. - location: ZWEIDENKER, Luxemburger Str. 72, 50674 KÃ¶ln (see https://zweidenker.de/kontakt/ <https://zweidenker.de/kontakt/> ) - dates & times: - Saturday, 24.8.2019 from 11:00 AM to 6:00 PM - Sunday, 25.8.2019 from 11:00 AM to 6:00 PM To have and idea who is coming, please fill out this doodle https://doodle.com/poll/ffkt7rqm4sfi62df <https://doodle.com/poll/ffkt7rqm4sfi62df> (just select when you will attend). FYI: Gamescom takes place in Cologne from 21.-24. August 2019. Cologne will be crowded and Hotels are expensive until the 24th.

July 17, 2019

Re: [Pharo-users] [ANN] GitBridge

by Otto Behrens

Thanks a lot! this is great functionality. Otto On Tue, Jul 16, 2019 at 10:08 PM Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Hi! > > Today I released the v1 of a project I wanted to do since a long time: > GitBridge. > > The goal of the project is to easily access external resources stored in > the git repository of the project and other information. > > For more infos check the Quick start or documentation present at: > https://github.com/jecisc/GitBridge > > When Monticello was the most common VCS usable with Pharo we stored a > lot of external resources in the image. Now we are able to store them > outside, get a lighter image and make it easier to edit and version them! > > This can be useful to store test resources, CSS/JS files for web > applications, documentation, etc. > > This can also be useful to get from the application some information > such as the current version of the application instead of hard-coding it > in a method to update at each release. > > It implementation relies on Iceberg and the repositories registered in it. > > -- > Cyril Ferlicot > https://ferlicot.fr > >

July 17, 2019

Re: [Pharo-users] [ANN] Pharo TechTalk July 18th

by Marcus Denker

This is tomorrow > On 11 Jul 2019, at 11:33, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > A regular chat about Pharo. Happens on Discord. > > Topic: How to report and fix bugs for Pharo. In a live coding session, we will together have a look at some simple fixes for Pharo8 and learn how to report bugs and do Pull Requests. > > - We will send an information to all subscribers of this event some hours before the talk starts. > - Or just hangout in Discord, we post everything there, too > > https://association.pharo.org/event-3419542

July 17, 2019

Re: [Pharo-users] [ANN] GitBridge

by Konrad Hinsen

Am 16.07.19 um 22:07 schrieb Cyril Ferlicot D.: > Today I released the v1 of a project I wanted to do since a long time: > GitBridge. > > The goal of the project is to easily access external resources stored in > the git repository of the project and other information. Excellent - that's a functionality I have wanted for a while! Thanks, Konrad.

July 17, 2019

Re: [Pharo-users] Testing "Weekly Digest" for GitHub

by Marcus Denker

Hi, This seems to have been caused by a faulty config (I really hate YAMLâ¦). I changed it *and* put the day to be saturday, as they seem to have run into rate limiting for the API on Sundays in the past. So hopefully this will work saturday again. Marcus > On 15 Jul 2019, at 11:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Somehow it did not make a report this sundayâ¦ to debug. > >> On 8 Jul 2019, at 10:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> There is a ProBot that creates an issue with a weekly summary. >> >> By installing it for testing, we got the first report: >> >> Weekly Digest (1 July, 2019 - 8 July, 2019) >> https://github.com/pharo-project/pharo/issues/381 >> >> >> I will do some fine-tuning (e.g. disable commits and star-gazers) later. >> We then can let it run for some weeks and see if it is useful or not. >> >> Marcus >

July 17, 2019