[EMAIL PROTECTED] wrote: > you have hit the issue on the head, finally. I was looking at this > route, and recently the 2 agile plugins that have popped up (agilo > looks really nice btw) and came to the same problem. The general idea > for me, is a requirement "document" is just a container object (say a > master ticket, or a field in a db row linking to a table) that holds > requirement objects(say, child tickets, a row in a table, etc). This > relationship also applies to design documents/design requirements, use > cases/accpetance criteria, test doc/test cases..etc. so, Trac ticket > system, or some other relational tool would work just fine, viewing in > Trac. Well, that's dandy, however, some of us ultimately need an > ACTUAL set of documents, so how to get them.
FWIW, I recently came across a Python library to create OpenOffice (ODF) documents by merging Python data structures into ODF template docs. See http://appyframework.org/pod.html. I don't know if it'd fit your needs, but maybe worth investigating. -- Don Dwiggins Advanced Publishing Technology --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
