As a suggestion, i think that we could have an API for getting a documentation on a per-package basis.
It could be accessible like following: System menu -> Help browser in help browser you having a special 'getting extra documentation' which autobuilds entries by collecting all implementors of 'documentationPackage' (or something like that) so user can see a tree like following: Getting extra docs Metacello Smethocello etc... and when user clicks on it, it either loads it automatically, or contains an instructions how to load it. On 18 January 2011 11:15, Torsten Bergmann <[email protected]> wrote: >>The problem is that we have 25 pages of metacello explanation before that >>>blog (which will be added to the book chapter). > > Hi Stef, > > I do not mean to add the blog contents! His latest blog post shows > a Pharo help book that is available as monticello documentation: > > See this screenshot: > http://gemstonesoup.files.wordpress.com/2011/01/screenshot.png > http://gemstonesoup.files.wordpress.com/2011/01/screenshot.png > http://gemstonesoup.files.wordpress.com/2011/01/profstef-tutorial.png > > and I ask if it would make sense to add it to Pharo-dev > by default or if one only gets it if he knows about Metacello > and how to load this book. > > Since it includes the API-Doc I think this would mean to > include Metacello too into Pharo-dev... > > Bye > T. > > > > > > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl > > -- Best regards, Igor Stasenko AKA sig.
