On 24 May 2016, at 04:00, Sean P. DeNigris <sean@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.