Hi,

>From the author's point of view, Dandelion is basically a tool for generating
inter-operable meta models in various formats. HTML output was actually
just an sample, though I added some frills.

For just browsing Smalltalk code, I think SystemBrowser is better.

The advantage of Dandelion is abstraction. For example, it stores
analyzed code info in a repository. The analyzed data is independent of the
current code and it can be retrieved later for further analysis.

2006/9/5, Ramon Leon <ramonleon at cox.net>:
> > 2. ruby. http://www.ruby-doc.org/core and http://www.ruby-doc.org/stdlib
> > present current, accessible API docs and also higher level docs with
> > very little fuss. These are generated from extensive code comments,
> > READMEs, etc. (Many other languages do this but less effectively.)
>
> I can't help but point out how much Ruby's doc's are just imitations of
> a Smalltalk class browser.  How exactly is this better than class and
> method comments in Smalltalk directly?  How is dandelion better than a
> real browser either?  If you can generate the docs from the code, of
> what additional value is the doc?
-- 
[:masashi | ^umezawa]