April 2015 - Pharo-dev - lists.pharo.org

[Reflectivity] MetaLinks with metalevel

by Marcus Denker

Hi, The next step: meta level support. Imagine you put a link in a method like OrderedCollection>>#add:, and then the meta level itself class that method againâ¦ endless loop. This e.g would happen easily if you would use a link to put a watch-point somewhere... With this Slice: https://pharo.fogbugz.com/f/cases/15447/Links-with-MetaContext <https://pharo.fogbugz.com/f/cases/15447/Links-with-MetaContext> MetaLinks now can optionally model the meta-level: when calling a link, it is increased. This happens only when setting a level explicitly with #level: like here: link := MetaLink new metaObject: <something>; selector: #someSelector level: 0. Keep in mind that it is fairly heavy, using a Process-Local variable. On the TODO: -> support for links on primitive methods (by wrapping them) -> parameters for conditions -> parameters for the method called on the meta object -> âsymbolicâ meta objects #object, #node and #class -> links on Slots -> links on Globals and of course breakpoints, we have now everything already that we need. Marcus

April 29, 2015

Re: [Pharo-dev] Rectangle Center

by Peter UhnÃ¡k

On Wed, Apr 29, 2015 at 3:51 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 29 Apr 2015, at 15:18, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Natalia Tymchuk wrote > > Should it really be like that? > > > The problem is that you can't have half-a-pixel if a dimension is odd > > > Well, the methods is not called #centerPixel, nor is the class called > PixelatedRectangle. Both #origin and #corner return not rounded values. And > any way, I invite everyone to read the bug report by Tommaso, he described > in a really nice way: > https://pharo.fogbugz.com/f/cases/15445/Rectangle-center-not-really-a-cente… > I thought so too, but if you read the class comment: "I represent a rectangular area of the screen." So it seems designed for screen, and screen operates on whole pixels. Thus there is no reason to round #origin or #corner because it will be always integer (for screen). So maybe split into Rectangle (=An actual rectangle) without rounding and ScreenRectangle? Peter

April 29, 2015

Re: [Pharo-dev] Rectangle Center

by Ben Coman

On Wed, Apr 29, 2015 at 9:18 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Natalia Tymchuk wrote > > Should it really be like that? > > The problem is that you can't have half-a-pixel if a dimension is odd > > > Will it be more applicable with the move to vector basis of Athens? cheers -ben

April 29, 2015

Re: [Pharo-dev] Class Comment Template Suggestion

by Ben Coman

+1 -- I always liked the first person feel I got from Smalltalk class comments. You might add something like comments should be written in "first person from the perspective of the class" -0.5 -- Maybe the third person CRC style is better for external documentation (?) cheers -ben On Wed, Apr 29, 2015 at 9:17 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > The class comment template begins: "For the Class part: State the name of > the class with one line description: For example, I'm xxx the root of the > hierarchy of visitor objects." > > Unlike a traditional CRC card, we are already in a live programming > environment with good tools! So the class name is duplicated info (the > browser already shows this) which will have to be manually changed on a > class rename. Also, the specific example provides an implementation detail > duplicated by the class hierarchy tree already shown in the browser. I'd > like to change it to: "For the Class part: State a one line summary. For > example, "I represent a paragraph of text."" > > Any objections? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Class-Comment-Template-Suggestion-tp4822890.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 29, 2015

Re: [Pharo-dev] Rectangle Center

by Yuriy Tymchuk

> On 29 Apr 2015, at 15:18, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Natalia Tymchuk wrote >> Should it really be like that? > > The problem is that you can't have half-a-pixel if a dimension is odd Well, the methods is not called #centerPixel, nor is the class called PixelatedRectangle. Both #origin and #corner return not rounded values. And any way, I invite everyone to read the bug report by Tommaso, he described in a really nice way: https://pharo.fogbugz.com/f/cases/15445/Rectangle-center-not-really-a-cente… <https://pharo.fogbugz.com/f/cases/15445/Rectangle-center-not-really-a-cente…> Uko > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Rectangle-Center-tp4822883p4822891.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 29, 2015

Rectangle Center

by Natalia Tymchuk

Hello. I found very interesting method. Should it really be like that? Or maybe we need to rename this method as #roundedCenter and add the normal #center with usual division? Best regards, Natalia

April 29, 2015

Re: [Pharo-dev] Rectangle Center

by Sean P. DeNigris

Natalia Tymchuk wrote > Should it really be like that? The problem is that you can't have half-a-pixel if a dimension is odd ----- Cheers, Sean -- View this message in context: http://forum.world.st/Rectangle-Center-tp4822883p4822891.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 29, 2015

Class Comment Template Suggestion

by Sean P. DeNigris

The class comment template begins: "For the Class part: State the name of the class with one line description: For example, I'm xxx the root of the hierarchy of visitor objects." Unlike a traditional CRC card, we are already in a live programming environment with good tools! So the class name is duplicated info (the browser already shows this) which will have to be manually changed on a class rename. Also, the specific example provides an implementation detail duplicated by the class hierarchy tree already shown in the browser. I'd like to change it to: "For the Class part: State a one line summary. For example, "I represent a paragraph of text."" Any objections? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Class-Comment-Template-Suggestion-tp4822890.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 29, 2015

Re: [Pharo-dev] ZnUrl and closePath

by Sven Van Caekenberghe

=== Name: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.52 Author: SvenVanCaekenberghe Time: 29 April 2015, 2:50:03.993582 pm UUID: b8c7646e-74ff-4200-aa7f-4fdcd1d13dd2 Ancestors: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.51 Modify ZnUrl>>#closePath to only add a / if there is no trailing one already (Thx Norbert Hartl) === > On 29 Apr 2015, at 14:27, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 29.04.2015 um 13:53 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> Norbert, >> >>> On 29 Apr 2015, at 13:07, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> I'm not sure the behaviour of ZnUrl>>#closePath is the desired one. >>> >>> 'http://foo/a/b/c/' asZnUrl closePath >>> >>> gives >>> >>> http://foo/a/b/c// >>> >>> It adds a slash if the #isSlash returns false. #isSlash indicated only the server root and not (what I was thinking) it returns true on trailing slash. >>> IMHO #isSlash should be a test for trailing slash and #isRootPath should be a test for a non-existing or / path. >>> >>> Norbert >> >> #isSlash was/is intended to be what it is, but indeed #closePath could maybe be improved. >> >> What about >> >> closePath >> self isDirectoryPath >> ifFalse: [ self addPathSegment: #/ ] >> >> ? >> >> Would that work for your use case ? > > Sure. Didn't know about isDirectoryPath. > > Norbert

April 29, 2015

Re: [Pharo-dev] ZnUrl and closePath

by Norbert Hartl

> Am 29.04.2015 um 13:53 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Norbert, > >> On 29 Apr 2015, at 13:07, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> I'm not sure the behaviour of ZnUrl>>#closePath is the desired one. >> >> 'http://foo/a/b/c/' asZnUrl closePath >> >> gives >> >> http://foo/a/b/c// >> >> It adds a slash if the #isSlash returns false. #isSlash indicated only the server root and not (what I was thinking) it returns true on trailing slash. >> IMHO #isSlash should be a test for trailing slash and #isRootPath should be a test for a non-existing or / path. >> >> Norbert > > #isSlash was/is intended to be what it is, but indeed #closePath could maybe be improved. > > What about > > closePath > self isDirectoryPath > ifFalse: [ self addPathSegment: #/ ] > > ? > > Would that work for your use case ? Sure. Didn't know about isDirectoryPath. Norbert

April 29, 2015