On Nov 13, 2006, at 2:26 AM, Steve Holden wrote: > ... 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.
This is an excellent point. In the DVD, I do go through a lot of the code to get people acquainted with how things are laid out, but that is no substitute for a few good diagrams. The specs will help people tackle specific things (if they mention where to look to start implementing), but there's nothing like really *understanding* how everything is wired up vs. just knowing how to approach a given problem. TG doesn't have magic imports, so if you have the source available you can track through the source to find out what goes on... but, I think a lot of people would get tripped up when they enter the rather interesting world of turbogears.controllers (or turbogears.errorhandling!) That code is up for some major simplification. But, for now, some diagrams that show what's going on there would be a big bonus. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
