- Pharo-dev - lists.pharo.org

[Pharo-project] Nautilus feedback - format of history pulldown combo box

by Ben Coman

In Nautilus there is a combo box spanning and underneath the protocol and method panes which I shall presume to call the 'history pulldown' where items are display like: MyObject -> myMethod: (1) The usual convention in most documentation seems to be: MyObject >> myMethod: (2) Now it strangely feels uncomfortable to getting used to (1). Is there a strong directive to move away from (2), or could this be used instead of (1). cheers -ben

May 14, 2012

Re: [Pharo-project] Singleton access selector

by Carla F. Griggio

For personal/work projects, I also use #uniqueInstance. It's true that if #current is used for singleton instances it could be ambiguous. On Mon, May 14, 2012 at 7:12 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > Historically, #soleInstance can be found in st80 I think. > > Nicolas > > 2012/5/14 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > > > > On Mon, May 14, 2012 at 9:42 AM, Mariano Martinez Peck > > <marianopeck(a)gmail.com> wrote: > >> > >> > >> > >> On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris < > sean(a)clipperadams.com> > >> wrote: > >>> > >>> I've noticed we use a buffet of accessors for singletons, like > #default, > >>> #instance, #current... it'd be nice to just pick one. I like #instance, > >>> but > >>> could live with any as long as I never have to guess which one from a > >>> list > >>> again :) > >> > >> > >> Indeed. For me it depends in the case. For the general case, I like > >> #uniqueInstance. And #default and #current I use it when it is not > completly > >> singleton. I mean, when there is a class side variable storing it, but > there > >> could be also some other instances, like non-default or non-current. > > > > > > +1 > > > >> > >> > >>> > >>> > >>> Sean > >>> > >>> -- > >>> View this message in context: > >>> http://forum.world.st/Singleton-access-selector-tp4630062.html > >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >>> > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > > > >

May 14, 2012

Re: [Pharo-project] Singleton access selector

by Nicolas Cellier

Historically, #soleInstance can be found in st80 I think. Nicolas 2012/5/14 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > On Mon, May 14, 2012 at 9:42 AM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: >> >> >> >> On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris <sean(a)clipperadams.com> >> wrote: >>> >>> I've noticed we use a buffet of accessors for singletons, like #default, >>> #instance, #current... it'd be nice to just pick one. I like #instance, >>> but >>> could live with any as long as I never have to guess which one from a >>> list >>> again :) >> >> >> Indeed. For me it depends in the case. For the general case, I like >> #uniqueInstance. And #default and #current I use it when it is not completly >> singleton. I mean, when there is a class side variable storing it, but there >> could be also some other instances, like non-default or non-current. > > > +1 > >> >> >>> >>> >>> Sean >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Singleton-access-selector-tp4630062.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >

May 14, 2012

Re: [Pharo-project] [Seaside] Zinc as static file server

by Sven Van Caekenberghe

Paul, On 12 May 2012, at 23:59, Sven Van Caekenberghe wrote: > I'll have a look later on (I have little time this weekend). > > We also need at least one simple test (another one of Marcus' quotes; if there is no actively run test, it does not exist). We just need an extra version of #testIfModifiedSinceNotModified directly on a local server, it will require some setup, be it should be doable. I integrated your changes and added 3 tests: --- Name: Zinc-HTTP-SvenVanCaekenberghe.275 Author: SvenVanCaekenberghe Time: 14 May 2012, 10:59:51 am UUID: 94f2451b-b7e0-4d74-866b-d55b01c98ed9 Ancestors: Zinc-HTTP-PaulDeBruicker.274 refactored ZnStaticFileServerDelegate a bit: - store expiration times as seconds in #defaultMimeTypeExpiration & #mimeTypeExpiration map - add not only Cache-Control but Expires header as well - removed unused #responseForFile: fixed a bug in ZnMessage>>#clearEntity (didn't #close streaming entities with HEAD requests) --- Name: Zinc-Tests-SvenVanCaekenberghe.142 Author: SvenVanCaekenberghe Time: 14 May 2012, 11:11:41 am UUID: 9f8498a3-c576-4844-a0f5-bafc5c5cbeca Ancestors: Zinc-Tests-SvenVanCaekenberghe.141 added ZnStaticFileServerDelegateTests for - expiration - cache-control - if-modified-since, not-modified --- Have a look and tell me what you think. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

May 14, 2012

Re: [Pharo-project] Notify progress with Announcements instead of Exceptions

by Esteban Lorenzano

Hi, On Mon, May 14, 2012 at 6:18 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > A few updates... > * String>>displayProgressAt:from:to:during: has "deprecated" in the > comment, > but is not in a deprecated category. The timestamp is 9/7/11 which puts it > either 1.2 or early 1.3, but either way, it should be removed for 2.0, > right? There is only one sender in the image, which can easily be fixed to > call #displayProgressFrom:to:during: > * String>>displayProgressFrom:to:during: should probably delegate to the > UIManager's displayProgress:from:to:during: > * Progress should have its own announcer. The progress could be something > that doesn't alter the system, so it doesn't really fit into system > announcer. > I don't like the idea of having several notification centers...I think that approach tends inevitably to chaos. instead, I much prefer an unique notification center for all system... I do think it fits System Announcer (as any other system announce), and you just receive notification if you are registered to do so... so, why not? Esteban > > -- > View this message in context: > http://forum.world.st/Notify-progress-with-Announcements-instead-of-Excepti… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

May 14, 2012

Re: [Pharo-project] Semantic Versioning

by Philippe Marschall

On 05/14/2012 04:45 AM, Sean P. DeNigris wrote: > Do you guys know about this? Yes, Eclipse uses it, successfully, for a decade. > This seems like it could fit really well with > Metacello... I don't think you'd be happy with the consequences. First you'd have to define what is API which is hard because everything is public in Smalltalk. And then you have to live by it which means you have much less freedom how you version things. Cheers Philippe

May 14, 2012

Re: [Pharo-project] Singleton access selector

by Esteban Lorenzano

On Mon, May 14, 2012 at 9:42 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > >> I've noticed we use a buffet of accessors for singletons, like #default, >> #instance, #current... it'd be nice to just pick one. I like #instance, >> but >> could live with any as long as I never have to guess which one from a list >> again :) >> > > Indeed. For me it depends in the case. For the general case, I like > #uniqueInstance. And #default and #current I use it when it is not > completly singleton. I mean, when there is a class side variable storing > it, but there could be also some other instances, like non-default or > non-current. > +1 > > >> >> Sean >> >> -- >> View this message in context: >> http://forum.world.st/Singleton-access-selector-tp4630062.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

May 14, 2012

[Pharo-project] Pharo Kernel job working again

by Pavel Krivanek

Hi, the Pharo Kernel job working again. This two issues are related: http://code.google.com/p/pharo/issues/detail?id=5890&thanks=5890&ts=1336981… http://code.google.com/p/pharo/issues/detail?id=5889&thanks=5889&ts=1336981… Cheers, -- Pavel

May 14, 2012

Re: [Pharo-project] Singleton access selector

by Mariano Martinez Peck

On Mon, May 14, 2012 at 6:24 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > I've noticed we use a buffet of accessors for singletons, like #default, > #instance, #current... it'd be nice to just pick one. I like #instance, but > could live with any as long as I never have to guess which one from a list > again :) > Indeed. For me it depends in the case. For the general case, I like #uniqueInstance. And #default and #current I use it when it is not completly singleton. I mean, when there is a class side variable storing it, but there could be also some other instances, like non-default or non-current. > > Sean > > -- > View this message in context: > http://forum.world.st/Singleton-access-selector-tp4630062.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

May 14, 2012

[Pharo-project] [update 2.0] #20073

by Marcus Denker

20073 ----- Issue 5887: Less Sensor hardcoded http://code.google.com/p/pharo/issues/detail?id=5887 Issue 5839: TestRunner Run Coverage fails. http://code.google.com/p/pharo/issues/detail?id=5839 Issue 5876: StringMorphAttributeScanner>>initializeFromStringMorph: http://code.google.com/p/pharo/issues/detail?id=5876 -- Marcus Denker -- http://marcusdenker.de

May 14, 2012