[Mono-list] Help needed with XSLT transformations (documentation browser)

[Adam Treat]

On Saturday 12 October 2002 03:55 pm, Scott Bronson wrote:
> On Sat, 2002-10-12 at 04:46, Scott Bronson wrote:
> > Here is a very, very, VERY basic start.  Don't expect much.  It's a
> > super quick demo that shows a little of what's possible.
>
> Whoops, sorry guys.  I didn't realize Evo quoted the entire Types.xml
> file in the reply.  Weird.  I'll try to keep mailbombs to a minimum in
> the future...
>
>
> My questions, a bit more lucid:
>
> 1) How do you want the transformed data stored?
>    Need to know this to know how to generate URLs.

IMHO, every type should have it's own file.  Miguel would probably want every 
member to have it's own file too, but am not sure about that.  Many people 
are clamoring for an msdn like documentation and this would require members 
to be broken out into individual html files, but many others like javadoc 
style...  

So for linking you'd probably have something like <a 
href="RelativePath/System.Object.html">Object</a>

> 2) What sort of output do you want?  Right now, I'm just shoving
>    out some really bad HTML.  I figure you'll want some sort of
>    parseable XML or at the very least presentable CSS/xhtml.
>    Have you got an example of what you want?

My preference is css/xhtml or compliant css/html ie, it should follow web 
standards and work in all major browsers.

> 3) Where can I find the other XML files?  Is there a DTD or spec
>    or something?  I've only tested against Types.xml.

The monodoc module in cvs.