Re: [Pharo-dev] do we "how to use Announcements" somewhere

Le 20/04/2017 à 23:47, Peter Uhnak a écrit : > I was just explaining how Announcer/Announcements work to somebody because I > couldn't find any online resource, but I thought I saw it somewhere. > > Do we have it explained in some book? > > Peter > Hi, Check the Help Browser in Pharo. In

Re: [Pharo-dev] #renameTo: and #moveTo:

2017-04-20 9:53 GMT+02:00 Alistair Grant : > On Wed, Apr 19, 2017 at 09:57:41PM +0200, Nicolas Cellier wrote: > > 2017-04-19 21:41 GMT+02:00 Alistair Grant : > > > > Hi All, > > > > While recently running the test suite I've been getting

[Pharo-dev] do we "how to use Announcements" somewhere

I was just explaining how Announcer/Announcements work to somebody because I couldn't find any online resource, but I thought I saw it somewhere. Do we have it explained in some book? Peter

Re: [Pharo-dev] [Vm-dev] Fwd: Nix package for Pharo flavor of opensmalltalk-vm

Hi Ben, Thanks for explaining the process for maintaining the stable vs development versions and illustrating it with data. I need to understand the Pharo Launcher better. Could indeed be the best strategy is to focus on supporting that well. That's basically the approach that Damien has taken

[Pharo-dev] [pharo-project/pharo-core] 7bde98: 60468

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7bde98ed1694390205b9b93c81ebfffc82ed2ff3 https://github.com/pharo-project/pharo-core/commit/7bde98ed1694390205b9b93c81ebfffc82ed2ff3 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60468 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] In the quest of a new iterator :)

2017-04-20 13:31 GMT-03:00 Nicolas Cellier : > > > 2017-04-20 17:06 GMT+02:00 Ben Coman : > On the other hand, we have #keysAndValuesDo: which competes with > #withIndexDo: and is a bit more portable across dialects > (it's just that it

Re: [Pharo-dev] #renameTo: and #moveTo:

Hi Stef, On Thu, Apr 20, 2017 at 08:11:31PM +0200, Stephane Ducasse wrote: > Thanks for looking at this. We should really improve this part. No problem. I've just finished coding and testing. The one part I'm not completely happy with is what I mentioned earlier: I'm not aware of any way

[Pharo-dev] Pharo 5 and retina displays in 2017?

I mentioned this last year - and I’m wondering if there is any news or developments on making Pharo look better on higher end hardware like Macbook’s and Dell’s? I keep dipping into Pharo but every time I see the blurry screen, it just takes away the shine for me (which is a bit sad)? Is Bloc

[Pharo-dev] [pharo-project/pharo-core] bf8db7: 60467

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: bf8db76012347d23e7b9b78176aebbc6e9be413f https://github.com/pharo-project/pharo-core/commit/bf8db76012347d23e7b9b78176aebbc6e9be413f Author: Jenkins Build Server Date:

Re: [Pharo-dev] #renameTo: and #moveTo:

On Wed, Apr 19, 2017 at 09:57:41PM +0200, Nicolas Cellier wrote: > 2017-04-19 21:41 GMT+02:00 Alistair Grant : > > Hi All, > > While recently running the test suite I've been getting failures in > FileLocatorTest>>testMoveTo if the working directory when the

Re: [Pharo-dev] Epicea should ask before recovering

I as trying to write little tips. But I realized new issue 19957 2017-04-20 3:34 GMT+02:00 Ben Coman : > > > On Wed, Apr 19, 2017 at 9:42 PM, Rajula Vineet > wrote: >

[Pharo-dev] Spotter feature idea/request - exclusion filter

I had a poke at this but couldn't find my way into how Spotter filters work, so I'll just pass on the idea. Wanting to look at implementers of #withIndex* several tests are mixed in the result that it would be nice to eliminate by typing "subtract test" like this... " -test " much like I'd do in

Re: [Pharo-dev] [Vm-dev] Fwd: Nix package for Pharo flavor of opensmalltalk-vm

On Thu, Apr 20, 2017 at 10:19 PM, Ben Coman wrote: > Moved thread back to pharo-dev for image-side nix packaging discussion. Whoops. Try again, back to pharo-dev. > > On Thu, Apr 20, 2017 at 3:59 PM, Luke Gorrie wrote: >> >> On 20 April 2017 at 06:03, Ben

Re: [Pharo-dev] In the quest of a new iterator :)

The first thing I thought of was: | anArray | anArray := #(#Object #subclass: #Point #instanceVariableNames: 'x y' #classVariableNames: '' #package: 'Kernel-BasicObjects'). (1 to: anArray size by: 2) collect: [:i | anArray at: i] All the best, Ron Teitelbaum On Thu, Apr 20, 2017 at 2:04 AM

Re: [Pharo-dev] In the quest of a new iterator :)

2017-04-20 17:06 GMT+02:00 Ben Coman : > > > On Thu, Apr 20, 2017 at 3:17 AM, Stephane Ducasse > wrote: > >> why? >> Iterators are powerful and avoid that we all reinvent the wheel in our >> own corners. >> >> About keySelect: I do not see the

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60467 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] In the quest of a new iterator :)

This is what I was looking for. On Wed, Apr 19, 2017 at 10:54 PM, Sven Van Caekenberghe wrote: > There are already #pairsDo: and #pairsCollect: that could be used: > > #(a b c d e f g h) pairsCollect: [ :x :y | y ] > > => #(#b #d #f #h) > > > On 19 Apr 2017, at 22:12, Tudor

Re: [Pharo-dev] In the quest of a new iterator :)

Yes this is probably what I was also looking for. On Wed, Apr 19, 2017 at 11:07 PM, Peter Uhnak wrote: > We already have > > * #withIndexCollect: > * #withIndexDo: > > > So why not #withIndexSelect: ? > > #(#Object #subclass: #Point #instanceVariableNames:) withIndexSelect: [

Re: [Pharo-dev] In the quest of a new iterator :)

Peter can you send an implementation and a bunch of tests :) Stef On Wed, Apr 19, 2017 at 11:07 PM, Peter Uhnak wrote: > We already have > > * #withIndexCollect: > * #withIndexDo: > > > So why not #withIndexSelect: ? > > #(#Object #subclass: #Point #instanceVariableNames:)

Re: [Pharo-dev] In the quest of a new iterator :)

Hi nicolas Yes but it looks strange :) but indeed having a #keysAndValuesSelect: #keysAndValuesCollect: And it would be good to have #withIndexDo: following the same orders for argument. On Thu, Apr 20, 2017 at 6:31 PM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > >

Re: [Pharo-dev] Pharo 5 and retina displays in 2017?

retina should be supported. Now we need to get rid of bug induced by freetype and what would be better is to have the time to breath and think. Because right now FFI and 64 bits sucked most of the attention of esteban. For Bloc yes it got more traction but we will know more during PharoDays I

Re: [Pharo-dev] #renameTo: and #moveTo:

Thanks for looking at this. We should really improve this part. On Wed, Apr 19, 2017 at 9:41 PM, Alistair Grant wrote: > Hi All, > > While recently running the test suite I've been getting failures in > FileLocatorTest>>testMoveTo if the working directory when the test >

Re: [Pharo-dev] changing default theme to DarkTheme

I see in 60467 that the deed is done. Okay, so moving forward... be prepared ;) for a surge of feedback as a bunch of us dark-theme-newbies start using it in earnest. I understand those that been using it a while already are obviously happy with how its tuned, and probably not many things can be

Re: [Pharo-dev] In the quest of a new iterator :)

On Thu, Apr 20, 2017 at 12:17:35AM +0300, Yuriy Tymchuk wrote: > I second the Peter???s idea. I don???t think that we need a dedicated > index-based select when we already have withIndex*. Also one year after > adding withIndexSelect: we can mine public repos and see how many projects > use the