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

Re: [Pharo-users] Spec layout

by stepharo

marion the solution is what peter proposes. Stef Le 18/5/16 Ã 11:14, Marion Noirbent a Ã©crit : > In fact i was trying to modify RadioButtonGroup to turn it into a > widget, #buttons is not a widget but its collection of widget. > > May you have confused RadioButtonGroup with the MenuModel / > MenuGroupModel / MenuItemModel which are widgets. I take inspiration > from them and I would got the same kind of behaviour. > > Le 17/05/2016 21:11, stepharo a Ã©crit : >> Thanks Johan >> >> >> We looked at >> >> RadioButtonGroupExample >> >> but you see we cannot have a RadioButtonGroupPresenter having 2, 3 or 4 >> radioButton. >> >> Stef >> >> >> Le 17/5/16 Ã 18:52, Johan Fabry a Ã©crit : >>> Hi Marion, >>> >>> the class side message of defaultSpec is generally meant to be used if >>> you use a fixed number of widgets, so you can put the reference to the >>> name of each widget there (in cour case #buttons). For variable number >>> of widgets you should have a look at the dynamic features of Spec. >>> >>> That being said, It looks like what you really want to use is a Radio >>> Button Group. Have a look at RadioButtonGroupExample. >>> >>> HTH >>> >>> -- >>> Does this mail seem too brief? Sorry for that, I donât mean to be >>> rude! Please see http://emailcharter.org . >>> >>> Johan Fabry - http://pleiad.cl/~jfabry >>> PLEIAD and RyCh labs - Computer Science Department (DCC) - >>> University of Chile >>> >>>> On May 17, 2016, at 13:48, Marion Noirbent >>>> <ms.noirbent(a)etudiant.univ-lille1.fr> wrote: >>>> >>>> Hi, >>>> I'm trying to create a widget whith Spec, managing a collection of >>>> RadioButton. But I have a problem with defaultSpec (the accessor of >>>> the collection is the methods "buttons") : >>>> >>>> If i put defaultSpec on class side, i can't acces the collection of >>>> the instance. (the following code iterate on the string) >>>> >>>> defaultSpec >>>> <spec: #default> >>>> ^ SpecLayout composed >>>> newColumn: [ :column | #buttons do: [ :item | column add: >>>> item ] ]; >>>> yourself >>>> >>>> If i put it on instance side, the lookup don't find it (in the book >>>> Building UI with Spec, it said the lookup begin by the instance side >>>> and it allow to have specific UI, in part about layout) >>>> >>>> defaultSpec >>>> <spec: #default> >>>> ^ SpecLayout composed >>>> newColumn: [ :column | self buttons do: [ :item | column add: >>>> item ] ]; >>>> yourself >>>> >>>> Any idea ? >>>> >>>> Marion Noirbent, >>>> >>>> >>> >>> >> >> >

May 18, 2016

Re: [Pharo-users] Retina support in Pharo

by Thibault Raffaillac

> > What happens if Pharo is launched on a retina computer? > You get the same thing as on a non-retina display, except instead of each > fuzzy pixel you get a visibly sharper square made of 2*2 retina pixels. > From sufficiently far away there's no difference, but when you're right in > front of it you can see the pixelation, especially for text and compared to > HiDPI-enabled apps in nearby windows. I have the same problem too. When working on OpenGL demo in C I noticed SDL2 does output the same ugly pixels by default, yet should support Retina screens (https://wiki.libsdl.org/SDL_CreateWindow - did not try, switched to GLFW which supports Retina out of the box). Is Pharo window created with native calls or SDL2? Cheers, Thibault

May 18, 2016

Re: [Pharo-users] GLMFormatedPresentation>>format bug?

by Tudor Girba

Hi, > On May 16, 2016, at 7:59 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On Mon, May 16, 2016 at 05:42:54AM +0200, Tudor Girba wrote: >> Hi, >> >> >> On May 16, 2016, at 1:00 AM, Ben Coman <btc(a)openInWorld.com> wrote: >> >> On Mon, May 16, 2016 at 6:28 AM, Alistair Grant <akgrant0710(a)gmail.com> >> wrote: >> >> Hi Andrei, >> >> On Mon, May 16, 2016 at 12:08:01AM +0200, Andrei Chis wrote: >> >> Hi Alistair, >> >> Try something like this. Now 100% sure it will work. >> >> gtInspectIn: composite >> <gtInspectorPresentationOrder: 30> >> >> ^ composite text >> title: 'Meme'; >> format: [self asText]. >> >> The display block should return the object to be displayed, which >> is this case >> is self. >> >> >> Yep, that fixes the problem! Thanks for your reply. >> >> >> Just curious if this also works... >> >> ^ composite text >> title: 'Meme'; >> format: #asText > > This also works, and looking at the definition of #format I'm guessing > that this is closer to the original intended usage (see below)? > > >> It works because the format block takes an optional argument with the input >> entity. However, the semantics are not going to be quite the same. In >> isolation, the behavior will be identical. However, the difference comes when >> you try to reuse a presentation. >> >> Letâs look at an example. This is how an AST node displays the source: >> >> RBProgramNode>>gtInspectorSourceCodeIn: composite >> <gtInspectorPresentationOrder: 30> >> ^ composite pharoMethod >> title: 'Source codeâ; >> display: [ self source ]; >> ... >> >> Like this, the block closure can simply delegate to the corresponding ast node >> to display the source: >> >> BlockClosure>>gtInspectorSourceCodeIn: composite >> <gtInspectorPresentationOrder: 40> >> self sourceNode gtInspectorSourceCodeIn: composite >> >> And a keymap object which holds a block in an action instance variable, can >> simply delegate to the block closure object to display the source: >> >> KMKeymap>>gtInspectorSourceCodeIn: composite >> <gtInspectorPresentationOrder: 30> >> ^ self action gtInspectorSourceCodeIn: composite >> >> >> If the ProgramNode definition would have been implemented like: >> display: [ :each | each source ] >> >> then when inspecting the block object, we would have gotten the block object as >> each, and not the AST node. >> >> Does this explanation make sense? > > So using this code is going to be more flexible than > > ^ composite text > title: 'Meme'; > format: [self asText] > > since the format object isn't supplied the optional arguments. Actually, the less flexible approach is: format: [ :each | each source ] Given that you define the extension directly in the class of the object you want to inspect, you essentially always want to apply the transformations on self, regardless of the âeachâ block argument. In this way, you can reuse this presentation in other objects through delegation like I mentioned above. In any case, I am happy to hear that you want to extend you object. Could you let us know the use case? Cheers, Tudor > Thanks, > Alistair -- www.tudorgirba.com www.feenk.com "Some battles are better lost than fought."

May 18, 2016

Re: [Pharo-users] Retina support in Pharo

by markm

Thanks for the update. Looking forward to the better fonts, but also appreciate all the hard work everyone has put in so far! -- View this message in context: http://forum.world.st/Retina-support-in-Pharo-tp4895245p4895558.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 18, 2016

Re: [Pharo-users] On Class and Method comments

by Nicolai Hess

2016-05-17 18:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > > Now, I only know that comments in block closures are placed behind the >> block code. >> Do you know more examplmes where the formatter still misplaces the >> comment. > > > Maybe just comments now? I've added a formatting configuration that > preserved vertical white space (and I believe also comment position, > because I used to write inline comments), but I think it was lost during > migration to BlueInk. But I'll have a look. > > I opened a bug report: https://pharo.fogbugz.com/f/cases/18253/formatter-misplaces-some-block-comm…

May 17, 2016

Re: [Pharo-users] Disabling welcome window

by Henrik Nergaard

World submorphs select: [ :sm | sm isSystemWindow and: [ sm label = PharoWelcomePage title ] ] thenDo: [ :window | window delete ]. Best regards, Henrik From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Peter UhnÃ¡k Sent: Wednesday, May 18, 2016 12:20 AM To: Pharo-Users List <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Disabling welcome window Is there a clean way how to close or not open the Pharo 5.0 welcome window? Short of going through the stack and closing it (courtesy of Cyril) (SystemWindow allInstances select: [ :w | w labelString includesSubstring: 'Welcome' ]) do: #delete Thanks, Peter

May 17, 2016

Disabling welcome window

by Peter UhnÃ¡k

Is there a clean way how to close or not open the Pharo 5.0 welcome window? Short of going through the stack and closing it (courtesy of Cyril) (SystemWindow allInstances select: [ :w | w labelString includesSubstring: 'Welcome' ]) do: #delete Thanks, Peter

May 17, 2016

Re: [Pharo-users] On Class and Method comments

by Dimitris Chloupis

yes template looks fine to me, basic classes is a good place to start too. I will give it a try and see how it goes :) On Tue, May 17, 2016 at 10:55 PM stepharo <stepharo(a)free.fr> wrote: > > I really like to start writing some class and method comments to make > Pharo image more beginner friendly. > > > This would be realllllllllly coool. > Did you check the class comment template because I wrote it thinking about > this. > > What I think would be great is to have great comments for the basic > classes. Because as a newby such classes are really important. > > For example I would like to enhance the symbol class comment to include > the snippet sent by henrik > > | s1 s2 | > s1 := 1234 asString. s2 := 1234 asString. > s1 = s2. "true" s1 == s2. "false" > s1 asSymbol = s2 asSymbol. "true" s1 asSymbol == s2 asSymbol. "true" > (s1 class allInstances select: [:s | s = s1 ]) size. "2" (s1 asSymbol > class allInstances select: [:s | s = s1 asSymbol ]) size. "1" > [ #stringA = #stringB ] bench. "26,812,864 per second" [ 'StringA' = > 'StringB' ] bench. "3,492,987 per second" > > Are there any guidelines when and how to comment classes and methods ? > What about inline comments ? > > >

May 17, 2016

Re: [Pharo-users] Retina support in Pharo

by Serge Stinckwich

On Tue, May 17, 2016 at 10:21 PM, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > On 17 May 2016 at 22:14, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> My email was _not_ about judging the community effort, but more on whether >> pharo work on a Retina laptop. >> What happens if Pharo is launched on a retina computer? > > > You get the same thing as on a non-retina display, except instead of each > fuzzy pixel you get a visibly sharper square made of 2Ã2 retina pixels. From > sufficiently far away there's no difference, but when you're right in front > of it you can see the pixelation, especially for text and compared to > HiDPI-enabled apps in nearby windows. I'm still having these peaky shadowed lines when I move the windows on my retina screen. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 17, 2016

Re: [Pharo-users] Retina support in Pharo

by Alexandre Bergel

Okay, this is what I suspected. So buying a new laptop will not prevent me from using Pharo :-) Alexandre > On May 17, 2016, at 2:38 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > it works. > just fonts could be better (and eventually, they will). > > Esteban > >> On 17 May 2016, at 21:32, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> I am about to buy a new laptop. Pharo does not work with Retina display? >> How can it be? >> >> Alexandre >> >> >>> On May 17, 2016, at 2:13 PM, Luis Felipe Strano Moraes <luis.strano(a)gmail.com> wrote: >>> >>> I asked about this just a few days ago, here's the reply: >>> >>> http://forum.world.st/Pharo-and-HiDPI-tc4894853.html >>> >>> >>> >>> On Mon, May 16, 2016 at 10:37 PM, markm <mjmzen(a)gmail.com> wrote: >>> Hi >>> >>> Is it possible to get Pharo (4 or 5) to run with retina support on OS X? I >>> have tried searching for some answers, but alas could only find a handful of >>> posts from a few years back. >>> >>> Any help much appreciated! >>> >>> >>> Mark >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Retina-support-in-Pharo-tp4895245.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> >>> >>> >>> -- >>> LuÃs Felipe Strano Moraes >>> http://www.strano.org >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 17, 2016