Re: [Pharo-dev] Do we kill the catalog?

Thierry Goubier wrote > If using a baseline in the Catalog forces it to be more complex… I didn't think we were discussing changing baselines themselves, just a better adapter layer than hand-edited Configs Thierry Goubier wrote > A typical git-based development is one tag or branch per pharo >

[Pharo-dev] [Pharo 7.0-dev] Build #805: 21777 Some assert:equal: and formatting cleanups in UFFI

There is a new Pharo build available! The status of the build #805 was: SUCCESS. The Pull Request #1250 was integrated: "21777 Some assert:equal: and formatting cleanups in UFFI" Pull request url: https://github.com/pharo-project/pharo/pull/1250 Issue Url:

Re: [Pharo-dev] Do we kill the catalog?

> Sent: Tuesday, April 24, 2018 at 3:42 AM > From: "Esteban Lorenzano" > To: "Pharo Development List" > Subject: Re: [Pharo-dev] Do we kill the catalog? > > hi, > > > > On 24 Apr 2018, at 00:49, monty wrote: > > > > +1. >

Re: [Pharo-dev] (no subject)

Welcome, Tristan! Please let us know how we can help you. Cheers, Doru > On Apr 24, 2018, at 5:14 PM, Tristan Debrousse > wrote: > > Hello, I am a student at Université de Bretagne Occidentale (Brest, France) > and I just began an internship project of 6 weeks

Re: [Pharo-dev] (no subject)

That's great, Tristan. Welcome ! Have fun. Sven > On 24 Apr 2018, at 17:14, Tristan Debrousse > wrote: > > Hello, I am a student at Université de Bretagne Occidentale (Brest, France) > and I just began an internship project of 6 weeks with Alain Plantec and >

[Pharo-dev] (no subject)

Hello, I am a student at Université de Bretagne Occidentale (Brest, France) and I just began an internship project of 6 weeks with Alain Plantec and Steven Costiou. The project involves the use of Pharo with Bloc to develop a GUI. -- Tristan

Re: [Pharo-dev] Do we kill the catalog?

Hi Sean, Guille, 2018-04-24 15:31 GMT+02:00 Sean P. DeNigris : > Guillermo Polito wrote >> Should we continue providing configurations that point to the >> baselines? I've read some rants against it. >> I know it may be "uncomfortable", but publishing some meta-data in a >>

Re: [Pharo-dev] Do we kill the catalog?

Guillermo Polito wrote > Should we continue providing configurations that point to the > baselines? I've read some rants against it. > I know it may be "uncomfortable", but publishing some meta-data in a > repository in XXX technology is kind of the same... This seems like an implementation

[Pharo-dev] [Pharo 7.0-dev] Build #804: 21771-testInjectingExceptionHandlerFromProcessItself-is-unstable

There is a new Pharo build available! The status of the build #804 was: SUCCESS. The Pull Request #1246 was integrated: "21771-testInjectingExceptionHandlerFromProcessItself-is-unstable" Pull request url: https://github.com/pharo-project/pharo/pull/1246 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #803: 21775 KeyPrinterMorph

There is a new Pharo build available! The status of the build #803 was: SUCCESS. The Pull Request #1249 was integrated: "21775 KeyPrinterMorph" Pull request url: https://github.com/pharo-project/pharo/pull/1249 Issue Url: https://pharo.fogbugz.com/f/cases/21775 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #802: 21766-Remove-Versionner-and-Komitter

There is a new Pharo build available! The status of the build #802 was: SUCCESS. The Pull Request #1245 was integrated: "21766-Remove-Versionner-and-Komitter" Pull request url: https://github.com/pharo-project/pharo/pull/1245 Issue Url: https://pharo.fogbugz.com/f/cases/21766 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #801: 21756-Add-roots-and-hierarchyRoots-to-RPackage

There is a new Pharo build available! The status of the build #801 was: SUCCESS. The Pull Request #1243 was integrated: "21756-Add-roots-and-hierarchyRoots-to-RPackage" Pull request url: https://github.com/pharo-project/pharo/pull/1243 Issue Url: https://pharo.fogbugz.com/f/cases/21756

Re: [Pharo-dev] Do we kill the catalog?

hi, > On 24 Apr 2018, at 00:49, monty wrote: > > +1. > > Replacing is sometimes necessary (Sven's stream work is an obvious example), > but I don't see why Nautilus had to be junked rather than gradually evolved > into Calypso. that’s clearly because you didn’t see

Re: [Pharo-dev] Do we kill the catalog?

Hi all, I think that we are all aligned. Stef may be "too strong" in his way of talking, but he raised an issue: we should probably do an iteration on the catalog. And I think we all agree on that? So, what would be a list of tasks for it? (I copy past what Stef put before) - Use Metacello API.

Re: [Pharo-dev] Do we kill the catalog?

2018-04-24 7:31 GMT+02:00 Sven Van Caekenberghe : > > >> On 24 Apr 2018, at 00:49, monty wrote: >> >> +1. >> >> Replacing is sometimes necessary (Sven's stream work is an obvious example), >> but I don't see why Nautilus had to be junked rather than gradually