Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

t that way you can be compatible and use the new > methods. > > Thanks > T. > > > Gesendet: Donnerstag, 28. September 2017 um 10:19 Uhr > Von: "Esteban Lorenzano" <esteba...@gmail.com> > An: "Pharo Development List" <pharo-dev@lists.phar

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

teban Lorenzano" <esteba...@gmail.com> An: "Pharo Development List" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])   On 28 Sep 2017, at 10:01, Denis Kudriashov <dionisi...@gmail.com[mailto

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

> On 28 Sep 2017, at 10:01, Denis Kudriashov wrote: > > So it is integrated it Pharo 7 > > 2017-09-18 11:09 GMT+02:00 Denis Kudriashov >: > I did pull request for issue 20426 >

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

So it is integrated it Pharo 7 2017-09-18 11:09 GMT+02:00 Denis Kudriashov : > I did pull request for issue 20426 > . > > Interesting that Iceberg uses pinning in couple of places. I not touch it > because it

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

On Mon, Sep 18, 2017 at 10:38 PM, Todd Blanchard wrote: > I think the asymmetry would drive me bananas. > I prefer the original set. > +1. Think of it this wayun-"pinInMemory" cheers -ben > On Sep 18, 2017, at 7:28 AM, Tudor Girba wrote: > >

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

2017-09-18 16:28 GMT+02:00 Tudor Girba : > Hi, > > In this case, it would sound better to have: > - pinInMemory > - unpin*From*Memory > Then first message can be named #pinToMemory. But I prefer simple InMemory for both cases. > - isPinnedInMemory > - setPinnedInMemory: >

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

I think the asymmetry would drive me bananas. I prefer the original set. > On Sep 18, 2017, at 7:28 AM, Tudor Girba wrote: > > Hi, > > In this case, it would sound better to have: > - pinInMemory > - unpinFromMemory > - isPinnedInMemory > - setPinnedInMemory: > >

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi, In this case, it would sound better to have: - pinInMemory - unpinFromMemory - isPinnedInMemory - setPinnedInMemory: Cheers, Doru > On Sep 14, 2017, at 10:17 AM, Denis Kudriashov wrote: > > Hello. > > I guess we are agree to rename. I will prepare pull request for

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

I did pull request for issue 20426 . Interesting that Iceberg uses pinning in couple of places. I not touch it because it would not be single commit. And I have no idea how contribute in that case. I thing we are still in process to

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

> On Sep 14, 2017, at 7:07 AM, Norbert Hartl wrote: > > > >> Am 14.09.2017 um 10:17 schrieb Denis Kudriashov : >> >> Hello. >> >> I guess we are agree to rename. I will prepare pull request for Pharo. And >> Squeak is up to you. >> >> Here is the

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

> Am 14.09.2017 um 10:17 schrieb Denis Kudriashov : > > Hello. > > I guess we are agree to rename. I will prepare pull request for Pharo. And > Squeak is up to you. > > Here is the new messages: > - pinInMemory > - unpinInMemory > - isPinnedInMemory > -

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hello. I guess we are agree to rename. I will prepare pull request for Pharo. And Squeak is up to you. Here is the new messages: - pinInMemory - unpinInMemory - isPinnedInMemory - setPinnedInMemory: What was decision about #pinInMemoryDuring: ? Do we need it? 2017-09-14 9:28 GMT+02:00 H.

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

+1 for pinInMemory It explains what it does. On 9/14/17, Eliot Miranda wrote: > Hi Norbert, > >> On Sep 13, 2017, at 3:18 PM, Norbert Hartl wrote: >> >> >>> Am 14.09.2017 um 00:09 schrieb Eliot Miranda : >>> >>> Hi Denis,

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi Norbert, > On Sep 13, 2017, at 3:18 PM, Norbert Hartl wrote: > > >> Am 14.09.2017 um 00:09 schrieb Eliot Miranda : >> >> Hi Denis, >> >> On Tue, Sep 12, 2017 at 9:29 AM, Denis Kudriashov >> wrote: >>> Hi Eliot. >>> >>>

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

On Thu, Sep 14, 2017 at 12:18:34AM +0200, Norbert Hartl wrote: > > > Am 14.09.2017 um 00:09 schrieb Eliot Miranda : > > > > Hi Denis, > > > > On Tue, Sep 12, 2017 at 9:29 AM, Denis Kudriashov > > wrote: > > Hi Eliot.

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

> Am 14.09.2017 um 00:09 schrieb Eliot Miranda : > > Hi Denis, > > On Tue, Sep 12, 2017 at 9:29 AM, Denis Kudriashov > wrote: > Hi Eliot. > > I know and I only talk about new messages. I am not trying to rethink

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi Denis, On Tue, Sep 12, 2017 at 9:29 AM, Denis Kudriashov wrote: > Hi Eliot. > > I know and I only talk about new messages. I am not trying to rethink full > meta model of Smalltalk. > By the way #class is very common message and it is handy to use short > name. But

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

+1 > On Aug 31, 2017, at 1:29 AM, Pavel Krivanek wrote: > > I would use pinInMemory

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi Eliot. I know and I only talk about new messages. I am not trying to rethink full meta model of Smalltalk. By the way #class is very common message and it is handy to use short name. But pinning messages will be used rarely in very specific applications. So no much sense to preserve them in

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi Denis, > On Sep 12, 2017, at 2:39 AM, Denis Kudriashov wrote: > > I am really wonder guys. I thought you are not big funs of Object protocol. > Current pinning messages are a new set of very generic messages in the Object. Yes, and that's because this is a fundamental

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

On 9/12/17, Denis Kudriashov wrote: > I am really wonder guys. I thought you are not big funs of Object protocol. > Current pinning messages are a new set of very generic messages in the > Object. > > About Norbert idea. > - bePinnedObject is not bad convention. >But I

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

I am really wonder guys. I thought you are not big funs of Object protocol. Current pinning messages are a new set of very generic messages in the Object. About Norbert idea. - bePinnedObject is not bad convention. But I would prefer the memory suffix because it reflects the low level behaviour.

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

od names like #isPinnedTab. #isPinnedToWindow > or #isPinnedToBrowser) > > Bye > T. > > > Gesendet: Montag, 11. September 2017 um 14:16 Uhr > Von: "Esteban Lorenzano" <esteba...@gmail.com> > An: "Pharo Development List" <pharo-dev@lists.pharo.org> > Bet

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

edTab. #isPinnedToWindow > or #isPinnedToBrowser) > > Bye > T. > > > Gesendet: Montag, 11. September 2017 um 14:16 Uhr > Von: "Esteban Lorenzano" <esteba...@gmail.com> > An: "Pharo Development List" <pharo-dev@lists.pharo.org> > Betreff: Re:

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

or #isPinnedToBrowser) Bye T.   Gesendet: Montag, 11. September 2017 um 14:16 Uhr Von: "Esteban Lorenzano" <esteba...@gmail.com> An: "Pharo Development List" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objec

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

I understand it's not about the intention revealing of the selector, but about not making #pin:/#unpin: a kind of "reserved selector" as many implemented in Object. Regards, Esteban A. Maringolo 2017-09-11 9:16 GMT-03:00 Esteban Lorenzano : > yes, me :) > > I do not see a

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

yes, me :) I do not see a reason to change them, tbh. for me they are comprensible as they are now and it does not adds more information pinInMemory or pinMemory. Esteban > On 11 Sep 2017, at 11:56, Denis Kudriashov wrote: > > Anybody else? > > 2017-08-31 10:29

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

I don't think we should come up with a new naming scheme every now and then. If I look at the read-only support there the selector is beReadOnlyObject so in this case it should be bePinnedObject I didn't like the extra Object at the end but now I think it makes it clear and still steps aside

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Anybody else? 2017-08-31 10:29 GMT+02:00 Pavel Krivanek : > > > 2017-08-31 10:24 GMT+02:00 Denis Kudriashov : > >> Hi. >> >> We now have very generic message names: >> - pin >> - unpin >> - setPinned: >> - isPinned >> >> Problem that they collide

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

2017-08-31 10:24 GMT+02:00 Denis Kudriashov : > Hi. > > We now have very generic message names: > - pin > - unpin > - setPinned: > - isPinned > > Problem that they collide with possible domain related names. > For example I implemented pinning of tabs in Calypso and I found

[Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi. We now have very generic message names: - pin - unpin - setPinned: - isPinned Problem that they collide with possible domain related names. For example I implemented pinning of tabs in Calypso and I found that I overrides #pin and #isPinned messages. Then I fix it with different names.