> On 6 maj, 2015, at 21:27 , Sergio Fedi [via Smalltalk] <[hidden email]> wrote:
>
> Does this mean that we should focus on adding the comments on this ManifestXXX class?
> (instead of other implementations)���
Yes, that seems like the right approach to me.

I believe we could add some methods to ���TheManifestBuilder��� to get/set a package comment. If we put the methods in a special category in that builder, we should be ok.

These methods are then what we call from the get/add comment in the AbstractNautilusUI class.


(Then I have some reservations to the details of how ManifestXXX are done, but that is for some other time - package comments should live here, and it is easy to work with.)



View this message in context: Re: Package comments
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.