- Pharo-dev - lists.pharo.org

Re: [Pharo-project] OB annotation icons

by Dan Corneanu

Wouldn't be enough for deprecated methods to just use a strikethrough font style?

Oct. 22, 2008

Re: [Pharo-project] OB annotation icons

by David Roethlisberger

>> I'm not a big defender of the super send icon, but what would certainly have >> helped in your use case is an icon that denotes whether you send super to a >> method with a different selector. Then you would have spotted this problem >> maybe even quicker than if it wouldn't have had any icon. > > Is it possible to put a configuration in the preferences so one can > select what icons wants to be visible in the browser ? It is possible to do of course, but I'm not a friend of adding too many preferences for this and that... On the other hand, it seems to be impossible to find a set/configuration of icons that fits everyone's need and style. So maybe it's indeed best to just let people configure the icons they want... I will look into that. David

Oct. 22, 2008

Re: [Pharo-project] OB annotation icons

by Dan Corneanu

On Wed, Oct 22, 2008 at 12:06 PM, David Roethlisberger <squeak(a)webcitas.ch> wrote: > I'm not a big defender of the super send icon, but what would certainly have > helped in your use case is an icon that denotes whether you send super to a > method with a different selector. Then you would have spotted this problem > maybe even quicker than if it wouldn't have had any icon. Is it possible to put a configuration in the preferences so one can select what icons wants to be visible in the browser ?

Oct. 22, 2008

[Pharo-project] [update] 10102

by Marcus Denker

- Issue 277: SelfEvaluating Arrays - {$a. Array. 1} instead of {$a . Array . 1} - Issue 265: TODO: (simple): remove Browser "printOut" menu - Issue 251: remove ref Parser from getSourceFor:in: - Issue 249: add regexps to core image -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 22, 2008

Re: [Pharo-project] OB annotation icons

by David Roethlisberger

> It is absolutely evil to display anything else than if there are super > (up triangle) or sub implementations (down triangle) next to method. I > just lost 10 minutes, because of these agressive green arrow that mark > methods calling super. I couldn't figure out why the method wasn't run > as expected. Eventually I found out that I misspelled the selector > name. With the icons as they were before I would have spotted that > within less than a second (no yellow triangle would be shown in this > case). I hate that green arrow, it is absolutely useless and totally > misleading. I'm not a big defender of the super send icon, but what would certainly have helped in your use case is an icon that denotes whether you send super to a method with a different selector. Then you would have spotted this problem maybe even quicker than if it wouldn't have had any icon. David

Oct. 22, 2008

Re: [Pharo-project] OB annotation icons

by Antony Blakey

On 22/10/2008, at 6:38 PM, Lukas Renggli wrote: > It is absolutely evil to display anything else than if there are super > (up triangle) or sub implementations (down triangle) next to method. I > just lost 10 minutes, because of these agressive green arrow that mark > methods calling super. Whilst I agree that the 'calls super' is worse-than-useless, having multiple annotations can be useful if they are appropriately presented: http://linkuistics.com/ftp/Stardust-TraitAnnotation-2008-10-08.png A 'deprecated' marker would be useful in my environment. Then you'd also want to find all senders of methods for which every implementation is deprecated (or maybe just some?). Antony Blakey -------------------------- CTO, Linkuistics Pty Ltd Ph: 0438 840 787 Reflecting on W.H. Auden's contemplation of 'necessary murders' in the Spanish Civil War, George Orwell wrote that such amorality was only really possible, 'if you are the kind of person who is always somewhere else when the trigger is pulled'. -- John Birmingham, "Appeasing Jakarta"

Oct. 22, 2008

Re: [Pharo-project] OB annotation icons

by Lukas Renggli

>> Does OB have any icon associated with deprecated methods? > > There is no such icon at the moment. > If someone sends me a gif icon denoting deprecation, I will integrate it. I am sorry to come up again with that, but it sort of fits the context. It is absolutely evil to display anything else than if there are super (up triangle) or sub implementations (down triangle) next to method. I just lost 10 minutes, because of these agressive green arrow that mark methods calling super. I couldn't figure out why the method wasn't run as expected. Eventually I found out that I misspelled the selector name. With the icons as they were before I would have spotted that within less than a second (no yellow triangle would be shown in this case). I hate that green arrow, it is absolutely useless and totally misleading. Lukas :-( -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 22, 2008

Re: [Pharo-project] OB annotation icons

by David Roethlisberger

Hi Dan, > Does OB have any icon associated with deprecated methods? There is no such icon at the moment. If someone sends me a gif icon denoting deprecation, I will integrate it. David

Oct. 22, 2008

Re: [Pharo-project] Merging one-click and pharo-dev

by Lukas Renggli

>> Then, you can embed the latest one into a One-Click that >> you generate (it seems I can't generate them myself because I don't >> use MacOS, but I'm not sure). > > Don't know if you need macos, could be. (never tried it on linux). > In general it would be nice to be able to build the one-click > programmatically. If you want it working on a mac you need to make it on OS X, otherwise the resource forks are missing. Maybe there are some unix tools that could compensate that? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 22, 2008

Re: [Pharo-project] Merging one-click and pharo-dev

by Marcus Denker

On 21.10.2008, at 20:34, Damien Cassou wrote: > On Tue, Oct 21, 2008 at 7:55 PM, Marcus Denker <denker(a)iam.unibe.ch> > wrote: >> We should really think/discuss about the next one-click be based on >> the dev >> image (the non-one-click then will be the "core" image for people >> building >> deployment images, for example). > > First, you have to comment on the pharo-dev images to make them fit > your needs. Yes, I will check. And we should start to move some things into the Core (e.g. truetype + Regexps). > Then, you can embed the latest one into a One-Click that > you generate (it seems I can't generate them myself because I don't > use MacOS, but I'm not sure). Don't know if you need macos, could be. (never tried it on linux). In general it would be nice to be able to build the one-click programmatically. There should be a "one-click" package-generator in the image. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 22, 2008