- Pharo-users - lists.pharo.org

Re: [Pharo-users] Block/Brick

by Glenn CavarlÃ©

H Steve, I just saw that you sent me a personal email about that. Thanks for your interest in Brick, I have been slightly away from the project for some time so maybe Aliaksei or Doru could provide a better answer. For my part, since Brick is using GtExample, I'm just browsing examples by inspecting the class. When the inspector is open, you can browse and show examples in the tab named "Examples". test email wrote > PS Is Brick/Block the thing to learn these days? Is this where development > is heading? Good question. There are 2 actively developed projects : Spec2 and Bloc/Brick. Some fresh info here: http://forum.world.st/Explaining-Spec2-and-why-Bloc-is-on-the-roadmap-td509… Spec (https://github.com/pharo-spec/Spec) is a UI Builder which aim to be backend-independent. All "native" tools shipped in the Pharo image are developped using it (or should be). A new version is actively developed and already show great results. Spec2 should probably support Bloc/Brick as backend in the near future. Brick is a redesigned widget layer on top of Bloc, a new UI infrastructure which aim to replace Morphic, one day. The original github repo is https://github.com/pharo-graphics/Brick but I saw that the Feenk team (which actively develop it) forked the repo in Febrary (https://github.com/feenkcom/Brick) So i don't know what is exactly the current state of each version. I hope I have answered your questions ;) Cheers, ----- Glenn CavarlÃ© -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 7, 2019

Block/Brick

by Steve Quezadas

I am trying to experiment with Bloc and Brick. I downloaded the packages, and want to "play around with it" by experimenting with the examples in it. But how do I open the examples? The github page for both Block and Brick doesn't really list much documentation. Taking from an arbitrary Brick example, these things don't work: foo := BrExamplesShowroom new. foo openInWorld. - or - BrExamplesShowroom openPlayer Sorry for the naive quesiton. - Steve PS Is Brick/Block the thing to learn these days? Is this where development is heading?

May 4, 2019

Visit Tokyo from 27 June to 5 of July

by ducasse

Dear Pharoers/Smalltalkers from Japan (and other countries) I will visit (mainly) Tokyo from 27 of June to 5th of July 2019. I will give several talks and one is scheduled to the Smalltalk User group (Oda Tomohiro is organising it). I will give some talks to researchers and companies. Iâm really excited to meet people. Do not hesitate to contact me so that we can plan extra meetings. I really want to see what you are doing and how to support the community. Stef

May 4, 2019

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

by Ben Coman

Thanks for the background info Steph. On Thu, 2 May 2019 at 17:28, ducasse <stepharo(a)netcourrier.com> wrote: > Spec 2.0 revisits fundamentally Spec. > - adds much better layouts (we will deprecate the interpreter design) A very long time ago that I was debugging a Spec app was that debugging INTO the framework from application code would take 30 odd steps before it got to evaluate the block passed by the application code. Sorry thats a bit vague, but I'm hoping deprecating the interpreter will improve such experience. As a general comment also, architectures using stored blocks for configuration rather than passing in an "object with defined methods" seems a lot "less live". Changing the code inside the block doesn't change the behaviour of existing elements. But maybe the "methods" way has its own issues. cheers -ben

May 3, 2019

Re: [Pharo-users] 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. Thanks for all the replies with interesting suggestions! Gabriel Cotelli <g.cotelli(a)gmail.com> writes: > Dictionary newFromPairs: (words collect: [ :each | each -> each size > ]). Sven Van Caekenberghe <sven(a)stfx.eu> writes: > { #foo->1. #bar->2 } #asDictionary > > (#('abc' 'defg') collect: [ :each | each -> each size ]) asDictionary. K K Subbu <kksubbu.ml(a)gmail.com> writes (after correction): > Dictionary newFromKeys: words andValues: (words collect: #size) For my real-life use case, asDictionary is the most appopriate choice. It does exactly what I need. I had discovered newFromKeys:andValues:, which indeed is a good fit for my small example, but not for my real applications, where the list of associations comes from another method, so I can't change the way it is constructed. What I was most surprised about is newFromPairs:, which works as quoted although its documentation says something else: "Answer an instance of me associating (anArray at: i) to (anArray at: i+1) for each odd i. anArray must have an even number of entries." Konrad.

May 3, 2019

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

by Eric Gade

Stef, Exciting news all around. Is this s good opportunity to revisit theming? I made a good attempt to wrap my head around themes about a year ago or so, but it's quite complex. If now's not (understandably) the time, how will themes work with this new multiple-backend approach? On Thu, May 2, 2019 at 11:45 AM Alexandre Bergel via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > 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 > > > > > > > > > -- Eric

May 2, 2019

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

by K K Subbu

On 02/05/19 9:52 PM, Sven Van Caekenberghe wrote: >> Dictionary withKeys: words andValues: (words collect: #size) >> >> HTH .. Subbu >> > Never saw that one, cool. > > But it is #newFromKeys:andValues: as far as I can see You're right. I got mixed up. Thanks for the correction .. Subbu

May 2, 2019

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

by Sven Van Caekenberghe

> On 2 May 2019, at 18:18, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > > On 02/05/19 9:14 PM, Konrad Hinsen wrote: >> | words lengths | >> words := #('abc' 'defg'). >> lengths := Dictionary new. >> words do: >> [ :each | lengths at: each put: each size ]. > > Dictionary withKeys: words andValues: (words collect: #size) > > HTH .. Subbu > Never saw that one, cool. But it is #newFromKeys:andValues: as far as I can see

May 2, 2019

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

by K K Subbu

On 02/05/19 9:14 PM, Konrad Hinsen wrote: > | words lengths | > words := #('abc' 'defg'). > lengths := Dictionary new. > words do: > [ :each | lengths at: each put: each size ]. Dictionary withKeys: words andValues: (words collect: #size) HTH .. Subbu

May 2, 2019

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

by Sven Van Caekenberghe

> On 2 May 2019, at 17:52, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > 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, { #foo->1. #bar->2 } #asDictionary (#('abc' 'defg') collect: [ :each | each -> each size ]) asDictionary. > 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