- Pharo-users - lists.pharo.org

Re: [Pharo-users] Creating a dictionary from a list of associations

by Gabriel Cotelli

Dictionary newFromPairs: (words collect: [ :each | each -> each size ]). On Thu, May 2, 2019 at 12:45 PM Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > Hi everyone, > > About twice a week I start looking for a straightforward way to > turn a list of associations into a dictionary, spend a while searching, > and give up, ending up with a messy explicit loop. > > Example: > > | words lengths | > words := #('abc' 'defg'). > lengths := Dictionary new. > words do: > [ :each | lengths at: each put: each size ]. > lengths > > Is there really no way to this with less code? I'd expect the following > to work: > > | words lengths | > words := #('abc' 'defg'). > lengths := Dictionary withAll: > (words collect: [ :each | each -> each size ]). > > but it looks like Dictionary>>#withAll: was specifically designed to > make this impossible (because with the default implementation in > Collection it would work). > > Konrad. > >

May 2, 2019

Re: [Pharo-dev] Explaining Spec2 and why Bloc is on the roadmap

by Alexandre Bergel

Hi Stef, Thanks for this email. Spec 2 really looks great. It is also great to foresee an integration of Bloc/Brick in Pharo. Cheers, Alexandre > On May 2, 2019, at 5:27 AM, ducasse <stepharo(a)netcourrier.com> wrote: > > Dear Pharoers > > We would like to explain what is Spec 2.0 and how Bloc is on the Pharo roadmap. > > Spec is a way to support a way to express and reuse application interaction logic. > Spec was first developed by Benjamin van Ryseghem and others while supervised > by StÃ©phane Ducasse. > Over the years we cleaned Spec, but we never took the time to really revisit it, and Spec > was never stressed outside the scope of Pharo tools (even if there is some people who > used it in their projects, this was not the general case). There was a need to deeply rethink > the way we express and reuse interaction application logic. > > Spec 2.0 revisits fundamentally Spec. The consortium wants to acknowledge the strong financial > support of Schmidt in this new development. Here is a list of points we are working on to support companies > to build modern applications with Pharo. > > - adding support for many widgets and at the same time improving existing widgets such as fasttable > - adds much better layouts (we will deprecate the interpreter design) > - introducing a new way to architecture an application: > Spec20 introduces the notion of application to better handle resources and window flow > - revisiting the internal logic of Spec (to remove useless parts and enhance the ones that works) > - adding many tests > > In addition we want that Spec 2.0 is not tight anymore with Morphic. > Why? Because we want to make sure that: > - companies can deploy desktop applications > - we can reuse all the tools logic of Pharo with new widgets sets such as Brick (widgets on top of Bloc) > without having to rewrite everything. > > This is why Spec2.0 can optionally render using Gtk3.0. It also means that in the future we can have native widgets. > > Now that Bloc/Brick is finally reaching a point where it can be tried and eventually adopted, we want to > make sure the transition to it will not force us to throw away the tools we developed last ten years. > We think that Bloc needs some effort to clean and structure it and Spec2.0 gives the time to let Bloc and Brick > mature. Also, we want to make sure that in the future we will be able to adopt other backends in case we > decide it (Remember new now is old tomorrow and while Bloc/Brick is new and modern, it will not remain > new and modern forever). > > Brick needs to be ready for Pharo consumption, and to make it possible we need to move the image to converge. > With Spec 2.0, in future versions we will just need to define a new backend to get all our tools working. > > The Pharo Board > > >

May 2, 2019

Creating a dictionary from a list of associations

by Konrad Hinsen

Hi everyone, About twice a week I start looking for a straightforward way to turn a list of associations into a dictionary, spend a while searching, and give up, ending up with a messy explicit loop. Example: | words lengths | words := #('abc' 'defg'). lengths := Dictionary new. words do: [ :each | lengths at: each put: each size ]. lengths Is there really no way to this with less code? I'd expect the following to work: | words lengths | words := #('abc' 'defg'). lengths := Dictionary withAll: (words collect: [ :each | each -> each size ]). but it looks like Dictionary>>#withAll: was specifically designed to make this impossible (because with the default implementation in Collection it would work). Konrad.

May 2, 2019

[ANN] Pharo Consortium New Academic Member: ISCLab

by Marcus Denker

The Pharo Consortium is very happy to announce that ISCLab has joined the Consortium as an Academic Member. About - ISCLab: Intelligent Software Construction Laboratory, Department of Computer Science, FCFM, University of Chile. The ISCLab develops methodologies to build software systems that are both resource efficient (CPU, memory, energy) and adequate with modern software development techniques. We push further the knowledge frontier of Software Engineering with innovative methodologies, rigorous empirical evaluations, and valuable software artifacts. https://isclab.dcc.uchile.cl - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

May 2, 2019

Explaining Spec2 and why Bloc is on the roadmap

by ducasse

Dear Pharoers We would like to explain what is Spec 2.0 and how Bloc is on the Pharo roadmap. Spec is a way to support a way to express and reuse application interaction logic. Spec was first developed by Benjamin van Ryseghem and others while supervised by StÃ©phane Ducasse. Over the years we cleaned Spec, but we never took the time to really revisit it, and Spec was never stressed outside the scope of Pharo tools (even if there is some people who used it in their projects, this was not the general case). There was a need to deeply rethink the way we express and reuse interaction application logic. Spec 2.0 revisits fundamentally Spec. The consortium wants to acknowledge the strong financial support of Schmidt in this new development. Here is a list of points we are working on to support companies to build modern applications with Pharo. - adding support for many widgets and at the same time improving existing widgets such as fasttable - adds much better layouts (we will deprecate the interpreter design) - introducing a new way to architecture an application: Spec20 introduces the notion of application to better handle resources and window flow - revisiting the internal logic of Spec (to remove useless parts and enhance the ones that works) - adding many tests In addition we want that Spec 2.0 is not tight anymore with Morphic. Why? Because we want to make sure that: - companies can deploy desktop applications - we can reuse all the tools logic of Pharo with new widgets sets such as Brick (widgets on top of Bloc) without having to rewrite everything. This is why Spec2.0 can optionally render using Gtk3.0. It also means that in the future we can have native widgets. Now that Bloc/Brick is finally reaching a point where it can be tried and eventually adopted, we want to make sure the transition to it will not force us to throw away the tools we developed last ten years. We think that Bloc needs some effort to clean and structure it and Spec2.0 gives the time to let Bloc and Brick mature. Also, we want to make sure that in the future we will be able to adopt other backends in case we decide it (Remember new now is old tomorrow and while Bloc/Brick is new and modern, it will not remain new and modern forever). Brick needs to be ready for Pharo consumption, and to make it possible we need to move the image to converge. With Spec 2.0, in future versions we will just need to define a new backend to get all our tools working. The Pharo Board

May 2, 2019

Re: [Pharo-users] Getting example images - https://picsum.photos

by Sven Van Caekenberghe

> On 2 May 2019, at 11:12, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > This makes me remember when I was working doing android mobile apps: there is a kitten placeholder service too. > > https://placekitten.com/ > > And status codes too > > https://http.cat/ > > > ZnEasy getJpeg: 'https://placekitten.com/200/300'. > > :) That is obviously better ! > On Wed, May 1, 2019 at 10:41 AM Franz Josef Konrad <franzl(a)fjkonrad.de> wrote: > Am 29.04.2019 um 13:23 schrieb Sven Van Caekenberghe: > > Hi, > > > > This is a cool service: https://picsum.photos - it gives you example images (pictures/photos). > > > > Here is how you can use this from a standard Pharo image (no pun intended). > > > > ZnEasy getJpeg: 'https://picsum.photos/512'. > > > > ImageReadWriter formFromStream: (ZnClient new > > systemPolicy; > > url: 'https://picsum.photos/640/480?grayscale'; > > accept: ZnMimeType imagePng; > > get) readStream. > > > > Sven > > > > > > Picsum is listed here <https://github.com/toddmotto/public-apis> along > with a number of other public APIs. Maybe this overview list is > interesting for one or the other. > > Franz Josef > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

May 2, 2019

Re: [Pharo-users] Getting example images - https://picsum.photos

by Guillermo Polito

This makes me remember when I was working doing android mobile apps: there is a kitten placeholder service too. https://placekitten.com/ And status codes too https://http.cat/ ZnEasy getJpeg: 'https://placekitten.com/200/300'. :) On Wed, May 1, 2019 at 10:41 AM Franz Josef Konrad <franzl(a)fjkonrad.de> wrote: > Am 29.04.2019 um 13:23 schrieb Sven Van Caekenberghe: > > Hi, > > > > This is a cool service: https://picsum.photos - it gives you example > images (pictures/photos). > > > > Here is how you can use this from a standard Pharo image (no pun > intended). > > > > ZnEasy getJpeg: 'https://picsum.photos/512'. > > > > ImageReadWriter formFromStream: (ZnClient new > > systemPolicy; > > url: 'https://picsum.photos/640/480?grayscale'; > > accept: ZnMimeType imagePng; > > get) readStream. > > > > Sven > > > > > > Picsum is listed here <https://github.com/toddmotto/public-apis> along > with a number of other public APIs. Maybe this overview list is > interesting for one or the other. > > Franz Josef > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 2, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by Stephan Eggermont

TedVanGaalen <tedvga(a)gmail.com> wrote: > Thanks, but I will revert to Pharo 5.0 (pre spur VM) again... > until the problems with 7.x are solved... or 8 is really stable. The problem here really is Apple breaking things and not telling developers what changes they make. Weâve been hit by that before. Microsoft has the same problem Stephan

May 1, 2019

Re: [Pharo-users] Getting example images - https://picsum.photos

by Franz Josef Konrad

Am 29.04.2019 um 13:23 schrieb Sven Van Caekenberghe: > Hi, > > This is a cool service: https://picsum.photos - it gives you example images (pictures/photos). > > Here is how you can use this from a standard Pharo image (no pun intended). > > ZnEasy getJpeg: 'https://picsum.photos/512'. > > ImageReadWriter formFromStream: (ZnClient new > systemPolicy; > url: 'https://picsum.photos/640/480?grayscale'; > accept: ZnMimeType imagePng; > get) readStream. > > Sven > > Picsum is listed here <https://github.com/toddmotto/public-apis> along with a number of other public APIs. Maybe this overview list is interesting for one or the other. Franz Josef

May 1, 2019

Re: [Pharo-users] Why doesn't the VM command line help show the useful image commands anymore?

by K K Subbu

On 30/04/19 6:14 PM, Tim Mackinnon wrote: > Subbu - I didnât understand your point? How would I know to do pharo > -- --list , by looking at the output of âhelp? (And in fact that > doesnât work on OSX, it prompts me for an image - thus reinforcing my > point that the default image doesnât appear to work, at least not in > osx). Tim, I don't have access to Mac OSX :-(. The usage text is printed in lines 296-301 in https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/plat… If you don't see the same usage message, then it is a bug, possibly a missing macro def in the build script. The platform startup code on Mac and Linux are similar. They both parse args for option words starting with single or double hyphens until a word which matches "*.image" or "--" is seen. Rest of the words are treated as a image (optional) and its arguments. Regards .. Subbu

May 1, 2019