Em Domingo 23 Abril 2006 20:04, Jorge Vargas escreveu:
> I'm agains that, we will never reach a "good for all" default model.
>
> I think that the fact the default one is big means it will encourage most
> people to think of good/better/big ways to use it. (I'm refering to new
> web-developers)
>
> If we ever change it there should be diferent set of pre-define providers
> and have one as default.
>
> Or just don't define one at all and make it as simple as one class you
> define in your model, and make it as open as possible.
Please, say that at ticket #778
( http://trac.turbogears.org/turbogears/ticket/778)
Done
I believe it is better to have more opinions there, even though there's a link
to this thread.
How about what I said there, have no default provider? Unless people contrain their app to the default provider most people will
a) extend it
b) write their own
problem with a) is that it adds overhead, basically 2 everything being the most expensive (in performance) the 2 tables
problem with b) is that even if it's easy most people at first glance are "scare" of going into the deeps of TG.
So having no default at all will make everyone go with b)
Looking at the soprovider.py code, the TG_* classes are just normal SQLObjects the only reason they are there is convinience (which seems some people don't see it that way)
--
Jorge Godoy <[EMAIL PROTECTED] >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
