I already have support for package comments with cargo (including ui) using the package manifest. In fact, it is more. I have support for package metadata on packages (cf screenshot)
The question is how do you integrate that with current browser? When you select a package, the class creation template is displayed and there is no much space to display other things.
Le 24 mai 2016 � 09:15, stepharo <stepharo@free.fr> a �crit :
Le 24/5/16 � 08:21, Esteban Lorenzano a �crit :
On 24 May 2016, at 08:05, stepharo <stepharo@free.fr> wrote:
When people use a configuration and add a description
hovering over the package show you the description and this helps for real.
yes, this is super cool� but I would like the possibility to toggle a �comment� for packages too :)
Sure I push the manifest also for that.
So let us make every package gets a manifest and add a button to display the description.
Esteban
Stef
Le 24/5/16 � 04:00, Sean P. DeNigris a �crit :
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.