<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2015-05-06 13:08 GMT+02:00 Marcus Denker <span dir="ltr"><<a href="mailto:marcus.denker@inria.fr" target="_blank">marcus.denker@inria.fr</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
> On 06 May 2015, at 10:53, Christophe Demarey <<a href="mailto:Christophe.Demarey@inria.fr">Christophe.Demarey@inria.fr</a>> wrote:<br>
><br>
><br>
> Le 5 mai 2015 à 17:14, Kasper Osterbye a écrit :<br>
><br>
>> Marcus Denker-4 wrote<br>
>>> Right now we do not have yet Package comments.<br>
>>><br>
>>> But we should!<br>
>>><br>
>>> MBInfo seems to be a private class of Versionner…<br>
>>><br>
>>> For package comments we first need to evaluate the design space…<br>
>>> e.g. where to store it in the image, how to store it in Monticello…<br>
>><br>
>> OK - Makes sense.<br>
>><br>
>> From my perspective, the key to getting this of the ground is to make sure<br>
>> such comments can be written and read in Nautilus. The package objects used<br>
>> in Nautilus are from "RPackage".<br>
>> Thus, the problem, in my view reduces to:<br>
>> a) How to make room in RPackage for a comment field (add one more IV)<br>
>> b) How to integrate the storage of this field in connection with Monticello<br>
>> as Marcus writes.<br>
><br>
> I don't think is the good way to do that.<br>
> We are working on adding meta-data to packages. These meta-data includes a package description (or comment) but also a lot of other data.<br>
> You will not be able to store everything in rpackage inst. var. And of course, there is also the problem that Monticello is not able to store meta-data (e.g. STON files).<br>
> For now, the best option is to use a PackageManifest.<br>
><br>
> If you want to allow package comments in Nautilus, I would display the content of the description method of the package manifest if available.<br>
><br>
<br>
</div></div>Yes… this could be the easiest for now.<br>
<br>
Then as a second step, we add support to store resources in Monticello.<br>
<span class="HOEnZb"><font color="#888888"><br>
Marcus<br>
<br>
<br></font></span></blockquote><div><br></div><div>Adding metadata to MC cannot be very difficult, MC already carries plenty of metadata ;)<br></div><div>Coordination with other dialects (squeak/gemstone/...) would be welcome, because i'm sure that every dialect would benefit from package comments, or already has package comments (vw along with many other properties).<br></div><div>No long discussion required, if no consensus, just let Pharo lead.<br></div><div>I remember that Bert has experimented adding a comment to PackageInfo, but I don't know in which state it did end up (MC-wise).<br></div></div><br></div><div class="gmail_extra">Nicolas<br></div></div>