After looking at the Mathematica documentation

Hi Vadim, you wrote in response to me:

> > * Each function is on a separate page.

> Do you mean HTML documentation or printed book?
> Each function on separate page may be good for HTML
> but it is paper waste for printed material.

I mean only the html documentation. I haven't seen the
printed Mma documentation, although that would be interesting.

> > * Links at the top of the page show the place of
> >   the item in a hierarchy of categories.
> >   Clicking on a category name shows the items in the category.

> Do we have any notion of hierarchy for Maxima objects?
> I haven't seen anything like this. 

Well, at present related functions are more or less grouped
into a file. A more careful category scheme will be helpful,
but it's something we'll have to create.

> > * Color and font distinguish aspects of the description.
> >   A synopsis stands out at the top. In examples, comments
> >   and labels are colored differently from input & output.
> >   Arguments are italicized (except for examples).

> I can implement different font attributes in update_examples
> script.  At least one thing can be done immediately - user input
> in bold face to make it differ from program output
> (like in Mathematica book).  I'm not sure about color though.

Bolding the user input is a good idea. I'd like to see that.

Color should be used in good taste, of course -- nothing
heavy handed. I'll try to show what seems appropriate in a mockup.

I looked for the Maple documentation but it's not on-line.
Maybe they have some good ideas too.

For what it's worth,
Robert Dodier


	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail