[Pharo-dev] [pharo-project/pharo-core] eaac18: 60030

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

Re: [Pharo-dev] What's new in Pharo 5.0

> On 24 May 2016, at 07:41, Sven Van Caekenberghe wrote: > > >> On 24 May 2016, at 03:37, Sean P. DeNigris wrote: >> >> Sean P. DeNigris wrote >>> Is there a more complete description than the announcement? >> >> I should've mentioned that I did see the

Re: [Pharo-dev] What's new in Pharo 5.0

> On 24 May 2016, at 04:00, Sean P. DeNigris wrote: > > Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages > with no class comments. The missing class comments are totally unacceptable, we should refuse these. Apart from BlueInk (a code

Re: [Pharo-dev] What's new in Pharo 5.0

> On 24 May 2016, at 03:37, Sean P. DeNigris wrote: > > Sean P. DeNigris wrote >> Is there a more complete description than the announcement? > > I should've mentioned that I did see the link to the bugtracker, but I'm > looking for some middle ground between the 5

Re: [Pharo-dev] What's new in Pharo 5.0

Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages with no class comments. How would a new user discover what these are? Also, not new to Pharo 5.0, but thinking as a new user... Nautilus presents the system as an overwhelming mess of top level packages. I guess this is

Re: [Pharo-dev] What's new in Pharo 5.0

Sean P. DeNigris wrote > Is there a more complete description than the announcement? I should've mentioned that I did see the link to the bugtracker, but I'm looking for some middle ground between the 5 bullet points in the announcement and the 2400+ issues tagged for Pharo 5.0 - Cheers,

[Pharo-dev] What's new in Pharo 5.0

Is there a more complete description than the announcement? I've been dutifully following the mailing lists, but don't feel like I have a real handle on what the new features are and why they matter. Thanks! - Cheers, Sean -- View this message in context:

Re: [Pharo-dev] compiledcode ?

Thanks and a nice one please :) Le 23/5/16 à 07:18, Clément Bera a écrit : I will do a slice today. On Mon, May 23, 2016 at 12:49 AM, Nicolai Hess > wrote: Would it be possible to add some comments, please. CompiledMethod is

Re: [Pharo-dev] cleaning the Pharo Catalog

esteban we should sit with Pavel & christophe because package validation for distribution is on Pavel's roadmap and this is probably the time to activate it. Stef Le 23/5/16 à 09:53, Esteban Lorenzano a écrit : Hi guys, I will update the Catalog for Pharo 6 and I was wondering if we

[Pharo-dev] UTF-8 regression in package saving

Hi I did not have the time to check but it seems that people cannot save code with accents using Monticello. Stef

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

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

[Pharo-dev] [pharo-project/pharo-core] 756471: 60029

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

[Pharo-dev] ConfigurationOfMerlin: to the guy who used a Halt as a cool way to let a message

don’t! I’m banning your configuration from MetaRepo because well… it messes with the update process. yes, I could and will add more solid support, but seriously, this is very bad programming. Esteban

Re: [Pharo-dev] cleaning the Pharo Catalog

On Mon, May 23, 2016 at 4:04 PM, Cyril Ferlicot Delbecque wrote: > > > On 23/05/2016 10:00, Stephan Eggermont wrote: >> Split into two categories? Those with full descriptions likely to load >> and those probably needing some updates? >> > > I like this option. Two tabs.

Re: [Pharo-dev] Mocketry names again

Yuppee! Thanks :) Doru > On May 23, 2016, at 12:18 PM, Denis Kudriashov wrote: > > And done. Version 3.4 deprecates "should got" and introduces "should receive". > All docs are updated. > > Prebuilt PDF can found here >

Re: [Pharo-dev] Mocketry names again

And done. Version 3.4 deprecates "should got" and introduces "should receive". All docs are updated. Prebuilt PDF can found here https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgress/107/artifact/book-result/Mocketry/Mocketry.pdf 2016-05-18 11:59 GMT+02:00 Denis

Re: [Pharo-dev] cleaning the Pharo Catalog

On 23/05/2016 10:00, Stephan Eggermont wrote: > Split into two categories? Those with full descriptions likely to load > and those probably needing some updates? > I like this option. Two tabs. A tab "PharoX" and a tab "Legacy" could be an idea. > Stephan > > > -- Cyril Ferlicot

[Pharo-dev] [pharo-project/pharo-core] e22bb5: 60028

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

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

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

Re: [Pharo-dev] cleaning the Pharo Catalog

On 23/05/16 09:53, Esteban Lorenzano wrote: Hi guys, I will update the Catalog for Pharo 6 and I was wondering if we should keep the “Unsorted” category… this corresponds with projects present in old MetacelloRepository repo, I added it at the beginning because I did not want those project

[Pharo-dev] cleaning the Pharo Catalog

Hi guys, I will update the Catalog for Pharo 6 and I was wondering if we should keep the “Unsorted” category… this corresponds with projects present in old MetacelloRepository repo, I added it at the beginning because I did not want those project to be lost, but in fact they are more or less