Em Segunda 24 Abril 2006 17:25, Jorge Vargas escreveu:
> NO you will have one model.py in one template for SA and another for SO,
> and yes the SA one will be bigger.
So you're proposing that we go now to 4 templates:
- SO standard
- SA stantard
- SO big
- SA big
For each provider we add, we need *now* two new templates (one for standard
and one for the big template). If we add a new "template", then we'd have to
add variations for each provider as well...
This doesn't scale well to me and looks like a lot of duplicate code -- today
the two templates can use both providers, so as of today instead of four we
just have two templates, if we add a third, then we don't need to touch any
provider since both will be automatically available to it as well.
> The reason why I think we should take the "default" out of the controller
> is that most people will just go with it, defaults are the root of all evil
> :)
Or good.
> About the templates I was thinking of doing that myself. I just need to
> learn how to work with nose, paste, adn tg templates.
You don't need all that. Take a look at the source and you'll see in
turbogears/qstemplates the templates we have today. Just duplicate them with
your structure.
What you'll need is to find a way to deploy those on any installation without
changing the installation itself, this is why I was talking about entry
points. This would provide the same flexibility as we have with widgets
today: you install a new widget and it is readily available for all
applications.
--
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
-~----------~----~----~----~------~----~------~--~---
