A naive proposition : Use a comment in the header of the mcz of the configuration (or whatever appropriate metadata about one of the file of the mcz) so that the description of the package (a configuration is a package, right?) can be retrieved without loading the zip in complete.
In the same way when opening a package repository, you can get the last commit release ? Equivalent approaches could then be designed for other formats than the mcz. Thierry ________________________________________ De : [email protected] [[email protected]] de la part de Esteban Lorenzano [[email protected]] Date d'envoi : samedi 4 août 2012 14:20 À : [email protected] Objet : Re: [Pharo-project] RE : Configuration Browser feedback Yes, that would be a good addition, but sadly is not so easy... if you have an idea of how to implement it, I would be happy to introduce it :) Cheers, Esteban On Aug 4, 2012, at 2:06 PM, GOUBIER Thierry <[email protected]> wrote: > +100 on the configuration description ! > > Thierry > ________________________________________ > De : [email protected] > [[email protected]] de la part de Ben Coman > [[email protected]] > Date d'envoi : samedi 4 août 2012 13:14 > À : [email protected] > Objet : [Pharo-project] Configuration Browser feedback > > Just thinking that the second tab of the Configuration Browser being > called "Untrusted" is a bit harsh and not really socially engaging. > "Community" has a better feel to me. > And perhaps not "Configurations" for the first tab either, since both > tabs are configurations. Perhaps "Core" or "Supported" or "Vetted" or > "Gold" or something similar. > > Also, what would be really fantastic would be some description of each > configuration being displayed in a pane on the right hand side. There > are A LOT of configurations listed there - which is great - but I don't > feel inclined to go looking up every single one to see if they interest > me. Sometimes what gets people interested in trying out new things is > that it just catches their eye in casual browsing. > > I guess a pre-requisite of that would be the ConfigurationOf file > containing such a description, as well as perhaps something on the back > end server that caches those descriptions into one file. > > cheers -ben > >
