- Pharo-dev - lists.pharo.org

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

by Marcus Denker

> On 24 May 2016, at 07:41, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 24 May 2016, at 03:37, Sean P. DeNigris <sean(a)clipperadams.com> 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 bullet points in the >> announcement and the 2400+ issues tagged for Pharo 5.0 > > It is our fault that such a list does not exist, but it is really, really hard to make it, since no one knows everything. It is also a huge amount of work. Yes, I was not able to do this. At some point one needs to decide: Release (finish!), as imperfect as it is, or not. Marcus

May 24, 2016

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

by Sven Van Caekenberghe

> On 24 May 2016, at 04:00, Sean P. DeNigris <sean(a)clipperadams.com> 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 formatter), I have never heard or seen the others ;-) > How would a new user discover what these are? If these are important to end users, they should be mentioned somewhere. > 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 > because we're showing packages, which are a dependency/SCM artifact, instead > of capturing/representing logical domain relations. There are so many > packages that start with e.g. System. It is not relevant to the user that > they are packaged separately, unless one is hacking that library. These > should all be collapsed under a top-level System node. This has been suggested before. I actually like the current approach, I would not want to click open trees all the time. > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896956.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 24, 2016

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

by Sven Van Caekenberghe

> On 24 May 2016, at 03:37, Sean P. DeNigris <sean(a)clipperadams.com> 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 bullet points in the > announcement and the 2400+ issues tagged for Pharo 5.0 It is our fault that such a list does not exist, but it is really, really hard to make it, since no one knows everything. It is also a huge amount of work. > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896955.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 24, 2016

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

by Sean P. DeNigris

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 because we're showing packages, which are a dependency/SCM artifact, instead of capturing/representing logical domain relations. There are so many packages that start with e.g. System. It is not relevant to the user that they are packaged separately, unless one is hacking that library. These should all be collapsed under a top-level System node. ----- Cheers, Sean -- View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896956.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 24, 2016

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

by Sean P. DeNigris

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, Sean -- View this message in context: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954p4896955.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 24, 2016

What's new in Pharo 5.0

by Sean P. DeNigris

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: http://forum.world.st/What-s-new-in-Pharo-5-0-tp4896954.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 24, 2016

Re: [Pharo-dev] compiledcode ?

by stepharo

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 <nicolaihess(a)gmail.com > <mailto:nicolaihess@gmail.com>> wrote: > > Would it be possible to add some comments, please. > > CompiledMethod is now a subclass of the new class CompiledCode > (and there is another > class CompiledBlock). > > Can we please don't add new classes at this system level without > *any* comment. > > nicolai > >

May 23, 2016

Re: [Pharo-dev] cleaning the Pharo Catalog

by stepharo

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 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 abandonware and definitively, they were not very well kept (no descriptions, no tags and even worst, many of them will not load fine). > So what do you think? should I keep them? > > Esteban >

May 23, 2016

UTF-8 regression in package saving

by stepharo

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

May 23, 2016

microsecondClockValue

by Eliot Miranda

Hi All, I see that access to the microsecond clock is called "microsecondClockValue". This name is wrong. It derives from millisecondClockValue which was indeed a value. The millisecond clock started from zero on every image startup and wrapped around every 45 days or so. The microsecond clock is quite different; it is an absolute clock whose zero is midnight on January 1st 1901, the start of the 20th century (damn those monks). So "Value" should be omitted from the selector. In Squeak we provide both Time utcMicrosecondClock and Time localMicrosecondClock which provide the number of microseconds since the start of 1/1/1901 in utc and local time zones respectively. It wraps round no sooner than 24/4/20168 (/not/ 2168). Time millisecondClockValue is provided for backward compatibility. _,,,^..^,,,_ best, Eliot

May 23, 2016