- Pharo-users - lists.pharo.org

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

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

by Ben Coman

I'm not familiar with Spec but I'll have a go... On Wed, 17 Jul 2019 at 07:03, Steve Quezadas <steveeq1(a)gmail.com> wrote: > On Tue, Jul 16, 2019 at 7:43 AM Ben Coman <btc(a)openinworld.com> wrote: >> >> On Tue, 16 Jul 2019 at 12:49, Steve Quezadas <steveeq1(a)gmail.com> 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

July 17, 2019

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

by Steve Quezadas

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. ! ! !WidgetClassList methodsFor: 'api' stamp: 'SteveQuezadas 6/26/2019 18:22'! title ^ 'Widgets'! ! !WidgetClassList methodsFor: 'api' stamp: 'SteveQuezadas 7/15/2019 19:09'! list ^ list.! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! WidgetClassList class instanceVariableNames: ''! !WidgetClassList class methodsFor: 'specs' stamp: 'SteveQuezadas 7/10/2019 14:14'! defaultSpec ^ SpecLayout composed add: #list; yourself! ! On Tue, Jul 16, 2019 at 7:43 AM Ben Coman <btc(a)openinworld.com> wrote: > On Tue, 16 Jul 2019 at 12:49, Steve Quezadas <steveeq1(a)gmail.com> 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 > >

July 16, 2019

Re: [Pharo-users] [ANN] GitBridge

by Cyril Ferlicot D.

Le 16/07/2019 Ã 23:05, Christopher Fuhrman a Ã©critÂ : > Very cool! I think the quickstart section would benefit from an example > such as loading icons or a test resource (mse file for moose).Â > I'll add it to my todo ;) > Also, can you explain how updating a Readme.md would work using > GitBridge? I assume it would be modified with a text editor in Pharo > then Iceberg will see the changes to commit them? Sorry if I'm reading > too much into it. > Well, you can manipulate it as any other file reference and change the content then use the API of Iceberg to commit it but there is no GUI currently in Iceberg to manage external files. But my usecase was more the other way around. Instead of editing files in Pharo I wanted to edit files outside Pharo but still have my application using those files. In a web application I serve the files stored in my git repository via Zinc, referencing them via my bridge, and I edit them outside Pharo instead of editing string containing the files in Pharo. My goal was to benefit from the tools managing better the CSS/JS/Markdown than Pharo. > -- Cyril Ferlicot https://ferlicot.fr

July 16, 2019

Re: [Pharo-users] [ANN] GitBridge

by Christopher Fuhrman

Very cool! I think the quickstart section would benefit from an example such as loading icons or a test resource (mse file for moose). Also, can you explain how updating a Readme.md would work using GitBridge? I assume it would be modified with a text editor in Pharo then Iceberg will see the changes to commit them? Sorry if I'm reading too much into it. On Tue, Jul 16, 2019, 22:40 Tomohiro Oda <tomohiro.tomo.oda(a)gmail.com> wrote: > Cyril, > > Awesome! > I've been wanting to make something like this for my project. > Great thanks! > --- > tomo > > 2019å¹´7æ17æ¥(æ°´) 5:07 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > > > > 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 16, 2019

Re: [Pharo-users] [ANN] GitBridge

by Tomohiro Oda

Cyril, Awesome! I've been wanting to make something like this for my project. Great thanks! --- tomo 2019å¹´7æ17æ¥(æ°´) 5:07 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > > 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 16, 2019

[ANN] TinyLogger

by Cyril Ferlicot D.

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 16, 2019

[ANN] GitBridge

by Cyril Ferlicot D.

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 16, 2019