|
|
 top
|
  Subject: Alternate Documentation Stylesheets
Author: Lee Humphries
Date: 05 Nov 2002 06:22 PM
|
Hi Adam,
To add to your comments/wishlist.
>A few things would be nice (but not as new
>feature of SS):
>1) A repository of alternate layouts.
I'll second that.
>2) The existing stylesheet broken out
>(grouped) into more reusable components. We
>can then use these components as a
>starting point for creating libraries of
>different themes.
I've already done that to a degree. I wanted to generate documentation for my XSLTs and BizTalk XLangs (don't ask) based on what xs3p does. So I generated two XSLTs, one that builds the style element and one that builds the script. I can now modify them at will.
Having said that though, the ability to add your own layouts to such a repository as you described above would be great. Hmmm, maybe a WYSIWYG XSLT editor would come in handy here.
>In addition, it would nice if SS could:
>1) manage multiple documentation transform.
>Perhaps allow selection of the transform on
>a project or schema basis.
Yes, me too.
>2) Allow for post-processing (via FOP, or
>perhaps Batik)
Yep.
>3) Along the same lines, provide some
>mechanism where we can create (and deploy)
>the images used in the documentation (via
>SVG and Batik). This is rather complex
>because you'd have to run it a large number
>of times. Perhaps an XPath (relative to the
>root) to determine which nodes to generate
>an image for and an XPath (relative to the
>previous XPath) to generate the name of the
>results.
Yes, especially the bit about SVG and the bit about generating the name (I'm assuming you mean file path name) of the results.
>4) Allow for batch processing where I might
>create and store two documents, an HTML
>version and a PDF Version (along with all
>the graphics I produced).
Similarly, I would love it if I could drive the documentation generation process from an external script. At the very least open up access to the image generation.
>5) Provide a way to "Edit this Schema
>Documentation Transform" which would do the
>obvious thing, only having a default
>scenario where the source document is a
>exhaustively complete stylesheet.
(I'm assuming you mean 'exhaustively complete set of schemas'). That would be really handy because you could drop it straight into the WYSIWYG editor.
>It would be nice to have a way for me to,
>assuming that I've been good about
>annotating my schema, to produce all the
>documentation quickly and easily.
I annotate every last little bit (although why you're not allowed to stick an annotation inside a Group is beyond me), so I've got everything ready to go. But, like you, I just want some way of kicking off the whole thing in one go.
Lee
|
|
|
|
next