#36 look&feel and function

[Lynn Ranen]

It would be great if you could implement these in V3.

[1] Multi-color output (a la pydocs output) -- based
on object type

[2] .css-based output configuration -- provide a
default .css styles with bgcolors, fontcolors, ... in
(what i call) "Happydoc blue", but allow the user an
easy way to customize the look & feel.

[4] Write subclass that writes comments as ASCII in
<pre> tags. -- I find that my comments get mangled by
the .stx processing, and I would just like to see my
comments spit out in <pre> tags.

[5] Complete index page -- It would be nice to have a
complete index page, that lists all docs. ( This
might have to be limited to some number of entries for
large document sets -- eg 500 links MAX)

FWIW -- I guess that the current way to implement this
is by developing a new formatting class (which is
relatively painless). But, since you're writing a new
version, I figured there's no point in not asking.

[Doug Hellmann]

Logged In: YES
user_id=34486

Nobody (including me) particularly likes the current HTML
output format. I have been planning to try to support a
template system using PageTemplates, but haven't gotten
around to actually implementing that. There are a few more
framework changes to make for 3.0 before I could hope to
even implement it. But, it's on the list.

Once it is easier to write templates for the text output
formats (HTML, XML, etc.) #2 and #4 (no 3?) could be handled
by each user, and template sets could be submitted back to
be included in the core releases. I will also try to make
the default templates look nicer, although I'm not a designer.

#5 has been on the list for a long time, and I hope that the
architectural changes I'm making for 3.0 will make it easier
to produce such a thing.