On Dec 8, 2013, at 11:16 AM, Torsten Bergmann <astares@gmx.de> wrote:
The reason is simple: when I wrote the config browser there was no such additional description on the configs itself and one would have to load the config into the image first.
Think of 2000 config's (note each is a package) loading in the future when the config browser opens. This will take ages. I think this is not good since the app should be responsive.
Maybe a "show details" button helps when the package is selected.
I would rather see: 1. Either a simple hosted seaside app "Pharo Store" that one can use to register a config for a specific pharo version (similar like squeakmap) maybe directly from the STHub interface with description, â¦
Indeed open and downloading all the files containing the configuration does not scale Now having the descriptions in the configuration let us build the catalog on a server
This app can be queried by the config browser (JSON/XML/Fuel/...) to display infos on the package, maybe also a rating about downloads, ...
2. Or a general mechanism that loads the configs, runs tests and if OK provides them for the config browser as "yes these config really work"
I will ask inria for an engineer to do 1 and 2
Bye T.