On 1/12/06, Rubic <[EMAIL PROTECTED]> wrote:
> I came to TurboGears with the perception that
> SQLObject was optional, but if TG components
> are going to be tightly coupled to it then I
> may need to reevaluate my choices.

Decoupling is not a high priority for TG. Kevin does make efforts to
allow people to substitute components, but usually that results in a
sacrifice in functionality (e.g. non-kid templates lose i18n). You're
free to re-evaluate as you see fit, but having the pieces build on
others functionality is what makes it a stack rather than a collection
of components.

That said, the identity coupling break is at the provider level. You
have to couple somewhere if you want to interface with something...

> > That's just life.

Reply via email to