We added catalog metadata to configuration now - the tools should take into account about that - people should add such metadata to their configuration
If you modify the package browser to present description it will be in the system
Stef, what is the spec, the API, is there an example config with description in the image already ?
really simple 4 class side methods catalogDescription ^ 'Soup is a frameworks for scrapping HTML. It offers a simplified query mechanism to abstract over the XML and HTML structures of a document.' catalogKeywords ^ #(HTML web query scrapping Soup XPath) catalogChangeLog ^ '- Version 1. 4 21/02/2013 migrated to SmalltalkHub [[[ (ConfigurationOfSoup project version: ''1.4'') load ]]] - Version 1.3 adding better stable version. [[[ (ConfigurationOfSoup project version: ''1.3'') load ]]] ' catalogKeyClassesAndExample ^ 'It is composed of some keys classes: - ==SoupElement== is the root of elements that are extracted during the parsing of an HTML document. Contrary to traditional HTML Parser, Soup produces a limited set of elements which approximate the HTML elements but supports querying and extracting information. - Soup. ==Soup== is the main public class of the package. It is the class to interact with as shown by the tests. The best way to get started is to get a soup of html elements using ==Soup class>>fromString:== as follows: [[[ Soup fromString: ''http://www.bedetheque.com/album-105582-BD-Atomium-Express.html'' asUrl retrieveContents ]]] Tests of the ==Soup== class are the place to start to learn the API.' have a look at SOUP