Hi, as you know I’m working on QualityAssistant, and at the moment the current 
structure of false positives in Manifest in not good enough for me. So I plant 
to reimplement it. Should I follow some guidelines? Because you are introducing 
this new package manifest, and I think that it could make sense if I’ll give 
you a feedback whether I works well for my needs.

Uko


> On 06 May 2015, at 13:56, Christophe Demarey <christophe.dema...@inria.fr> 
> wrote:
> 
> 
> Le 6 mai 2015 à 13:21, Kasper Osterbye a écrit :
> 
>> demarey wrote
>>> If you want to allow package comments in Nautilus, I would display the
>>> content of the description method of the package manifest if available.
>> 
>> It would be great to leverage on something already taking place. 
>> Are you talking about class PackageManifest? 
>> I can see that RPackage has a method which will give me a PackageManifest
>> (or create a new one). I have not been able to spot "the description method
>> of the package manifest" (as mentioned by Marcus). Mostly those Manifest
>> classes seems to be used for other purposes than documentation.
> 
> Manifest classes were introduced to manage code critics false positives.
> 
>> I'll try out a few things to see how it can work, my reading of the
>> "TheManifestBuilder>>createManifestNamed:" shows that manifests would be
>> very suited for this documentation purpose, as it actually create a
>> ManifestClass in the package. I believe this class is stored in Monticello
>> like any other class. 
> 
> right
> 
>> For the time being I found no instances of PackageManifest, so it is a bit
>> unclear to me how these Manifest classes store any data?
> 
> 
> Indeed.
> There are PackageManifest classes only for projects managing code critics 
> false positives.
> I created the PackageManifest class to start the decoupling between the 
> manifest and critics, but there is not yet a lot of other tools / project 
> using it (but it will come).
> 
> Data is stored in raw strings in methods (instance side) of the Manifest.
> ex: 
> ManifestKernel>>#description
>       ^ 'I am the description of the Pharo Kernel package.'


Reply via email to