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

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

by Denis Kudriashov

2018-04-12 12:31 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > In future it should be completely removed (you know how RPackage is ugly >> because of that). Only old text code formats will use star protocols. > > >> So Calypso is a step to remove this "star habit" from users. >> > > What is the correct way to generate such methods then? > I use Something compile: 'method' classified: '*OtherPackage' ... but if > the star convention is removed? > It should be simple package parameter like: Something compile: 'method' inPackage: #'OtherPackage' asPackage > > Thanks, > Peter >

April 12, 2018

Re: [Pharo-dev] How to remove the extra protocol in Calypso

by Stephane Ducasse

I want that the tools let me to get focused on my task. And now I cannot disable. I do not want to live in a place with neon ads all over the place, I want a calm place where I can pick the tools I need when I need them and that they are not impose on me. BTW I will not adapt the mooc so students will use Pharo 50. Why because I'm fedup to be the idiot in this community upgrading books, slides and videos. Yes you can think that "oh we we cannot invent new stuff then we should better stop" - first I would like to see the people that think that to write more than a page on doc. - second paying attention to not impose new stuff for the shake on it would be better Stef On Thu, Apr 12, 2018 at 12:50 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > I want to remove > critiques > overridden > overrides > > THEY GET IN MY WAY. > Sorry to have to shout but I have the impression that I'm not heard. > > Ideally we could have a menu item to show extras things. RIght now > each time I browse my class I stop > because I have to interpret these new infroamtion and I'm not > interested in them. > > Stef > > > On Thu, Apr 12, 2018 at 12:46 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> Hi >> >> There are too much information by default I'm overhelmed. >> I would like to remove the following protocols >> >> critiques

April 12, 2018

Re: [Pharo-dev] How to remove the extra protocol in Calypso

by Stephane Ducasse

I want to remove critiques overridden overrides THEY GET IN MY WAY. Sorry to have to shout but I have the impression that I'm not heard. Ideally we could have a menu item to show extras things. RIght now each time I browse my class I stop because I have to interpret these new infroamtion and I'm not interested in them. Stef On Thu, Apr 12, 2018 at 12:46 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > There are too much information by default I'm overhelmed. > I would like to remove the following protocols > > critiques

April 12, 2018

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

by Stephane Ducasse

I do not see why we should remove star protocols. It will break many things. Why can't we focus on important next steps. On Thu, Apr 12, 2018 at 12:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > But it shows notification why it does not supported and what to use instead. > (it was not available in old versions) > > Idea to move away from star convention. Calypso gives you explicit tools to > add method to the package. Most simple is checkbox "extension" in the status > bar of method editor. > For now star convention will stay internal implementation detail of > RPackage. In future it should be completely removed (you know how RPackage > is ugly because of that). Only old text code formats will use star > protocols. > > So Calypso is a step to remove this "star habit" from users. > > 2018-04-12 11:42 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> in calypso. >> * was simple and nice. >> Now if I create a protocol with a star it got eaten and no protocol >> will be created. >> >> Stef >> >

April 12, 2018

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

by Stephane Ducasse

You see. You pushed this idea and at then end we will have to handle the mess. I do not see why we cannot simply support *. Seriously why eveybody on earth has to inforce their own view. Now to declare an extension (it took me at least 10 min) we have to create a protocol then to click on it then to select an existing package! Why it cannot stay and be simple On Thu, Apr 12, 2018 at 12:10 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > But it shows notification why it does not supported and what to use instead. > (it was not available in old versions) > > Idea to move away from star convention. Calypso gives you explicit tools to > add method to the package. Most simple is checkbox "extension" in the status > bar of method editor. > For now star convention will stay internal implementation detail of > RPackage. In future it should be completely removed (you know how RPackage > is ugly because of that). Only old text code formats will use star > protocols. > > So Calypso is a step to remove this "star habit" from users. > > 2018-04-12 11:42 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> in calypso. >> * was simple and nice. >> Now if I create a protocol with a star it got eaten and no protocol >> will be created. >> >> Stef >> >

April 12, 2018

How to remove the extra protocol in Calypso

by Stephane Ducasse

Hi There are too much information by default I'm overhelmed. I would like to remove the following protocols critiques

April 12, 2018

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

by Peter UhnÃ¡k

> > In future it should be completely removed (you know how RPackage is ugly > because of that). Only old text code formats will use star protocols. > So Calypso is a step to remove this "star habit" from users. > What is the correct way to generate such methods then? I use Something compile: 'method' classified: '*OtherPackage' ... but if the star convention is removed? Thanks, Peter

April 12, 2018

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

by Denis Kudriashov

But it shows notification why it does not supported and what to use instead. (it was not available in old versions) Idea to move away from star convention. Calypso gives you explicit tools to add method to the package. Most simple is checkbox "extension" in the status bar of method editor. For now star convention will stay internal implementation detail of RPackage. In future it should be completely removed (you know how RPackage is ugly because of that). Only old text code formats will use star protocols. So Calypso is a step to remove this "star habit" from users. 2018-04-12 11:42 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > in calypso. > * was simple and nice. > Now if I create a protocol with a star it got eaten and no protocol > will be created. > > Stef > >

April 12, 2018

Re: [Pharo-dev] [TechTalk] April 12: GIT with Iceberg

by Stephane Ducasse

I will not make it but I really want. Let us know where will be the videos. Stef On Thu, Apr 12, 2018 at 9:09 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > This is today > > 5:00 PM - 7:00 PM (UTC+02:00) > > There is a calendar entry to download at: https://association.pharo.org/event-2797068 > >> On 10 Apr 2018, at 16:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> There next TechTalk will be April 12: GIT with Iceberg >> >> https://association.pharo.org/event-2797068 >> >> >> A regular chat about Pharo. Happens on Discord. >> >> The Tech talks are open to both members and non-members! >> >> Topic: GIT with Iceberg. Demo of improved UI >> >> We will send an information to all subscribers some hours before the talk starts. >> >> > >

April 12, 2018

Why can't we use * in protocol for package extension?

by Stephane Ducasse

in calypso. * was simple and nice. Now if I create a protocol with a star it got eaten and no protocol will be created. Stef

April 12, 2018