Hello, is not having a field for description or a link to a description in ConfigurationBrowser a design decision? Best regards, Markus
Hi Markus, On 21 Mar 2014, at 18:44, Markus Fritsche <fritsche.markus@gmail.com> wrote:
Hello,
is not having a field for description or a link to a description in ConfigurationBrowser a design decision?
Best regards, Markus
A Metacello configuration is just a single class inside a Monticello package. The Configuration Browser lists all those MC packages from a repository. Recently, we started with a convention for a couple of methods that form a meta description of the configuration. https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/? It will take a while before all those descriptions are added. However, in order to see them, you have to load the configuration (not install the code), it is not enough to just look at the MC package. There is no easy solution. HTH, Sven
On 22 Mar 2014, at 02:31, Ben Coman <btc@openInWorld.com> wrote:
Sven Van Caekenberghe wrote:
Hi Markus,
On 21 Mar 2014, at 18:44, Markus Fritsche <fritsche.markus@gmail.com> wrote:
Hello,
is not having a field for description or a link to a description in ConfigurationBrowser a design decision?
Best regards, Markus
A Metacello configuration is just a single class inside a Monticello package. The Configuration Browser lists all those MC packages from a repository.
Recently, we started with a convention for a couple of methods that form a meta description of the configuration.
https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/?
It will take a while before all those descriptions are added.
However, in order to see them, you have to load the configuration (not install the code), it is not enough to just look at the MC package. There is no easy solution.
HTH,
Sven
There is no easy solution
A step along the way would be that CI job uploading the equivalent in STON/JSON format to files.pharo.org (maybe .../updates/catalog or .../extra/catalog) Having the raw data accessible would facilitate others (or at least me) experimenting with ConfigurationBrowser to display the descriptions.
Yes, that would be a solution, it just has to be built ;-)
Yes we asked engineer positions to build such kind of infrastructure but it was rejected soâ¦
There is no easy solution
A step along the way would be that CI job uploading the equivalent in STON/JSON format to files.pharo.org (maybe .../updates/catalog or .../extra/catalog) Having the raw data accessible would facilitate others (or at least me) experimenting with ConfigurationBrowser to display the descriptions.
cheers -ben
participants (4)
-
Ben Coman -
Markus Fritsche -
Pharo4Stef -
Sven Van Caekenberghe