> Ah, that makes sense. It's a real shame that all this 'magic' isn't  
> documented properly somewhere. It would save people banging their  
> heads to figure it out.

I've been thinking about this for a while now.

Although the devs are really putting a lot of effort into the
documentation, there's a fundamental problem. Let me try to describe
it.

The reason I've been developing with TG1, and now TG2 is because of
the flexibility it offers. I started with SQLObject. Didn't like it,
switched to SQLAlchemy. Great documentation there. Then I discovered
Elixir, used it for a while in simpler projects. Now I switched back
to SA for more advanced stuff. Learned a lot along the way, gained
some insights, because it showed me different approaches for using the
object model with a SQL backend.

Because of the wide range of interchangeable pieces in TG2. It all
needs to be covered in documentation, and it is, most of the time.
But the problem I often find is the lack of _depth_ in the
documentation. The examples look elegant and easy, they work, those
were the code snippets that made me enthusiastic about TG.
But just when you want to build a reald world application, you need
something a bit more powerful and all you're left with is the TG
source. That's the feeling I get sometimes. I've got no idea if
anybody feels the same way.

What to do about it?
I'd love to see source code of real-world TG deployments. With all its
imperfect workarounds.
I guess it only takes a TG wikipage with these 2 columns:
"project repository", "heavily used components".

I'll provide the first:
http://github.com/kvdb/6pp/tree/master, TGWebServices

Cheers,
Kees

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to