> ... I suspect what's either (possibly) missing or (more likely) not > currently pointed to determinedly enough is an architectural overview > showing the API relationships of the current bits. The famous graphic is > OK in terms of the gross relationships between the components, but after > a month working part-time with TG I'm only just beginning to feel that I > understand the architecture. > > Not only would such notes encourage contributors, they might also reduce > the amount of time those on this list who *are* familiar with the > architecture spend answering questions that seem insurmountable to the > questioners but often turn out to be quite trivial for those in the know. > > I don't underestimate the effort this would take. Maybe we need a > two-level effort, where the documenters can ask the architects off-line > and then tun the answers into documentation. Or something like that.
Very well put, such a document would be helping me a lot. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
