How it works

Tinaa is based on the idea that a system is made up of parts and subparts and sub-subparts (all resting on the back of a turtle). Tinaa can document anything as long as you tell it:

1. What kind of sub-parts it has
2. How to iterate over the sub-parts
3. How to display information about the parts

Mailing Lists

• tinaa-devel: A list for questions, patches, bug reports, and so on; It's for everything other than announcements.

Getting it

metabang.com is switching from darcs to git for source control; the current tinaa repository is on github and you can clone it using:

git clone git://github.com/gwkkwg/tinaa 

(note that this won't let you build CL-Markdown unless you also get all of its dependencies which I should list but don't because I haven't found (er, made) the time to automate the process yet...)

The easiest way to get setup with CL-Markdown is by using QuickLisp or ASDF-Install (deprecated). If that doesn't float your boat, there is a handy gzipped tar file

What it does now

Tinaa currently knows how to document packages (consisting of variables, constants, functions, classes, generic function, macros and symbols) and ASDF-Systems (consisting of sub-systems and packages). Here is Tinaa's self-documentation.

What it doesn't do

There are lots things it could do more nicely (class diagrams, prettier tables, callers and callees / cross referencing and so forth).

What is happening