Thank you Paul and Stepharo. AnnoApp is a tool for writting your own comment for Package\Tag\Class\Method. seperating from source code file. Your own annotation can be save out as a file use AnnoEditor. The output file can be read back to (new) image according the name of Package\Tag\Class\Method if the names still in the (new version) image. AnnoEdit can mark or delete the annotations that do not exist in the Image. for Pharo4.0, MCHttpRepository location: 'http://smalltalkhub.com/mc/LiangBing64/AnnoApp/main' user: '' password: '' Best Regarts! Liangbing At 2015-06-14 00:31:05, "Paul DeBruicker" <pdebruic@gmail.com> wrote:

Hi Liang,

I like that adding Annos don't make the package with the code I'm annotating dirty.

How do I move Annos from one image to another?

The help is in Chinese, is there anything there that a person would need that they couldn't figure out from reading hte code? I found the AnnoEditor, which seems nice.

Have you put this up on smalltalkhub yet?

Thanks for sharing

Paul

BingLiang wrote

...

Hi,

I know the comment is very important for reading source code and it is also important to write your own comment after understand somethings. I created a rough annotation application----AnnoApp for Nautilus, please give me good advice to improve it. Attached are the monticello files. Thank you in advance!

Liang

PS I love Smalltalk and I love Pharo.

AnnoApp-Pharo4.0.mcz (36K) <http://forum.world.st/attachment/4832260/0/AnnoApp-Pharo4.0.mcz>; AnnoApp-Pharo5.0 50113.mcz (36K) <http://forum.world.st/attachment/4832260/1/AnnoApp-Pharo5.0%2050113.mcz>;

-- View this message in context: http://forum.world.st/If-comments-seperate-from-the-source-code-and-have-you... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.