On 4/22/06, jvanasco <[EMAIL PROTECTED]> wrote: > I've been reading TG docs and sourceode nonstop for 4 days trying to > get this project to work. And I think most of my problems tie into > this: I picked an AWFUL time to try TurboGears - the docs are all out > of sync with the source ( they seem to be .9a2 <> .9a4 , the source > itself is constantly changing ( new releases seem to break old ones and > come out often) , and there's a new release on the horizion. In > regards to the Identity stuff, the identity information in the wiki is > all out of date.
Hopefully, we'll get a bunch of that cleaned up this weekend. The intention is to switch to using the new Docudo tool for managing our docs and I think that will help us avoid this mess for the next major release. Believe me, I feel your pain and I'm working to see both the docs and the source code accessibility picture improve dramatically. > People in Python LOVE large files with all their classes in it. Python > people also love tons of files in the same directory. Personally, I don't like either one of those things. When a file gets to be a certain length, I break it up into other files. When the directory has too much files, I make more packages. > People in web > development hate that stuff - it makes it a struggle to divide up work > and assign tasks to different people -- which is critical when you're > breaking something down into components for a few people to work on > simultaneously in the same room, or cross country, independant of one > another. Its even harder if you're trying to limit permissions to > certain components via SVN. Any project needs to be set up in a way that works for the needs of the project. Python is very flexible in that regard. You can have one class per file if you wish. You can have a bunch of classes in modules that are spread out among a bunch of packages. However you wish to build up your program's namespace is in your hands. TurboGears really only makes a couple of assumptions about where it can find things (yourpackage.controllers.Root, yourpackage.config and yourpackage.model). > The tg-big template solves a lot of that in regards to controllers, but > its largley/wholly undocumented (will this change in .95?). If you > want to break up the templates into directories - its entirely > undocumented, and lots of conflicting info exist on the newsgroups (i'm > guessing from API changes over the past few versions) In .9a4 > ,touching __init__.py and importing master.kid using a relative path > seems to do the trick. ( BTW I have a documentation patch half done > for that . I'll add it to trac later on ) Yep, you're right about how you create new template directories. Some new options for this may show up in 1.1 to help support customization of TG apps. > While I'd really love to see TG come out on top - so much of it makes > sense and is so intuitive to use - right now too much of it requires an > advanced knowledge of the TG internals to work on projects in a more > web-shop / less python way. I don't know what .9a5 and .9a6 will look > like - but I hope they will be easier for people who don't 'think in > python' . Docs are the big bug to be fixed. We'll see what other refinements are needed once we've done a decent job of actually explaining what's there... 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 -~----------~----~----~----~------~----~------~--~---
