[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] API Docs


  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • From: "Richard Hartmann" <richih.mailinglist@xxxxxxxxx>
  • Date: Thu, 5 Jul 2007 18:36:20 +0200
  • Delivery-date: Thu, 05 Jul 2007 09:33:58 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=B0j1rFnORS5l4jw86ZCoJeLBrcuOAMCQZqsrSeNDWkwZAKN/0Y/yNW53MkD8xXEbzDsB4XuYaeVylaRfUQZj0sXSrUwoBqN2bi42FTkz/QrVHZePoEbj+zGtVq6BPAE6T+9jz4/MOEw7KVNHZzIoSF2UhmMv28GuA+ecBrY4z98=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

And yes, me again..


Regarding the API doc itself:
I assume it was written in Latex. If that is the case,
a \tableofcontents would greatly improve readability.
Perhaps even with clickable hyperlinks.

Also, it would help to use \\* instead of \\ within API
call blocks. That prevents splitting a single API call
over two pages which happens sometimes.

Finally, a reference for API calls would make a great
appendix enabling people to quickly reference the
calls.


I hope I am not annoying you guys (yet) ;)
Richard
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.